Alexa shows 365 days of price history: keep deal clips honest
Amazon says Alexa for Shopping shows price history up to 365 days, so price claims are easy to check. Keep prices out of the frames and list claims for review.

Assume a shopper can check your price claim. Amazon's own announcement says Alexa for Shopping offers deal alerts, price history up to 365 days, and automatic purchase at target prices. A line such as "lowest price of the year" in a video can therefore be compared with real history in seconds. Keep claims you cannot prove out of the clip, and keep the price in text you control.
What does Amazon say?
This is Amazon's description of its own shopping tools. It does not describe what other retailers show.
| Topic | What the post says |
|---|---|
| Dates | October 6-7, 2026, "48 hours of exclusive deals" |
| Deal timing | New deals three times daily: midnight, 8 a.m. and 1 p.m. PDT |
| Alexa for Shopping | Deal alerts, price history up to 365 days, auto-purchase at target prices |
What belongs in the video and what does not?
Put the product action in the video and the price in the listing or caption text. A clip that says "now $24" is wrong the moment the price moves. The same holds for "half price" and "lowest ever". If you must show a price on screen, render that clip last, from the data, and render a new one when the data changes.
The Format API can bind an output_schema to a run, so the receipt returns typed JSON beside the video. Ask for a claims array that lists every factual statement the clip makes. The run fills that list itself, so treat it as a checklist for a human to compare with your price records before publishing, not as proof.
{
"instruction": "15-second 9:16 demo clip. List every factual claim you make in the claims output.",
"input": { "product_image_url": "https://cdn.example.com/kettle.jpg" },
"output_schema": {
"name": "deal-clip/v1",
"strict": true,
"schema": {
"type": "object",
"properties": {
"claims": { "type": "array", "items": { "type": "string" } }
},
"required": ["claims"],
"additionalProperties": false
}
}
}How do I check the finished clip?
Pull stills from any on-screen text with video frames, using at[] for the seconds where a price or badge shows. Compare them with the current price. Keep the check cheap and automatic when you have many clips, and see the exact output_schema rules in the structured output docs, because a schema outside the supported subset returns 400 output_schema_invalid and nothing runs.
How do I keep a deal clip honest?
A deal clip is only as good as the number in it. Make the number easy to check.
- Put the price on a text card, not inside generated footage.
- Date the card, so an old clip is easy to spot.
- Write down where the price came from.
- Remove the card or retire the clip when the deal ends.
Sources
Related posts
More in Use cases
- Animatic on Wan 3.0: six 5 s shots, approve, redo, upgrade
Six 5-second Wan 3.0 shots at 480p cost $1.875 in total, the same as one 30-second job. Split by shot so each frame can be approved alone.
- App demo video through the sume-mobile-app-ugc Format: what to send
Call a catalog Format at the sume handle for an app demo video. Read its io profile first, send screens and copy, cap the spend, and test the receipt.
- App Promo Half-Banner: A Headline Still Over a Screen Recording
Stack a headline image above an app screen recording in one 9:16 shot with timeline compose: layout ratio, overlay mode, output size and a $0.02 price.
- App Store preview poster frame defaults to second 5: check it
Apple says an app preview's default poster frame is at 5 seconds and previews show before screenshots. Pull frames 0 and 5 with Sume video frames before upload.
Written by Sume