Two data worlds in one aisle: labelling-regulated food with analytical constituents, and accessories with size and colour variants — where GDSN helps, and where it stops.
Walk one aisle of a pet shop and you cross two completely different product worlds. On one shelf: a 12 kg bag of dog food with a printed table of analytical constituents, a composition list and a feeding guide keyed to the dog's weight. On the next: a harness that exists in five sizes and three colours, a bed in three sizes, a collar in a length run. Same category, same supplier catalog — two completely different ways product data behaves.
Product data for dog supplies is split between two logics: labelling-regulated food and size-driven accessories. Food is a flat, attribute-rich record; accessories are a variant matrix. A setup built for one always leaves the other half underserved. This is a sub-branch of the broader pet supplies challenge, and the mixed data world here is exactly what makes it hard.
The core problem every multi-supplier retailer knows — no two suppliers deliver alike — is amplified here because you're juggling two data logics at once:
Do this by hand and it doesn't scale. The fix is the same as everywhere: consolidate, normalize, enrich and publish — but here you have to do it for both data worlds simultaneously.
On the food side there is a real standard: GDSN (Global Data Synchronisation Network), the pool the big pet-food brands use to publish master data with GTIN keys, pack sizes, analytical constituents and feeding guides. GDSN is genuinely useful for the branded food core. But it's important to be honest about what it does and doesn't reach:
| Data layer | What GDSN / brands deliver | Where it stops |
|---|---|---|
| Branded food master data | GDSN records for the big brands (GTIN, pack, constituents) | Nothing for regional / own-brand food outside the pool |
| Treats & supplements | Partial, brand-dependent | Small-brand snacks and supplements arrive as Excel/PDF |
| Accessories (harness, collar, bed) | Not a GDSN use case in practice | Size/colour variants entirely manual |
| Size normalization | No shared accessory size standard | cm-girth vs. XS–XL vs. breed chart — you map it |
| Sales content | Not the job of a data pool | Descriptions, SEO text, benefit copy absent |
In short: GDSN covers the food core of the big brands well. What it doesn't give you is the regional and own-brand food, the accessory size matrices, a way to normalize inconsistent sizing, or any sales content. That's the gap — and in dog supplies the gap is most of the SKU count.
The throughline is a three-step job, run for both data worlds at once — and that's exactly what Productbay is built for:
Crucially, Productbay starts where GDSN ends. If the big food brands already feed clean records via GDSN, great — Productbay complements it and takes over the regional food, the supplements, the accessory size matrices and the sales content no data pool provides. For the wider view across every animal, see the pet supplies overview. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains — and the whole product data process lives in one place.
Food and accessories, GDSN core and sized longtail, feeding guides and harness size runs — dog supplies packs it all into one catalog. See how Productbay consolidates, enriches and publishes both data worlds in a 30-minute walkthrough.
Get started