A warning at the scan that the cashier taps past

The customer asks: A warning when an item is scanned (another batch has less shelf life), with the cashier tapping to carry on

• Verdict: Ready, with limits (5)
• Door: Capture on an event · area: Till controls and approvals › Questions and details during the sale
• Recipe: A value captured at the scan, and a code before a new customer (capture)
• Sample: S20 — Warranty capture and a member code (capture)
• Checked: read 2026-10-16 in recipes/capture.md and the capture contract · a confirm on a till not run

What you build

A capture on scan. Your service looks up the item's other batches in the store over the record API, then answers confirm with your sentence ("This item has a batch with less shelf life in the store. Add it anyway?"). The cashier taps Yes once and the item is added.

Limits

• It is a question, not a notice: one tap, and No leaves the item off. POS LANE X row X60, P-CAPTURE4 (a notice answer at the scan: the sentence shows and the item is added with no tap) removes the tap when it merges.
• The call is made before the line is added, and an ordinary item scan carries no batch: you can say the item has shorter-dated batches, not that this lot is the longer one, unless the scanned code names the batch. The lot is chosen later, at the batch pick (card first-expiry-first-out).
• Online, your service answers. When it is down or offline, the answer you declared applies (allow_and_flag lets the line on and flags it for review), so the warning is missed then.
• Your service reads other batches over the record API: allow for the seconds it takes (the scan waits up to the time you declared).
• Not run: a confirm answer on a till.

Tell the customer

Scanning an item with a shorter-dated batch in the store makes the till ask the cashier once, and one tap adds the item.

What next

1. Tell the customer the 5 limits above, and write them into the proposal.
2. Follow the recipe: A value captured at the scan, and a code before a new customer (capture).
3. Copy the sample: S20 — Warranty capture and a member code (capture), and change it.
4. Build and test it on your sandbox (request one if you have none; what is on it).
5. Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
6. Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.

Test it with your service stopped: the till applies the answer you declared for when it is down.

Related needs

• A beep and a yes-or-no question when the cashier scans an item we flagged — Ready, with limits (2)
• A one-time code sent to the customer before a new customer is made at the till — Ready, with limits (2)
• An answer for the cashier during the sale: a message, or a seal number, a reference or a warranty card number added to the sale — Ready, with limits (3)
• Check a product's warranty at the till — Ready, with limits (3)

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit