How to make unit pricing a quotable fact for AI shopping answers

When shoppers ask an AI assistant whether a product is a good deal, the assistant rarely reasons about price in isolation. It looks for a comparable, quotable number: a price per unit, per litre, per 100g, per wash, or per month. If your product page states the price but buries the per-unit math, the assistant either does the arithmetic itself (and sometimes gets it wrong) or skips your page for one where the comparison is already spelled out. Unit pricing is one of the cheapest citation assets in ecommerce, and one of the most overlooked.

A raw price of $34 tells an assistant almost nothing about value. A price of "$34 for a 40-pack — about $0.85 per capsule, roughly 20% cheaper per dose than the 24-pack" gives it three quotable facts in one sentence. Assistants are trained to answer comparison and value questions, and unit price is the natural unit of comparison. When the work is already done on the page, the assistant copies the fact. When it is not, the assistant is forced to infer — and inference is where wrong numbers and skipped citations come from.

1. Price only, no unit basis. The page says "$34.00" but never says how many capsules, grams, washes, or servings that covers. The shopper cannot compare, and neither can the assistant.

2. Inconsistent units across a range. One variant is priced per 100g, another per item, a third per box. This forces the assistant to normalise across mismatched bases — work it will often avoid by citing a cleaner page.

3. Unit price stated only in an image or spec sheet. If the per-unit number exists only in a photo of the label, an assistant reading your text never sees it. Put the number in the text.

• State the pack size and the unit count in plain text, near the price: "40 capsules", "500 ml", "12 washes".
• Add the derived unit price yourself: "$0.85 per capsule", "$0.07 per ml". Let the shopper and the assistant both skip the math.
• Keep the unit basis consistent across variants of the same product, so comparisons are apples-to-apples.
• If a larger pack is genuinely cheaper per unit, say so with the number: "about 20% cheaper per dose than the 24-pack".
• Keep it factual, with a date, and avoid inflated value claims — assistants cross-check and drop exaggerations.

Where it fits, express the unit price in your product markup as well as in visible text. A structured unit-price field is unambiguous, while a sentence like "great value" is not. The point is not to game a format; it is to make a real fact machine-readable so it can be quoted accurately rather than guessed. For how auditors score this kind of missing or malformed structured data, see our /faq.

Unit-price clarity helps on its own: shoppers comparing two sizes instantly see which is cheaper per dose. But it also compounds with everything else on the page. Once price, pack size, and unit basis are all clean, quotable facts, they reinforce each other in the same buying answer — and a page that produces several quotable facts is more likely to be the one an assistant leans on.