Sourcing vegetable seeds by crop family instead of by single species

Retail shelves usually fill up one crop at a time, but customers often shop by meal or growing situation, not by botanical name. The wholesale catalogue can be read in two ways: as a long list of single species, or as clusters of related vegetables that share a shelf, a season and a shopper. This overview treats ten catalogue lines — tomatoes, cabbage and kale, peppers, leafy greens, cucumbers, gourds, squash and pumpkins, eggplant, corn, and onions and leeks — as family clusters, so a shop can decide its shelf structure before picking a single variety.

Why a species list and a shelf plan are different

A species list answers the question "do you have this crop?" A shelf plan answers "what does a customer walk past and pick up together?" The catalogue lists these ten lines as separate groups under vegetables, each with its own varieties and quantity tiers. Grouping them into families does not change the catalogue; it changes the order in which you plan, so you commit shelf space to a cluster before you start comparing individual references.

The fruiting cluster: tomatoes, peppers, eggplant, cucumbers

These four lines share a shopper and a season. Someone planning a summer vegetable patch or a greenhouse will often look for all of them in one visit. Treating them as a cluster helps you decide how deep to go within each line and keeps adjacent shelf space coherent. The catalogue lists them separately, so you still select varieties line by line; the cluster only decides how much space each line gets and which one anchors the section.

The Brassica cluster: cabbage, kale and leafy greens

Cabbage and kale form a catalogue section in their own right, but the group records mix horticultural group names rather than one accepted species name, and the entries note that a shared genus does not make names interchangeable. Leafy greens are listed as a separate group. Reading them as a cluster is useful for shelf layout, but preserve leaf-type and cultivar qualifiers in any enquiry, and ask for clarification against the SKU where the botanical label is broad.

The vine cluster: cucumbers, gourds, squash and pumpkins

Gourds, squash and pumpkins appear as distinct catalogue groups rather than one combined section, with cucumbers listed separately as well. For a retailer the distinction matters less for shelf logic than for labelling: customers looking for eating squash and customers looking for ornamental gourds are not the same shopper. Grouping them on a shelf can still work if the display and labels keep the four lines visibly apart.

The staple cluster: corn, onions and leeks

Corn, onions and leeks sit in the catalogue as their own groups. They tend to serve the customer who is planning a full kitchen garden rather than a single crop, and they are often bought in modest quantities alongside other staples. Clustering them makes sense for a compact shop with limited space, because the section serves the same browsing moment even though the varieties are chosen line by line.

How clustering changes depth decisions

Once lines are clustered, depth becomes a comparative decision rather than an absolute one. Within each cluster you can decide which line carries the widest selection and which line stays narrow. The catalogue does not fix that balance; varieties are recorded per group, so the number of entries in a line is the only published signal of depth. Use it as a starting point, not as a stocking instruction.

Writing enquiries that match the shelf plan

An enquiry is non-binding and no payment is taken through the website, so the enquiry is where your shelf plan meets availability. Group your selection by cluster when you send it, name the SKU and the required weight for each item, and state your destination and packaging requirements. Pack size, available quantity and final price are confirmed in the quotation, so the cluster plan stays a plan until that confirmation arrives.

Where clustering does not help

Clustering is a layout aid, not a botanical claim. The catalogue itself warns that related names can be confused and that a shared genus is not an identity. If a customer asks for a specific cultivar, the cluster is irrelevant and the SKU is what matters. Keep the cluster as the way you arrange the shop and the way you plan enquiries, and let individual references carry the accuracy.

Seeds, knowledge and growing possibilities.

Seed trade journal