Technology Deep Dive

Lot Traceability for Small Manufacturers: Run a Mock Recall in Minutes, Not Days

Q: What Is the Difference Between Forward and Backward Traceability?

Backward traceability starts from a finished lot and finds the raw material lots, suppliers and production records behind it. Forward traceability starts from a raw material lot and finds every finished lot and customer shipment that used it. A recall needs both.

Q: How Often Should We Run a Mock Recall?

Many manufacturers run one at least once a year because customers or certifications require it. Running one each quarter, alternating forward and backward traces, catches record-keeping gaps while they are still small.

Q: Do We Need Barcode Scanning for Lot Traceability?

Not on day one, but it helps most at the point where lots are issued to jobs, because that is where handwritten records break down. Start by capturing supplier lots at receiving, then add scanning where your mock recall shows gaps.

Quality manager timing a mock recall with a stopwatch, a lot trace diagram on her tablet beside wrapped pallets

If a supplier flags a bad lot today, could you name every affected shipment before lunch? Here is how to build a trace you can actually run.

By Delta Technologies5 min read

Traceability is not a binder of paperwork. It is a question you can answer while the customer is still on the phone.

A customer calls. One of your suppliers has flagged a bad lot of material, and the customer wants to know whether any of it reached them. On paper, the honest answer is usually "give us a couple of days." Someone pulls the receiving log, then the job travelers, then the packing slips, and tries to connect them by hand.

That is the moment traceability either works or it does not. This guide covers what a lot trace has to answer, what to record at each step, how to test it with a timed mock recall, and what to automate first.

The Two Questions Every Trace Must Answer

A working trace answers two questions quickly and completely:

Backward: for this finished lot, which raw material lots, suppliers, certificates, machines and dates were involved?

Forward: for this raw material lot, which finished lots contain it, and which customers received them?

A recall needs both. Customers usually ask the forward question. Auditors and your own quality team usually ask the backward one.

The Trace Chain

A trace is only as strong as its weakest link. Each link is a moment where one lot number has to be connected to another.

The trace chain, link by link

Receive the lot and its certificate
Issue lots to the work order
Record what was made, where and by whom
Link finished lots to shipments
Run a timed mock recall

If any link is missing, the trace stops there, and someone starts reading handwriting.

What to Record at Each Point

Point	What to record	Where it usually breaks
Receiving	Supplier, supplier lot or heat number, certificate, quantity, date	Certificate filed in a drawer, heat number never written down
Issue to job	Which lot went into which work order, and how much	Material grabbed from the rack with no lot recorded
Production	Work order, machine, operator, date, inspection results	Paper traveler never entered
Split, blend or rework	New lot numbers and their parent lots	Lot identity lost when material is combined
Pack and ship	Finished lot to sales order, customer and ship date	Packing slip lists part numbers, not lots

Two links cause most failures in small plants: issuing material to jobs and linking finished lots to shipments. Both happen in a hurry on the floor, and both are easy to skip when the record is a pen and a clipboard.

Run a Timed Mock Recall

Run the drill in both directions:

Forward. Pick a raw material lot received three to six months ago. Find every finished lot that used it and every shipment that carried those lots.

Backward. Pick a finished lot shipped last quarter. Find every input lot, its supplier and its certificate.

Reconcile. Check that the quantities balance.

Write down every stall. Each place you had to ask a person instead of a record is a gap.

Repeat it every quarter and keep a log: drill time, share of quantity reconciled, and number of stalls. Those three numbers are your most honest traceability metrics, and they show whether each fix worked.

What to Automate First

Automate in the order your mock recall exposes gaps:

Supplier certificates into lot records. Certificates arrive as PDFs by email. Capturing their key fields automatically removes a slow, error-prone typing job and puts the data where the trace can use it.

Lot capture at issue. A scan or a pick from a short list when material goes to a job is the single biggest improvement for most plants.

Finished lots on the shipment. When the packing slip carries lot numbers, the forward trace becomes a report instead of a project.

A trace report anyone can run. The test is simple: could a new quality tech answer the customer's question without asking anyone?

Alongside the drill log, track two more numbers each month: lots received without a certificate on file, and hours spent keying certificate and lot data. Both should fall as the first two automations go in.

What Published Traceability Projects Report

All four of the published case studies here started from paper or disconnected records, and two give figures. Published industry case studies from software firms show where the time goes. The figures below are self-reported by the firms that published them, and each describes a single project rather than an industry average.

Industry benchmark

Published results from other firms

Days → secondsfor recall and traceability reporting at a family-owned animal nutrition manufacturer, where a trace once took up to two days
30+ hrsa month saved by a coated steel supplier that stopped keying certificate data for 300+ incoming lots by hand
5-10 minper lot was the manual certificate entry time before automation, for 15-20 properties per lot

Self-reported results from case studies other software firms have published. See Sources & method below.

Days to seconds. A fourth-generation, family-owned animal nutrition manufacturer ran scale tickets and production orders on paper and re-keyed them, and tracing finished goods back to raw material lots could take up to two days. After moving production, scanning and lot tracking into one ERP, it reported recall and traceability reporting going from days to seconds.

Certificates without typing. A coated steel coil supplier receives 300+ lots of material a month and records 15-20 mechanical and chemical properties for each. Staff spent 5-10 minutes per lot keying that data. Automating certificate capture saved 30+ hours per month and eliminated the potential for data entry errors.

Paper batches. A fast-growing energy supplement maker tracked five-day production batches on paper, so auditing a batch meant physically hunting down the files. It moved batches into bills of materials and work orders that track every stage. The case study reports an auditable process without the paperwork, but gives no figures.

Six systems, one trace. A contract distiller with six separate systems across distilleries, warehouses, logistics and compliance consolidated them into one ERP with lot traceability from receipt through shipment. No figures are given.

Where does your team sit? The 14-day Ops Efficiency audit measures it. Book the audit

Start With One Drill

Run a forward mock recall this week and time it honestly. If it takes longer than you would want to explain to a customer, you already know your first project.

Want help with the first one? Book a systems review and we will walk your trace chain with you, from the receiving dock to the shipping door, and show where the records break. You can also see how we work with manufacturers.

Sources & method

Figures are self-reported results from case studies other software firms have published. Delta did not produce these results. Where a source says “up to”, so do we.

FAQ

Frequently Asked Questions

What Is the Difference Between Forward and Backward Traceability?

How Often Should We Run a Mock Recall?

Do We Need Barcode Scanning for Lot Traceability?

Written By

Caylan Wilcox

Founder, Delta Technologies · Operator-first builder

I'm Caylan, founder of Delta Technologies. It's a privilege to build the operating systems our clients' businesses depend on, for companies that have outgrown spreadsheets and disconnected SaaS.

Read Full Author Bio

Start a free AI diagnostic →

Private · For Delta Insights editors

Tell Us What You’re Seeing

How are customer expectations changing in your industry? Share your thoughts privately with Delta Insights.