← All posts

What an AI needs to answer "the cheapest one that meets my specs" in sale season

From Black Friday to year-end, more shoppers ask an AI assistant what's cheapest right now for their requirements. A checklist for making sure your product pages carry what it needs to answer.

2 min read

By ZAG

日本語版 →

Black Friday through year-end is when the most people shop by comparison. More of them now hand that comparison to an AI assistant instead of opening search results one by one.

What's the cheapest portable power station with at least 1,000 Wh?

To answer that one line, the assistant needs at least four things: whether the specs meet the requirement, what the price is, whether it's in stock, and how long the price lasts. If any one of them can't be read, the product drops off the shortlist, even when it qualifies.

Here are the four things to check on your product pages before a sale. Every example is fictional.

1. Specs: can they be compared?

To filter on "at least 1,000 Wh", capacity has to be written as a number with a unit. If it only appears in the product name, as in "High-capacity 1024Wh model", an assistant may not be able to treat it as a condition.

We covered how to split specs into value, unit and condition in the previous post.

2. Price: tax-inclusive or not, and for which model?

Sale pages often look like this:

  • "Up to 50% off" appears only inside a banner image
  • one page covers several model numbers but shows a single price
  • regular and sale prices sit side by side, and only the surrounding copy says which is current

People work it out from the image and the context. For an assistant, "which model costs how much" is left undecided. The baseline is a tax-inclusive price, as a number, for every model number.

For a fictional portable power station, EXAMPLE BP-U70:

Field Value
Model number BP-U70
GTIN 2001234567893
Price (incl. tax) ¥89,800
Regular price (incl. tax) ¥109,800

Product, model number, GTIN and prices are all fictional.

3. Stock: can it be bought now?

A cheap product that meets every requirement is no use as an answer if it's sold out. If stock is shown only as a "low stock" icon, an assistant may miss it. Write the stock status as text.

4. Period: how long does the price last?

Sale prices end. Without an end date, the old price can linger in answers after the sale is over. Write it as a date and time, such as "until 23:59 on December 1".

Update the structured data too

If your product pages carry schema.org Product and Offer markup, update it for the sale as well. price and priceCurrency, availability, and priceValidUntil map directly onto points 2–4 above. When the page and the structured data disagree, an assistant has no way to tell which one is right.

Pre-sale checklist

  • Comparable specs are written as value and unit
  • Each model number has a tax-inclusive price as a number (not only inside an image)
  • Stock status is written as text
  • The sale price has an end date and time
  • Structured data matches what the page shows

These are the things that slip when pages are rebuilt for every sale. Add one hour to your sale prep to reread your product pages the way an assistant would.