All posts
Ray Iyer
Ray Iyer
Co-founder & CEO, Anglera

Why medical & dental SKUs go invisible: the attribute gaps that filter you out

Why exam glove and dental SKUs vanish from filtered search and AI answers when AQL, ASTM rating, or GMDN code are missing — and how to fix it

Why medical & dental SKUs go invisible: the attribute gaps that filter you out

A box of exam gloves is not one product. It is a bundle of a dozen regulated attributes — material, AQL, thickness, chemo resistance, sterility, cuff length — and a buyer or an AI answer engine will only surface it if every attribute that matters is sitting in a structured field. Miss one, and the SKU doesn't rank lower. It disappears from the result set entirely. Here's the attribute set that actually governs visibility in Medical & Dental, and how to structure it so it holds.

Why this category punishes thin data harder than most

Medical and dental buyers are procurement specialists, practice managers, or infection-control leads working from a compliance checklist, not a mood board. They already know they need ASTM D6978 chemo-rated, powder-free, nitrile, size medium, before they open a page. Their job is to confirm a match against a spec, not to be sold on "premium comfort fit."

That makes the buying motion filter-first, and the filters are regulatory, not aesthetic. A hospital's infection-control team can't buy a glove that isn't proven against a specific chemotherapy drug list; a dental office can't buy a "sterile" glove that's actually only "clean." Classification bodies like the GMDN Agency exist specifically because generic commerce taxonomies aren't precise enough for this — GMDN Terms carry clinically relevant definitions and intended-use data that a plain category tree doesn't capture, and UNSPSC by itself isn't built to carry that level of medical-device nuance. If your feed only has a UNSPSC code and a marketing paragraph, you're missing the layer procurement systems actually query against.

The attributes that determine whether a glove SKU exists in search

For exam gloves specifically, the fields that drive both filtered search and safe purchasing decisions fall into a few buckets:

AttributeWhy it's a filter, not a footnote
MaterialNitrile, latex, or vinyl — allergy and durability filter, always facet #1
Governing standardASTM D6319 (nitrile) or ASTM D3578 (latex) — the base spec a glove must meet to be called "medical grade"
AQL (Acceptable Quality Level)Medical-grade exam gloves require an AQL of 2.5 or lower; buyers filter by AQL tier for defect risk
Powder statusPowder-free vs. powdered — regulatory and allergy filter
Chemo ratingASTM D6978 permeation testing against chemotherapy drugs — required for oncology and compounding buyers, absent from most consumer glove listings
SterilitySterile / non-sterile, and sterilization method if sterile
SizeXS–XL, cross-referenced to hand circumference, not just a letter
Cuff length / textureExtended cuff, textured fingertips — procedure-specific filters
Thickness (mil)Palm and fingertip gauge, tied to tactile sensitivity and puncture resistance
GMDN / UNSPSC codeTies the SKU to the classification systems hospital and dental procurement systems query against
FDA listing reference510(k) or device listing number, ideally cross-linked to the FDA's UDI/GUDID record for the labeler

None of these are optional metadata. Each one maps to a real filter in a hospital GPO portal, a dental supply e-commerce site, or a group-purchasing formulary. If the field is blank, the platform can't include the SKU in a filtered result — it isn't a ranking penalty, it's exclusion.

Before and after: a box of exam gloves

Here's what a typical supplier feed looks like next to what a buyer, a formulary system, or an AI answer engine actually needs.

Raw feed description (typical): "Premium nitrile exam gloves, powder-free, comfortable fit, box of 100. Great for medical and dental use."

Enriched attribute table:

AttributeValue
MaterialNitrile
Governing standardASTM D6319-19
AQL1.5
Powder statusPowder-free
Chemo ratingASTM D6978 tested, 9-drug panel pass
SterilityNon-sterile
SizeMedium (fits 7.5–8.5 in. hand circumference)
Thickness4 mil (fingertip), 3.5 mil (palm)
CuffStandard beaded cuff, textured fingertips
Units per box100
GMDN codePatient examination glove, nitrile
UNSPSC42132203

The raw version reads fine to a human skimming a page. It's invisible to a system filtering on AQL, chemo rating, or GMDN code — because there's nothing there to filter on.

Ask an answer engine

A buyer today doesn't always browse a category page. They ask: "which nitrile exam gloves are chemo-rated and meet AQL 1.5 for an oncology infusion suite?" An answer engine assembling that response needs a chemo-rating field, an AQL value, and a material field it can trust — extracted from a source document, not inferred from adjectives in a title. A listing with "premium fit" language and no structured fields simply isn't a candidate answer, regardless of how good the actual glove is.

How to structure it so it holds

Standardize units (mil, not "thin/thick"), enumerate values instead of free text (AQL as a number, not "low defect"), and map every SKU to both a commerce taxonomy and a clinical one — UNSPSC for procurement systems, GMDN for hospital and regulatory contexts. Pull the governing ASTM standard and AQL directly from the supplier's spec sheet or certificate of analysis, not from marketing copy, and keep a source reference on the field so it can be re-verified when a standard revises.

This is the same gap that shows up across distributor catalogs generally: the data buyers and AI systems actually query against lives in supplier PDFs and spec sheets, not in the description field. Anglera plugs into whatever PIM a distributor already runs — Akeneo, Salsify, inriver, or none at all, starting from a flat file — and continuously extracts, quality-scores, and gap-fills exactly these attributes from source documents, so a box of gloves stays a queryable, filterable, answerable SKU instead of a paragraph of adjectives.

Ray Iyer

About the author

Ray IyerCo-founder & CEO, Anglera

Ray is the co-founder and CEO of Anglera, building the product-data infrastructure for agentic commerce — turning messy catalogs into structured, AI-readable data that buyers and answer engines can find. Previously product at Uber; Stanford CS.

See it on your own SKUs.

A 30-minute walkthrough on your categories and your supplier data.

Book a demo