Purpose
This guide explains how to configure GS1 functionality, manage recalls, understand the shopper experience, and review scan activity.
Overview
GS1 functionality allows supported Scan&Pay devices to read product information encoded in a barcode, including expiration dates and batch or lot numbers.
A GS1 barcode can contain several pieces of information:
| Barcode information | Used for |
|---|---|
| Product identifier (GTIN) | Finding the corresponding product in the catalog |
| Expiration date | Determining whether the encoded date has passed |
| Batch or lot number | Checking whether the product belongs to a recalled batch |
With expiry and lot management enabled, the device checks this information when a shopper scans a product; it identifies the product and applies the location’s expiry and recall settings.
- If the product passes the checks: it follows the normal purchasing process, including existing pricing, tax, promotions, and other purchase restrictions.
- If it is expired or recalled: it is blocked and the shopper sees the applicable message.
Reading GS1 barcodes and blocking products are separate functions. Turning off expiry and lot management does not turn off GS1 barcode reading. Expired products and products matching an active recall are blocked from being added to the cart, and the shopper sees a message configured by the Operator.
Supported Devices and Barcode Format
The Scan&Pay scope includes:
- V5: Gen3, MM6, and Mini
- MobileMarket: PicoCooler, PicoMarket, and PicoCoffee
- Barcode format: GS1 DataMatrix
A barcode must contain the relevant information for the corresponding check. The device cannot read an expiration date that is not encoded in the scanned barcode.
Process
One-Time Scanner Setup: Gen3, MM6, and MM6 Mini
Before using GS1 functionality on Gen3, MM6, or MM6 Mini kiosks, a 365-provided configuration barcode must be scanner once at each kiosk to enable the barcode scanner to read GS1 barcodes.
Each kiosk scanner must be configured individually. Enabling expiry and lot management in ADM does not replace this scanner setup step.
- Scan the configuration barcode below at each applicable kiosk. A distinct chime should sound.
- Verify that the kiosk reads a supported GS1 product barcode before making the functionality available to shoppers.
Enable Expiry and Lot Management
Configure each location separately. The expiry and lot management setting defaults to Off.
| Setting | Expected Behavior |
| Off | GS1 barcodes are still read, but this feature does not block expired or recalled products or show its warning messages. |
| On | Expiry and recall checks apply, and blocked products display the configured shopper message. |
To enable expiry and lot management:
- Sign in to ADM.
- Open the applicable location’s Location Summary page.
- Find Enable GS1 Expiry & Lot management and enable the setting.
- Once enabled, the Expired item message and Recalled item message fields will appear. Use short messages that explain why the item cannot be purchased and what the shopper should do next. Both fields must contain a message; follow the character limit displayed in ADM.
- Configure GS1 Decrement Inventory according to the inventory process. (See the Inventory Handling section below for more information.)
- Save the location.
- Allow the configuration to synchronize to the devices, then verify the behavior with representative test products.
Inventory Handling
GS1 Decrement Inventory is a separate setting beneath the expiry and lot management control. It is visible only when expiry and lot management is enabled, and defaults to No.
| Option | Expected behavior |
|---|---|
| No | No automatic GS1 inventory decrement occurs. Use the established stock-removal process. |
| Yes | Qualifying expired or recalled scans trigger an inventory reduction under the supported GS1 workflow. |
The inventory requirements specify a reduction of one unit per qualifying scan, with removal reasons for expired or recalled stock. Before enabling automatic decrement, confirm the supported Operator scan workflow with 365. Ensure staff understand how to avoid recording the same physical removal twice.
A blocked shopper scan, an inventory adjustment, and physical removal from the shelf are different events. Review the inventory record before making an additional manual adjustment.
How Expiration Dates are Checked
The device compares the encoded date with the current business date in the store or device’s configured timezone.
The configured rules are:
- Use the expiration date when present.
- If no expiration date is encoded, use the encoded best-before date when available.
- Do not use the production date as an expiration date.
- A date equal to today does not trigger this expiry rule.
- If neither an expiration date nor a best-before date is encoded, the feature cannot determine expiry from the barcode.
- An invalid encoded date follows invalid-barcode handling.
For example, a product with an encoded expiration date of September 7 is blocked when scanned on September 8. A product dated September 8 does not trigger the expiry block on September 8.
Continue normal shelf checks and stock rotation. A successful scan does not confirm that a product was stored correctly or is suitable for sale.
Create a Product Recall
Recalls are configured by the Operator in ADM. A batch number in a barcode identifies the batch; it does not by itself indicate that the batch has been recalled.
To create a product recall:
- Open Admin > Recalled Product Management.
- Select Create New.
- Enter a descriptive name, such as “Sandwich Recall — Batch A104.”
- Select Choose Products.
- Search by product name or scancode.
- Select the affected products, then select Done.
- Set Enforce Against Batch/Lot:
- No: Apply the recall to the selected products without limiting it to specific batches.
- Yes: Apply the recall to the specified batches or lots for each selected product.
- If Yes was selected, enter the affected batch or lot values for each product. Multiple values can be entered as a comma-separated list.
- Select Save.
The recall is created with an Active status.
Recall records use products from the Organization’s catalog. Verify expiry and lot management is enabled at the locations where blocking is required, and confirm devices have received the updated recall data.
Product-Wide Versus Batch-Specific Recalls
| Recall type | When to use it | Example |
|---|---|---|
| Product-wide | All units of a selected product are affected. | All units of a particular sandwich |
| Batch-specific | Only identified batches or lots are affected. | Sandwich batches A104 and A105 |
Enter batch and lot values carefully, preserving leading zeros and letters. Confirm that each value matches what is encoded in the barcode.
For a batch-specific recall, a scan without the required batch information cannot establish a match to that batch. Remove affected stock using the normal recall process as well.
Review or Edit a Recall
- Open Admin > Recalled Product Management.
- Locate the recall in the list, and select the row to open it.
- Review or update the name, products, batch enforcement, or batch assignments.
- Select Save.
End a Recall
End a recall only when the restriction should no longer apply.
- Open the recall record.
- Select End Recall.
- Review the confirmation.
- Select End Recall again to confirm.
The record changes to Ended and remains visible in the list.
Once devices receive the update, that recall no longer blocks the affected products or batches. Other active recalls, expiry checks, and purchase restrictions may still apply.
Ending a recall does not change the expiration date encoded on a product.
What the Shopper Experiences
When a product is eligible for purchase:
- The shopper scans the barcode.
- The device checks applicable restrictions.
- The product is added to the cart.
When a product is expired or recalled:
- The shopper scans the product.
- The device identifies the expiry or recall condition.
- The product is not added to the cart.
An Item Expired or Item Recalled message appears with the Operator’s configured instructions.
- The shopper acknowledges and dismisses the message, then can continue with other products.
The message requires acknowledgement; it does not automatically disappear. Dismissing it does not authorize the blocked product for purchase. Scanning the blocked item again applies the same check.
Review the Expired/Recalled Product Scan Report
Use this report to identify expired or recalled products that shoppers attempted to scan.
- Open Reports in ADM.
- Locate Expired/Recalled Product Scan Report.
- Select the location(s).
- Select the date range and time criteria.
- Run the report.
- Review the events and arrange an onsite check where needed.
A report row records a scan event. It does not prove that the product was purchased or physically removed from the market. Repeated scans may represent repeated attempts involving the same item, so the number of rows is not a confirmed count of affected physical units.
| Report field | Meaning |
|---|---|
| Location Name | Where the scan occurred |
| Kiosk | Device that recorded the scan |
| Trans Date/Time | Date and time associated with the scan event |
| Trans ID | Transaction context associated with the scan |
| Product Name | Product identified from the barcode |
| Scancode | Product identifier recorded for the scan |
| Event Type | Expired or Recalled |
| Expired Date | Encoded expiration date for an expired scan |
| Recalled Batch | Scanned batch or lot identifier, when available |
Exports and Scheduling
Where available, use the report’s Excel or PDF output to share results. Use ADM’s report-scheduling options for recurring review. Events recorded while a device is offline may appear after it reconnects and synchronizes.
Troubleshooting
| Issue | What to check |
|---|---|
| An expired product is not blocked | Confirm the location setting is On, the device received it, and the scanned barcode contains a supported expiration or best-before date. Check the configured date and timezone. |
| A recalled product is not blocked | Confirm the recall is Active, the correct product is selected, batch values match where enforced, and the device has synchronized. |
| The barcode is read, but the product is not found | Verify the product’s catalog scancode and location availability. If matching still fails, provide 365 Support with the barcode example. |
| ADM will not save the messages | Confirm both messages are populated and within the displayed character limit. |
| The wrong message appears | Review the saved location messages and configuration synchronization. |
| Inventory did not decrease | Check GS1 Decrement Inventory and confirm the scan used the supported adjustment workflow. |
| Inventory decreased unexpectedly | Review repeated scans and manual adjustments for duplicate recording. |
| An event is missing from the report | Check location, date, and time filters, then confirm device connectivity and synchronization. |
| A product is still blocked after a recall ends | Check synchronization, other active recall records, and the product’s encoded expiry date. |