Sage X3 batch traceability — how to trace products and manage a recall

If a supplier tells you that a batch has a quality problem, how quickly could you establish where it went? Some may still be in the warehouse. Some may have been used in production. Finished goods may already have reached several customers.

Sage X3 batch traceability helps connect those stages. With the right lot management and accurate transaction records, teams can investigate the origin of a product and follow its movement through the business to customer deliveries.

For food manufacturers, distributors and other businesses handling controlled products, that information supports faster investigations, more focused stock containment and a clearer basis for recall decisions.

What batch and lot traceability mean in Sage X3

Businesses often use the words batch and lot interchangeably. Sage X3 uses lot and sub-lot references to identify groups of stock, alongside serial numbers where individual units need identification.

A product code identifies what the item is. A lot reference identifies the particular group involved. Two deliveries of the same ingredient can therefore have different lot identities, expiry dates and quality histories.

Supplier batch references also need to remain connected to your internal references. A supplier’s notification may quote a number printed on its packaging rather than the lot code your own warehouse uses. Sage’s receipt documentation describes recording the supplier lot alongside the internal lot.

This link gives the investigation a dependable starting point. It is particularly useful when products have been relabelled, split across locations or transferred between sites.

Forward and backward traceability answer different questions

Sage X3’s Traceability inquiry provides two directions of investigation:

• Upstream, or backward: which receipts, materials and production activity led to this lot?
• Downstream, or forward: where did this lot go, including related production lots and customer deliveries?

The inquiry can follow recorded events such as purchase receipts, quality control, work orders and deliveries, including movements between sites. Users select the product and relevant lot or other criteria, then inspect the trace and underlying transaction details.

Backward tracking is useful when a customer reports a problem with a finished product. Forward tracking is useful when the first warning comes from a supplier. A complete investigation may need both: identify the source, then check the other products and customers connected to it.

Capture the actual lot at each stage

Traceability relies on the transactions recorded in X3. The system needs the identity of what was received, moved, consumed and shipped.

At receiving, capture the supplier reference and required internal lot details. During production, record the actual material lots consumed and the finished lots produced. At dispatch, record the lot that physically leaves the warehouse.

A bill of materials describes the intended recipe or components. It does not, by itself, prove which batch an operator used on a particular day. Likewise, an order for a product does not prove which lot was picked.

Handheld capture can help operators record those details where the work happens. Our guide to Sage X3 Mobile Automation explains receiving and picking features, including configured lot and serial confirmations. Reliable labels and clear working practices remain essential.

A worked example: from a supplier warning to customer deliveries

Consider this simplified, illustrative example. A supplier reports a concern with ingredient batch SUP-27, recorded internally as ING-271.

The business received 100 kg. Production records show that 40 kg went into finished lot FG-A and 60 kg into FG-B. For this example, each finished unit consumes 0.1 kg and there are no production losses, giving 400 units in FG-A and 600 in FG-B.

The recorded position is:

Starting with the affected ingredient, the team should establish the receipts and actual consumption records, identify both finished lots, then check their stock and delivery history.

The initial investigation now has a defined scope: 350 finished units remain in the warehouse and 650 were delivered to three customers. The quality team can assess which goods require action using that evidence and the nature of the problem.

This is a model investigation, not a claim that one screen automatically performs every recall step. Real cases also need to account for waste, samples, work in progress, rework, returns and any transfers or external storage.

Separate finding the stock from preventing its use

Finding an affected lot is the first step. The business must also control what happens to the stock still under its control.

Sage X3 distinguishes accepted, quality-control and rejected stock statuses, with configurable sub-statuses. These can support the business’s hold, inspection and disposition processes.

However, allocation and issue rules determine how those statuses are used. Sage documents configurations where allocation and physical issue have different permissions. A quality status should therefore be tested against the actual picking, dispatch and production transactions rather than assumed to block every movement.

The team also needs physical control: identify the pallets or locations involved, notify the people handling them and follow the agreed hold or quarantine procedure. A correct system status is most effective when the warehouse understands the same decision.

Use expiry dates and stock rotation alongside traceability

Traceability helps investigate a problem; stock-rotation rules help manage stock before one develops.

X3 supports lot expiry information and allocation sequences including FEFO, or first expiry, first out. With suitable configuration, these help select stock according to shelf life. The Stock by Lot inquiry can show quantities, stock status, allocations and expiry information by lot.

Expiry alone does not determine suitability. A batch within its shelf life may still be under investigation, while a customer may require a minimum remaining shelf life at delivery. The stock policy should reflect those separate requirements.

Support the recall response with a clear evidence pack

The useful output of an investigation is information that people can act on. Our recommended evidence pack includes:

• the affected product, supplier and batch references
• related receipts, production records and finished lots
• quantities and locations still under the business’s control
• customer delivery references, dates, quantities and ship-to details
• stock placed on hold and the person authorising its release or disposal
• customer responses, recovered goods and unresolved quantities

The responsible team determines the required action and communications. X3 transaction records support that decision, but generating a trace does not itself contact customers, recover goods or close an incident.

Returns should retain the relevant identity and follow the inspection process. Crediting a customer and confirming that affected goods have been recovered are different outcomes; both need evidence where they apply.

Common gaps to check before an incident

Several weaknesses can make an otherwise capable system difficult to use under pressure:

• a supplier batch reference has not been captured consistently
• operators record the planned material instead of the lot actually consumed
• stock is moved physically before the system movement is entered
• relabelling, repacking or rework breaks the link to the original lot
• customer deliveries contain incomplete lot details
• a report shows only one site when stock also exists elsewhere
• held stock can still be issued through an alternative transaction

The production process deserves particular attention. Sage explicitly states that the standard Traceability inquiry does not show components used in Assembly or recovered by Disassembly. Test these processes separately if your operation uses them; do not assume they behave like work-order production.

The container-management guide also explains how handling units relate to stock identity. A pallet number helps identify what is together, but the underlying product and lot records still need to be correct.

Prove the process with a mock recall

Choose a real test lot and give the exercise a clear starting point: either a supplier warning or a finished-product complaint. Ask the team to trace in both directions and reconcile the quantities.

Include a partial delivery, a transfer, a return and any relevant production or rework activity. Check that warehouse, production, quality and customer-service staff can find the information they need without relying on one person’s private spreadsheet.

Record how long the exercise takes, where quantities fail to reconcile and which controls need improvement. These findings provide a practical basis for refining the X3 setup and training.

Good Sage X3 batch traceability combines appropriate configuration with consistent capture of the actual movements. It helps the business establish the origin and destination of affected stock, focus its response and retain evidence of what happened.

If you are reviewing your processes, explore our Sage X3 implementation and support services or contact us to discuss a traceability review and practical test.