Trace a Product

Find every lot of a product or batch code at your sites, back to the delivery it came on, its papers, what happened to it and any recall.

2 min readUpdated Today
tracetraceabilitytrace a productwhere did it come frombatch codebatch numberlot codeone step backmock recallrecalllotsexportcsvehoinspectionaudit pack

What a trace shows

Each product you receive with Batch Traceability on is a lot. A trace follows a lot back to where it came from and forward to what happened to it:

  • the supplier, the site, the day it came and who received it

  • the readings taken at the door

  • its papers: purchase order, delivery note, invoice, credit note

  • what happened to it since: used up, binned, frozen, corrected, voided, and by whom

  • any recall that names it, with the actions taken on that lot

On the web

  1. Go to Suppliers > Batch Traceability and click Trace a product.

  2. Trace by Product (such as "double cream") or by Batch code (part of a code works).

  3. Open a lot and choose its Trail tab.

The Lots tab is the full register: search a product or code, filter by site, supplier, status or use-by dates, and Export CSV for a spreadsheet. The export has no prices. A lot that came with no code shows as No code, and a code search never matches it.

From a product: open it from the Bought-in products view of the allergen chart, and its Deliveries tab lists each time it came, where, the code, the date and what happened to it.

In the app

In the app's inspection mode, open Traceability & Recalls and search a batch code. Tap a batch to see its trail: the delivery, the readings, the papers, what happened and any recall. Prices never show here, whoever holds the phone.

For the inspector

Tick Batch traceability in the Audit Pack for the lots received in the period, what happened to each one, and each site's daily use-by checks.

Ask Paddy

Ask "where did the chicken thighs come from?" or "trace batch L88213" and Paddy lists each lot with its supplier, site, delivery, papers and what happened to it. It only reads your own sites.

Practise it. Pick a product at random once a year, trace it, and time how long it takes to find every lot. That is a mock recall. If a lot is missing its code, photograph the label next time it comes.

What a trace cannot show is which customer ate it: Paddl follows a product to the day it was used up, binned or frozen. For a recall, see Recalls & Batch Traceability.

Try Paddl free for 30 days

Compliance, training, and daily operations in one platform. Nothing is charged until the trial ends.

Start Free TrialView all features

Related Articles

Operations

Routines and Checklists

See today's tasks across your sites, build recurring checklists with rich field types, reorder them, link SOPs, schedule them every day, week or few weeks, assign them, and change them later.

Operations

Attaching reports and certificates to a routine

Add a Document upload field to a routine so a contractor's report or certificate is filed in Documents and counts as evidence on the EHO visit page and in the audit pack.

Operations

Scheduling checks around service

The routine editor shows the quiet windows in each site's day so a check lands in a lull, not the lunch rush.

Operations

Late and missed tasks

When a task becomes overdue, when it becomes missed, what "missed in the busiest hour" means, and how to resolve one.

Back to Operations