Product facts are stored as discrete attributes and published into structured data and the merchant feed from one source.
“Available in S, M and L, made from European flax” reads as text to a model and as data to nobody. It cannot be compared, filtered, or cited against another product.
Each specification is stored as its own value, so an agent answering a shopping question can read them individually.
"Available in S, M and L" — a sentence a model has to parse and may get wrong.
Size = S, Size = M, Size = L. Each separately readable, comparable and citable.
Nothing in the code enumerates attribute names, so your categories define their own.
As a sentence
As attributes
Return policy, availability and price are emitted into the product page markup and the merchant feed from the same rows, so an agent comparing the two finds one answer.
Each product is compared with its category peers and the audit lists the attribute keys similar items declare and this one is missing.
Generate the missing descriptions, alt text and meta across a whole collection at once. Each one lands as a draft with the diff shown.
4 colours · in stock
$1286 colourways · machine washable
$96A draft stays a draft until somebody reads it. Hover one to see what the model wrote.
Woven from European flax, cut relaxed through the body, and washed soft before it ships.
hover to readThrown in stoneware with an unglazed foot, sized for two cups and safe in the dishwasher.
hover to readWaxed cotton with a leather base, 38 litres, and a strap that survives an airport.
hover to readNo. It proposes an action and waits. The assistant can read every module from one database, but it writes a pending action rather than executing one — a person approves.
AI assistants quote product facts. Litestore publishes them and flags the products that are missing any.
How ready your products are
Ready 68%Similar products list 3 things this one is missing
Material
European linen
Size
S
Size
M
Size
L
Fit
Relaxed
Care
Machine wash 30°
Three sizes are stored as three separate values, not one line of text.
Attributes, intent, recommendations
Your categories define their own
Markup and feed agree
The audit ships with the code
Missing attributes land in the same queue as everything else that needs doing.
Generated copy is saved as a draft and shown as a diff before it publishes.
Define options once and the variants are generated, so size and colour stay in sync.
Revenue and conversion are computed from the rows that fulfilled the orders.
The audit and the structured output are part of the app from the first clone.