Separate cardoon and globe artichoke references in seed buying
An artichoke catalogue group can bring cardoon and globe-artichoke references together, but a retailer should not treat them as one interchangeable seed product. The customer's intended crop and harvest need to be clarified before selecting the article. Precise commercial records can preserve useful historical or horticultural labels while still making the actual buying choice understandable.
Identify the intended reference
The BSI artichoke category retains separate Cynara cardunculus and Cynara scolymus hubs, with named cardoon and globe-artichoke entries. Use those records to locate the existing articles, not as a reason to make an unsupported taxonomic claim about unrelated species. The practical question is which commercial reference the buyer wants to obtain.
Keep the crop description, full named selection and supplier code together. A colour word alone may not resolve the request when several entries have similar language. If the customer asks simply for artichoke seed, clarify the intended crop and use before preparing the enquiry. Record that decision so another colleague can follow it without repeating the conversation.
Connect the description to the harvested part
RHS describes globe artichokes as plants grown for their flower buds and discusses them as substantial perennials. That context belongs with the relevant globe-artichoke project. It should not be pasted unchanged across every cardoon record merely because the catalogue groups them nearby. Identify the article first, then choose the appropriate crop guidance.
For customers planning a garden, the whole plant matters alongside the harvested bud shown in a photograph. Ask about available space and the growing situation, using reliable information for the selected reference. Avoid promising one exact size or timetable for the entire category from a single general description.
Keep names useful without merging stock
Botanical and horticultural naming can be complex, but the stock system still needs stable article identities. Preserve the supplier code as the commercial link and use aliases or explanatory notes to handle naming relationships. Do not merge separate references automatically because a botanical database organises them together, and do not create duplicate products solely because labels differ.
When a data import changes wording, review whether the underlying article has changed or only its naming field. Record the reason for any correction. This makes it easier to compare older purchase documents with current retail pages and prevents the same ambiguity from reappearing during the next catalogue update.
Check the final retail choice
Compare the selected source reference with the packet title, image and instructions. A correct supplier code in the buying file will not help the customer if the front image or growing insert describes another crop. Have a second person follow the final presentation back to the verified record before approval.
Add a short explanatory field to the buying sheet for the customer’s intended crop. This is useful when botanical names are being reviewed or imported labels vary. A future colleague can then understand the commercial choice without needing to reopen the whole naming discussion before processing a reorder or reviewing revised artwork.
Use the quoted quantity basis when planning the order and preserve source identity through packing. Record recurring questions about crop names for the next description review. Our Identify African eggplant seed before using aubergine descriptions explores another perennial vegetable-seed decision. A clear artichoke range helps customers recognise the intended crop while keeping the cardoon and globe-artichoke commercial references precise enough for reliable purchasing and support.