All posts
Ray Iyer
Ray Iyer
Co-founder, Anglera

Getting office supplies products recommended by ChatGPT, Gemini, and AI shopping

Office supplies shoppers now ask ChatGPT and Gemini to pick the product for them. Here's why thin catalog data loses that pick, and what actually fixes it.

Getting office supplies products recommended by ChatGPT, Gemini, and AI shopping

A facilities manager doesn't browse ten shredder listings anymore. She types one sentence into ChatGPT, gets one answer, and orders it. That shift is already reshaping which office supplies brands get bought, and most catalogs aren't built for it.

The office supplies shopper has a new front door

Office supplies used to be a search-and-compare category: type "cross cut shredder," open six tabs, compare spec sheets, pick one. That behavior is moving to a single prompt and a single answer. Gartner projects that AI agents will handle 90% of all B2B purchases within three years and intermediate more than $15 trillion in B2B spending by 2028, with procurement buyers already prompting tools like ChatGPT and Gemini for supplier and product discovery instead of running a search.

Office supplies retailers feel this earlier than most categories because the products are recurring, spec-driven, and easy to describe in a sentence: paper weight, shred capacity, ink yield, chair weight limit. That's exactly the kind of query an AI answer engine is built to resolve on its own, without sending the shopper to a results page at all.

Meanwhile the category itself is quietly moving online. In North America, office supplies ecommerce grew to 24% of category revenue, up from 22% the year before, even as brick-and-mortar sales slipped, according to a Shopify analysis of the office supplies market. More of the category's growth is happening in channels where an AI, not a store associate, is doing the recommending.

Ask an AI to recommend one, and watch what it actually checks

Here's the kind of prompt a real office supplies buyer runs today: "Recommend a paper shredder for a 10-person office that handles staples and credit cards, has a warranty, and won't overheat during a big cleanout."

To answer that, the AI has to filter on attributes, not adjectives. It needs shred type (strip-cut, cross-cut, micro-cut), security level, sheet capacity, continuous run time, bin size, whether there's a dedicated card slot, and warranty length. If a product page just says "heavy-duty office shredder" and a price, there's nothing for the model to match against the query. It skips the listing and recommends a competitor whose data actually answers the question.

This is the same pattern Google is formalizing in its own AI Shopping stack. Its 2026 Merchant Center changes push retailers toward more complete, verifiable variant data, and explicitly note that feed, page, and schema should reinforce each other — when the structured feed and the on-page Schema.org Product markup disagree, Google deprioritizes both rather than guessing which is right.

Why thin data makes a catalog invisible

Most office supplies catalogs were built for a shelf label, not a query. A typical feed row reads like a receipt: name, price, maybe a one-line description. That's enough for a human scanning a page. It's not enough for a model deciding whether your product answers a specific question.

Here's what that gap looks like on a real product, before and after enrichment:

AttributeRaw feedEnriched
TitleShredder BlackProShred CX400 Micro-Cut Paper Shredder
DescriptionOffice shredder, heavy duty12-sheet micro-cut shredder, P-4 security level, shreds staples, paper clips, and credit cards
Shred typeMicro-cut
Security levelP-4
Sheet capacity12 sheets per pass
Continuous run time30 minutes
Bin capacity5.5 gallons (approx. 90 sheets)
Credit card slotYes
Warranty2-year limited

The raw row has a name and a price. The enriched row has every value the AI needs to test the shopper's constraints one by one: staples, credit cards, a 10-person office's shred volume, a warranty. Only one of these versions can win the recommendation.

What machine-readable product content actually requires

Getting recommended isn't about writing punchier copy. It's about giving the model structured, checkable facts in the places it looks:

  • Complete core attributes on every SKU: brand, GTIN or MPN, material, dimensions, capacity, and condition, not just for flagship products but for the long tail of refills, cartridges, and accessories that make up most of an office supplies catalog.
  • Schema.org Product markup on every product detail page that matches the feed exactly, since mismatches between the two get both versions discounted.
  • Category-specific specs spelled out in words an AI can parse: "P-4 security level," not "extra secure"; "ENERGY STAR certified," not "eco-friendly"; "500-sheet paper tray," not "large capacity."
  • Accurate, current availability, because an agent that tries to check out a listing marked in stock when it isn't gets a failed transaction, and that failure follows the retailer, not just the SKU.

None of this requires ripping out an existing PIM or catalog system. It requires treating gap-filling and attribute maintenance as ongoing work, not a one-time cleanup, because new SKUs and refill variants arrive every week and each one starts life thin.

Anglera plugs into whatever PIM or commerce platform an office supplies retailer already runs — or none at all — and continuously scores, gap-fills, and enriches product data so every SKU carries the specs an AI shopping agent actually checks. Your PIM stores the data; Anglera does the work of making it complete enough to get recommended.

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