Skip to main content
GullySystem
Retail

Batch and Serial Tracking for Supermarkets

Trace goods using batch identifiers or individual serial numbers.

Manufacturing

Does this function belong in your operation?

Use when physical goods require lot history, expiry control or individual identification.

Traceable goods are received, produced or moved.

Dairy, bakery and packaged foods carry batch and expiry dates from receiving to shelf. A recalled lot is traced to the stores and tills it passed through. Staff pull only the affected cartons.

Bring the records the workflow depends on.

  • Item tracking rules
  • Batch or serial identifiers
  • Movement and expiry records

Outputs to check

  • Lot or unit movement history
  • Trace-forward and trace-back report
  • Held or expiring stock list

Follow the batch and serial tracking workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Set tracking rules

    Identify which items require lot, serial or expiry details.

  2. 2. Capture identity

    Record the required reference at receipt or production.

  3. 3. Carry it through movement

    Preserve identifiers during transfer, issue and supply.

  4. 4. Control held stock

    Apply the authorised inspection or restriction decision.

  5. 5. Trace an issue

    Find source and destination records for the affected lot or unit.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Storekeeper

Records the batch at goods receipt and issues the oldest one first.

Quality checker

Holds a batch, releases it, or marks it rejected, and the stock obeys.

Service desk

Types a serial number and sees the sale date, the warranty and every visit made since.

Owner

Asks one question after a complaint: who else received it.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Unknown batch at receipt

Hold the affected quantity until identification is resolved.

Duplicate serial number

Investigate the physical units and source entries before accepting another movement.

Batch put on hold

Prevent the agreed issues or sales and record the authority that later releases it.

Can this work independently?

Traceability requires identifiers on the physical goods and their recorded movements. It can run from controlled imports, but goods receipt, production, stock and sales must preserve the same references. A trace report cannot recover identifiers that were never captured at a handoff.

Systems and records it connects with

  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Stock: Item-location quantities and authorised stock movements.
  • Quality control: Inspection results and authorised hold or release decisions.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.

Configure, test and introduce the workflow.

  • You tell us which items carry shelf life or serials. We write back how each will be numbered.
  • The storekeeper shows how goods arrive. You get a goods receipt screen to try, with a field for the supplier’s lot. Send current stock. A trial import comes back with gaps listed for the team to fill, using whatever batch details exist.
  • Counter and service staff practise. They issue by batch and look up a serial, and you get a trained group and a corrected import.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Tracked items cannot move without required identifiers.
  • Serial references do not duplicate active units.
  • A lot can be traced to its recorded recipients.
Supermarkets

How the business operates.

A supermarket lives or dies between the delivery bay and the checkout lane, where a warm chiller or a wrong shelf label ends in a till dispute. Fresh lettuce, coriander and bananas turn in days. Packaged goods carry dates that cannot be missed. Prices change weekly.

Item master and barcodes

Hold every product with its barcode, department, pack size, unit, supplier and tax setting, and print shelf labels from the same record.

Checkout and weighed items

Scan or weigh at the lane, apply promotions, split tender between cash, card and vouchers, and close each shift against the cash counted.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Item master and labels. Keep every product with its barcode, unit, department, supplier and tax setting, and print shelf-edge labels and weighing-scale labels from the one record. No aisle strip disagrees with the till.
  • Lane billing. Scan or weigh at the lane, apply offers, split payment across cash, card and vouchers, and park a basket when a shopper walks back for a forgotten carton of milk.
  • Weighed and loose items. Price produce, deli and bakery lines by weight through price lookup codes, with a scale label or a lane scale, and keep the net weight printed on the bill.
  • Batch and expiry. Receive chilled, dairy, bakery and packaged lines by batch with a date, then list what falls due by department. Markdown stickers are planned before the oldest stock reaches the front.

Operational bottlenecks to check

Shelf expiry dates are checked by eye

Dairy shelves get a glance each morning. A short-dated carton of yoghurt that should have gone to markdown last week is found by a customer holding it at the lane, not by staff.

Shelf price and till price disagree

A multi-buy offer ends on Sunday. The endcap ticket stays up until Tuesday. The customer points to the shelf edge, the cashier points to the screen, and the manager approves a discount just to clear the queue behind them.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Item set-up

    A new product is added with barcode, department, pack size, tax setting, supplier and shelf location, and the shelf-edge label prints from that same record. The till reads that record too.

  2. 2. Purchase order

    Buyers raise orders to suppliers, distributors and local producers from sales and stock levels, and each order goes out by email or messaging with the agreed case rate. The delivery day is printed on it.

  3. 3. Receiving

    Cartons are counted against the delivery note, short or damaged cases are noted, and chilled goods are probed with a thermometer before the driver leaves. Perishable batches go in with their dates.

  4. 4. Shelf and promotion

    Stock moves from the backroom to the shelf with the oldest batch forward. Price changes and multi-buy offers start and end on their set dates, and shelf labels for the affected bays are reprinted that same day.

  5. 5. Checkout

    Cashiers scan and weigh, apply offers, take cash, card or vouchers and add loyalty points at the belt. At shift end, the cashier counts the drawer and the card terminal batch is settled before the lane closes.

  6. 6. Markdown and wastage

    Items nearing their date are marked down by department with a coloured sticker. What cannot be sold is written off with a reason, and the loss is read against that department’s sales.

Industry reports to connect with

  • Sales by department, product group and hour of the day
  • Batches due to expire this week, by department
  • Wastage by reason, department and week
  • Deliveries received against orders, with short supply

Questions before implementation.

When should supermarkets consider batch and serial tracking?

Use when physical goods require lot history, expiry control or individual identification. Traceable goods are received, produced or moved.

What should we bring to the requirements discussion?

Bring anonymised examples of Item tracking rules; Batch or serial identifiers; Movement and expiry records. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Trace goods using batch identifiers or individual serial numbers. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Traceability does not replace product testing, recall decisions or regulatory obligations.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Tracked items cannot move without required identifiers. Use this check when reviewing the first working version.

Talk to us

Discuss batch and serial tracking for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements