Why medical & dental feeds lose to marketplaces — and how to close the gap
Why medical & dental distributor feeds get outranked on marketplaces, the identifier and attribute bar channels enforce, and how to close the gap fast.
A box of exam gloves looks like the simplest SKU in a medical-dental catalog — until a buyer needs to know if it's powder-free, what the AQL rating is, whether it's rated for chemo drug exposure, and which size actually fits their staff. Most distributor feeds answer one or two of those questions. Marketplaces and hospital procurement portals now require the rest, in structured fields, before they'll rank the listing at all. Here's why thin feeds keep losing shelf space to marketplace-native sellers, and what channel-ready completeness actually requires.
Why "we have a description" isn't enough anymore
Medical-dental distributors have historically competed on relationship and price, not content. The feed was built to move a flat file into an ERP, not to answer a buyer's question at the point of search. That worked when reps and catalogs mediated the sale. It doesn't work on a marketplace, where ranking and buy-box eligibility are driven almost entirely by how completely and correctly a listing matches the category's required schema.
Google Merchant Center is explicit that products without a valid identifier — GTIN, MPN, or brand — become ineligible for full Shopping placement, not just downranked (support.google.com/merchants/answer/6324461). Amazon's medical and PPE categories often require Product ID validation even where GTIN exemptions exist elsewhere, and category-specific attribute sets (glove type, powder status, AQL, sterility) get enforced at the point of listing, not discovered later. In parallel, the industry's own data backbone — GS1's GDSN and the newer Global Data Model — exists specifically because healthcare retailers and distributors kept failing to synchronize a consistent set of foundational attributes across trading partners (gs1.org/services/gdsn). None of this is optional structure. It's the schema the channel checks against before it will show your product at all.
The bar marketplaces actually enforce
Three layers matter, and medical-dental feeds typically clear one of them.
| Layer | What's checked | Where feeds usually fail |
|---|---|---|
| Identifiers | Valid GTIN/UPC, brand, MPN, and — where applicable — UDI-DI mapped correctly to GUDID for regulated devices | GTINs reused across pack sizes; UDI present on the label but never structured back into the feed |
| Attributes | Category-specific required fields: glove material, powder status, AQL level, sterile vs. non-sterile, chemo rating, size, latex-free flag | Buried in a PDF spec sheet or the free-text description, not a structured attribute |
| Trust content | Images showing packaging and count, compliant claims language, certifications (FDA clearance, ASTM D6319) | Stock manufacturer image with no lot-count or size call-out, unverifiable claims |
A field existing somewhere in your data isn't the same as a field existing correctly for the category node the product sits in. That distinction is what silently throttles otherwise-live listings — no rejection email, just quiet suppression in search.
Case in point: a box of exam gloves
Here's what a typical supplier feed hands a distributor, next to what a marketplace and a procurement buyer actually need to make a decision.
Raw feed description (typical): "Nitrile exam gloves, box of 100, blue, various sizes available."
Channel-ready enrichment:
| Attribute | Value |
|---|---|
| Glove material | Nitrile, latex-free |
| Powder status | Powder-free |
| Size | Medium (also listed: S, L, XL as variant GTINs) |
| AQL rating | 1.5 |
| Chemo-rated | Yes, ASTM D6978 |
| Sterility | Non-sterile, single use |
| Count | 100 gloves / box, 10 boxes / case |
| Regulatory | FDA 510(k) cleared, class I exempt |
| Identifier | GTIN-14 (case), GTIN-12 (each), UDI-DI cross-referenced |
The first version reads fine to a human skimming a page. It fails almost every structured check a marketplace or GPO portal runs, and it gives an AI-driven answer engine nothing to match against a specific query.
Ask an answer engine
A buyer today doesn't browse a PDF catalog — they ask a question. "What's a chemo-rated, powder-free nitrile exam glove in medium that's AQL 1.5 or better?" only surfaces a distributor's product if size, AQL, powder status, and chemo rating exist as separate, correctly labeled values the engine can parse and compare. A description that just says "various sizes available" is invisible to that query, no matter how good the price is.
Closing the gap without a re-platform
None of this requires ripping out the ERP or running a multi-year PIM migration. Distributors typically start from whatever they already have — a flat export, a supplier spec PDF, images from the manufacturer — and the gap is almost always the same: values exist in source documents but were never scored, gap-filled, and mapped into the fields each channel actually checks.
This is the layer Anglera works in. It plugs into an existing PIM (Akeneo, Salsify, inriver, Stibo, Syndigo, Pimcore, Informatica) or sits on top of a flat file if there's no PIM at all — your system of record stays the system of record, and Anglera does the enrichment work: scoring completeness against the specific rules each marketplace or GPO enforces, extracting and gap-filling attributes from real supplier documentation, and getting a catalog to channel-ready in weeks rather than the multi-year timeline a full data-quality overhaul usually implies. The exam glove problem isn't unique to gloves — it's every SKU in a medical-dental catalog where the buyer's question is more specific than the feed's description.