All posts
Ray Iyer
Ray Iyer
Co-founder, Anglera

The office supplies attributes shoppers filter on — and most catalogs miss

Office supplies attributes like page yield, GSM, and ring size decide filter and AI-answer visibility. See a toner cartridge before/after fix.

The office supplies attributes shoppers filter on — and most catalogs miss

A shopper filtering for "high-yield black toner" or asking an AI agent to "find a compatible cartridge for my HP LaserJet Pro" is running a structured query against structured data. If the attribute isn't there, the product isn't either. Office supplies is a category where the differentiators are almost entirely spec-level, not descriptive, which makes it especially punishing when catalogs skip them.

Why office supplies breaks on missing attributes more than most categories

Apparel shoppers browse. Office supplies shoppers search with intent: a specific printer model, a specific ring size, a specific paper weight. That intent maps directly onto facets. When an attribute is blank, the product doesn't rank lower in that facet — it disappears from it entirely, because faceted search and AI shopping agents both filter on structured fields, not on adjectives buried in a title.

The same logic applies to AI answers. When someone asks ChatGPT, Gemini, or Google's AI Mode to recommend a toner cartridge for a specific printer, the model is reasoning over whatever structured attributes it can extract from the page or feed — compatible models, page yield, color, cartridge type. A title like "Premium Toner Cartridge — Black" gives an AI shopping agent nothing to match against a query like "ask an AI to recommend a high-yield toner for my Brother HL-L2350DW that won't void the warranty." No compatibility field, no yield number, no OEM/compatible flag — no recommendation.

The attributes that actually carry office supplies

Every office supplies subcategory has its own small set of load-bearing attributes. Miss these and the product is functionally invisible in filtered search, regardless of how good the copy is.

SubcategoryAttributes shoppers filter on
Toner/ink cartridgesPage yield, cartridge type (ink vs. toner), color, compatible printer model(s), OEM part number, OEM vs. compatible/remanufactured
Copy/printer paperSheet size, weight (lb/gsm), brightness rating, sheets per ream, recycled content %
Pens/markersInk type (gel, ballpoint, dry-erase), tip/point size, color, pack count
Staplers/staplesStaple gauge, sheet capacity, throat depth
Binders/filingRing size, ring style (D-ring vs. round), spine width, sheet capacity
LabelsLabel size, sheets per pack, adhesive type, printer compatibility (laser/inkjet)

None of these are marketing language. They're the fields a facet filter or an AI agent's structured-data parser is built to read. A "premium" or "professional-grade" toner cartridge tells a shopper nothing about whether it fits their printer.

Worked example: a toner cartridge, raw feed vs. enriched

Here's what a typical raw supplier feed looks like for a toner cartridge, next to what filtered search and AI agents actually need.

Raw feed (as received from supplier):

FieldValue
TitleBlack Toner Cartridge
DescriptionHigh quality replacement toner, long lasting
Brand(blank)
CategoryOffice Supplies / Ink and Toner
Price$34.99

Enriched (Anglera-normalized):

FieldValue
TitleCompatible Black Toner Cartridge — HP 410X Replacement (CF410X)
Cartridge typeToner
ColorBlack
Page yield6,500 pages at 5% coverage (ISO/IEC 19798)
Compatible printer modelsHP Color LaserJet Pro M452, M377, MFP M477 series
OEM/compatible statusCompatible (non-OEM)
OEM equivalent part numberHP CF410X
BrandGeneric-brand name
CategoryOffice Supplies / Ink and Toner / Laser Toner / Compatible Cartridges

The raw version can't answer "will this fit my printer," "how many pages will I get," or "is this OEM or compatible" — the three questions every toner buyer actually asks. The enriched version answers all three in structured fields a facet filter and an AI agent can both parse.

Page yield specifically needs to be normalized against the actual test standard, not just copied from a supplier's marketing claim. Page yield for laser cartridges is measured under ISO/IEC 19752 at 5% page coverage — a standardized text-document benchmark that makes yields comparable across brands. A number without that context, or one that's inconsistent with the standard, is a data-quality gap even if it's technically present.

The OEM-vs-compatible distinction matters just as much. Compatible cartridges are typically priced 50-70% below OEM equivalents for the same yield and spec, which is exactly the kind of comparison shoppers and AI agents are trying to make when they filter or ask. If that field is missing, the product can't surface in either an "OEM only" filter or a "cheapest compatible option" query.

Structuring for both facets and feeds

Google's own product data guidance backs this up outside the office supplies niche: brand, GTIN or MPN, and category-specific attributes like color and size are required or conditionally required for products to appear correctly in Merchant Center listings. Office supplies has its own version of that requirement set — page yield and printer compatibility function the same way brand and GTIN do elsewhere. If they're not structured as discrete, normalized fields (not sentences inside a description), they don't count as present for filtering purposes.

The fix isn't rewriting descriptions — it's separating spec data into its own normalized fields, cross-referencing against known standards (ISO page yield, OEM part numbers), and keeping compatibility lists current as printer lines change.

Anglera plugs into whatever PIM or feed a retailer already runs, scores each SKU against the attribute set its category actually needs, and gap-fills missing fields like page yield, cartridge type, and printer compatibility from source data rather than guesswork. Your PIM stores the data. Anglera does the work of making sure the fields that decide whether a toner cartridge shows up in a filter or an AI answer are actually there.

Ray Iyer

About the author

Ray IyerCo-founder, Anglera

Ray is a co-founder 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