The same species under a dozen names, and buying-decision attributes buried in free text — how to get botanical data into one consistent structure across every grower.
A rose is not a rose. In a plant catalog it is Rosa, then a group and a cultivar, then a German trade name, then a supplier article code — and depending on which nursery shipped the list, those pieces arrive in a different order, spelled differently, or half missing. Multiply that across perennials, shrubs, seeds and bulbs from a handful of growers, and the assortment stops being comparable long before it reaches the shop.
Product data for plants and seeds is botanical data: attribute-rich, naming-heavy and almost never standardized at the source. This is a focused corner of the broader garden & plant retail challenge — where the pain is less about variants and more about botany that no generic feed was designed to hold.
Unlike a screw or a t-shirt, a plant is bought on its living behavior. The attributes that decide the sale are botanical, and they rarely arrive in clean columns:
These attributes almost never come as a structured feed. They sit in free-text descriptions, on care-label PDFs, or in a grower's own spreadsheet layout — which means someone has to read them out and normalize them before the catalog can filter on them.
The attribute problem is real, but naming is what actually breaks the catalog. One plant legitimately carries several names at once:
Different growers deliver the same plant under different combinations of these, in different spellings, sometimes abbreviated. Without a unifying layer the same species lands as three separate products: the assortment splits, stock views fragment, and shop search misses matches because the customer typed the common name and the record only holds the botanical one. Reconciling that by hand across thousands of records is exactly the manual work that never ends.
Horticulture is one of the least standardized retail sectors on the data side. Here is honestly what applies and what does not:
| Data layer | What a standard covers | Where it stops |
|---|---|---|
| Article identity | GTIN/EAN identifies the packaged unit | Says nothing about the plant itself |
| General classification | ETIM / eCl@ss exist for technical goods | Barely reach into horticulture; no botanical depth |
| Botanical naming | Botanical nomenclature is a scientific convention | Not enforced in supplier feeds; trade names dominate |
| Botanical attributes | No dominant industry attribute standard | Location, hardiness, growth data = free text / PDF |
| Sales content | Not the job of any identifier | Descriptions, images, care copy absent |
In short: GTIN/EAN identifies the pack, and that is roughly where standardization ends. The botanical layer — the part customers actually buy on — is left to whatever each grower typed into their own sheet. That absence of a standard is why manual unification dominates the sector.
The job is the same three steps every multi-supplier retailer faces, tuned for the botanical case — and that is what Productbay is built for:
The point is that Productbay starts exactly where the standard stops: it builds the botanical structure the sector never got from an official body, and it does the naming reconciliation and attribute extraction that would otherwise be endless Excel work. For the fuller picture see the garden & plant overview, learn how the same engine categorizes products automatically, and how it enriches and normalizes data from multiple suppliers. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs.
Trade names, botanical names, hardiness zones, sowing times — plant data is messy by nature. See how Productbay unifies naming and extracts botanical attributes into one catalog in a 30-minute walkthrough.
Get started