Product Data for Aquaristics: Technical Values and Compatibility
Filter flow rate, tank volume, wattage, spectrum — aquaristics products are defined by their technical values. The problem is that every supplier delivers them in different units and column names, and compatibility rarely arrives at all.
- ✓Aquaristics is a technical-value business: tank volume, filter flow rate (l/h), wattage and light spectrum decide whether a product fits — the value lives in the attributes.
- ✓But every supplier delivers those values differently — l/h vs. gph, watts vs. tank-size range, spectrum vs. Kelvin — under different column names and units.
- ✓There is no dominant data standard, so the accessory and livestock-supply longtail arrives as Excel and PDF by hand.
- ✓Productbay normalizes the technical values and links compatible components in one system, so compatibility becomes a queryable attribute instead of a guess.
An aquaristics catalog is a catalog of numbers. A customer looking for an external filter doesn't want a nice photo first — they want to know the flow rate in liters per hour, the media volume, and whether it suits their tank. A heater is chosen by wattage against tank size. A light is chosen by spectrum and PAR. Almost every purchase decision in this branch runs through a technical value.
Product data for aquaristics is defined by technical values and compatibility: flow rate, volume, wattage, spectrum — and which component fits which setup. That's what makes the branch demanding, and it's why a data process built for simple consumer goods falls apart here. Aquaristics is a sub-branch of the broader pet supplies challenge, but a distinctly technical one.
Why are technical values in aquaristics so hard to maintain?
The core problem isn't that the values are complex — it's that no two suppliers deliver them alike. The value of the product sits in its attributes, and those attributes arrive inconsistent from every direction:
- Different units: filter flow rate as l/h from one brand, gallons per hour from another; volume in liters or gallons; light as Kelvin, lumen, PAR or a spectrum curve depending on the manufacturer.
- Different column names: the same attribute shows up as "flow", "pump rate", "Förderleistung" or "l/h max" across five supplier sheets — a mapping nightmare.
- Compatibility as prose: "suitable for tanks up to 400 l" lives in a free-text description instead of a structured, queryable range.
- Deep spec sheets: for filters, pumps, CO2 systems and lighting, the real data sits in a PDF datasheet, not a clean feed.
Normalized once, these values are gold — customers filter and compare on them. Left raw, they're a per-supplier cleanup job that never ends. The fix is the same discipline as everywhere: consolidate, normalize, enrich and publish.
Why does supplier delivery stay so inconsistent — and is there a standard?
In branches like automotive or building materials, a shared standard does most of the normalizing for you. Aquaristics has no such thing. A handful of large brands ship reasonably clean data, but there is no dominant classification everyone maps to. Compare the landscape:
| Data layer | What arrives from suppliers | Where it stops |
|---|---|---|
| Core technical specs | Large brands ship flow rate, wattage, volume | Different units and column names per brand |
| Classification | No dominant standard (no TecDoc/ETIM equivalent) | Every retailer builds its own category tree |
| Compatibility | Stated as free text, if at all | Not structured, not queryable, not linked |
| Accessory / consumable longtail | Manufacturer Excel or PDF | Sparse attributes, no images, no content |
| Sales content | Rarely delivered | Descriptions and benefit copy absent |
So the real setup is a clean-ish core from the big brands and manual spreadsheet work — often with PDF datasheets — for the accessory, plant and livestock-supply longtail. Without a standard to lean on, the normalization has to happen inside your own data process.
How does Productbay help in aquaristics retail?
The job is to turn inconsistent, unit-mismatched supplier data into consistent, linked technical attributes — and that is exactly what Productbay is built for:
- Consolidate: import every source once — supplier CSV, Excel, feed URL, FTP, API, PDF datasheet — and match by SKU or EAN/GTIN so existing products update and new ones are created.
- Normalize: map each supplier's columns to one target structure and unify the units — l/h, watts, liters, Kelvin — so the same attribute always means the same thing and stays comparable and filterable across brands.
- Enrich & link: AI writes descriptions, assigns categories, fills missing attributes from whitelisted sources, translates via DeepL, reads specs out of PDF datasheets, and keeps compatibility as structured, linked values — a filter rated for 200–400 l relates to the setups it fits. Always with a review queue before anything publishes.
- Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp), and feed exports for Amazon, OTTO and Kaufland — each with per-channel transformations.
The result is a catalog where compatibility is an attribute, not a guess, and where every technical value is comparable regardless of which supplier it came from. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — and aquaristics, with its density of technical attributes, is exactly the kind of assortment it was made for.