A pharmacy pack's 2D code read at the scan

The customer asks: Read a pharmacy pack's 2D code at the scan, and refuse an expired pack

• Verdict: Ready, with limits (2)
• Door: Scan source · area: Stock and buying › Batches and expiry
• Recipe: Unit codes at the scan (a scan source)
• Sample: S19 — Unit codes at the scan (a scan source)
• Checked: carried 2026-10-16 · not re-run

What you build

The till reads the pack's GS1 code (item, batch, expiry, serial) at the scan. It is data: no code runs.

Limits

• GS1 codes: not run in the kit (the product's own tests cover them).
• A pack's own serial checked on Desk documents too (receipt, transfer, count): the card units-as-serial-numbers, sample S30; at the till only from the lot iVendNext picks first until POS LANE X row X57, P-SERIALUNITS (one row per serial with its own batch at the till), merges.

Tell the customer

The till reads the pack's code, finds the batch, and refuses an expired pack.

What next

1. Tell the customer the 2 limits above, and write them into the proposal.
2. Follow the recipe: Unit codes at the scan (a scan source).
3. Copy the sample: S19 — Unit codes at the scan (a scan source), 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.

Related needs

• Scan a unit's own barcode or a handset's tag, and refuse a unit already sold — Ready, with limits (3)
• A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
• Insurance co-payment: the insurer pays part of a prescription and the customer the rest — Not yet
• Keep each customer's prescriptions in iVendNext — Ready

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

This card in the kit