Use case · Retail & e-commerce
Shoppers are asking an assistant before they open a tab.
The question is no longer "which site do I visit" but "what should I buy". If the assistant cannot read your catalog, it recommends from one it can, and the first time you hear about it is a soft quarter nobody can explain.
- 1Shopperasks an assistant for a sofa under $1,200
- 2Assistantreads a catalog it can parse
- 3Your catalogreal products, real prices, real stock
- 4Review pagethe shopper picks, on your site
- 5Your checkoutyour order, your customer, your margin
What the work is
- Catalog an assistant can parse, down to size, finish and stock
- A review page it can link to, so the shopper picks on your site
- Attribution for the online order and the one finished in store
/llms.txt# Shopping guide Products, prices and stock are live. Preview links let a shopper review picks without purchasing or changing a cart. ## Catalog - [Catalog index](/api/catalog) JSON, paginated: id, price, colour, dimensions, stock - [Product API](/api/products) Lookup by id or SKU ## Handing a selection back /review?picks=<id>~<qty>,<id>~<qty>&budget=<cents> Opens a page where the shopper chooses. Buys nothing.
Also covers
- Furniture & home
- Grocery
- Parts & supply
- Pharmacy & beauty
- Sporting goods
Is this your situation?
Send the address of the site. The first reply has findings in it, not a calendar link.