Overview
Batch tracking is the operational and regulatory requirement to know, for any unit of stock at any point in its journey through the supply chain, which batch or lot it belongs to, where that batch came from, how it was processed, where it has gone, and — critically — which customers received products from it. When a quality problem is identified, when a supplier issues a recall notice, when a regulatory inspection demands traceability evidence, or when a customer dispute requires proof of what they received, batch tracking is the system that answers these questions. Without it, the answers require manual investigation across paper records, email threads, and warehouse systems that may not have recorded the information in a retrievable form.
For businesses where batch tracking is a regulatory requirement — food manufacturers, pharmaceutical producers, chemical processors, medical device manufacturers — the absence of adequate lot traceability is a compliance failure with direct legal consequences. For businesses where it is a commercial requirement — components manufacturers whose customers require traceability certificates, food retailers whose supply chains are subject to audit — it is the evidence that customer relationships and contracts depend on. For any business handling products where defects, contamination, or quality failures have the potential to harm customers or generate recall liability, it is the risk management infrastructure that limits exposure when something goes wrong.
We build custom batch tracking software for manufacturers, processors, distributors, and importers across food and beverage, pharmaceuticals, chemicals, electronics, automotive components, and any industry where lot-level traceability is a regulatory, commercial, or operational requirement — integrated with the ERP, WMS, and production systems that batch data flows through, and designed for the specific traceability requirements of each industry and each business.
What Batch Tracking Software Covers
Batch creation and registration. Every batch has an origin — a purchase from a supplier, a production run in the facility, a processing operation that combines input batches into output batches. Batch registration captures the information that defines the batch at its creation: the batch number or lot number, the product, the quantity, the origin (supplier batch number, production order, processing date), the production or receipt date, the expiry date where applicable, and any quality or certification data that the batch carries.
Supplier batch data — the lot numbers, production dates, and certification data on incoming goods — is captured at goods receipt, either by scanning GS1 barcodes that encode this information in the barcode itself or through manual entry of the lot information from delivery documentation. The supplier's lot number and the internal batch number are maintained together in the batch record, supporting both internal traceability and the supplier traceability that regulatory audits and supplier recalls require.
For manufactured or processed products, batch creation is linked to the production order — the batch number generated when the production order is opened, the input batch numbers recorded as materials are issued to production, and the output batch details recorded when the production run is completed. The production batch record captures the full input-to-output traceability that process manufacturing requires.
Batch genealogy and composition. Manufacturing and processing operations typically combine materials from multiple input batches to produce an output batch. The relationship between input batches and output batches — the batch genealogy — is the core of manufacturing traceability. A food product may contain ingredients from dozens of supplier lots. A pharmaceutical batch may be produced from multiple sub-batches of active ingredient and excipients. An electronic assembly may incorporate components from multiple component lots.
Batch genealogy tracking maintains the complete tree of relationships between batches — which supplier lots were used in which production batches, which production batches were combined in which assembly batches, which assembly batches went into which finished goods batches. The genealogy tree supports the forward traceability question (if this ingredient lot is recalled, which finished product batches does it affect?) and the backward traceability question (which supplier lots and production batches contributed to this finished product batch?).
Stock management by batch. Inventory management at the batch level — knowing not just how many units of a product are in stock, but which batches they belong to, where each batch is located, how many units of each batch remain, and when each batch expires — is the foundation of batch-aware inventory operations.
FIFO (First In First Out) and FEFO (First Expiry First Out) stock rotation is only possible when the inventory system tracks stock at the batch level and presents the correct batch for picking based on the configured rotation rule. FEFO picking — essential for food, pharmaceutical, and any product with an expiry date — ensures that the oldest or earliest-expiring stock is picked first, reducing the waste and compliance risk of expired stock remaining in the warehouse while newer stock is picked instead.
Batch-level stock alerts — approaching expiry alerts that surface batches within a configured number of days of expiry date, low stock alerts at the batch level where a specific batch has limited remaining quantity — give stock managers the visibility to manage batch-level stock issues before they become operational problems.
Lot allocation to orders. When a batch-tracked product is picked for a customer order, the specific batch allocated to that order is recorded — creating the link between the customer delivery and the batch that was supplied. Batch allocation at the point of picking, confirmed by barcode scanning, produces the customer-to-batch traceability record that customer complaints, recall notifications, and traceability audits require.
Lot-specific allocation — where a customer has requested or been allocated a specific batch, or where regulatory requirements mandate that the batch supplied to each customer is recorded — is managed through the batch allocation rules that the order management workflow applies. For pharmaceutical distribution, for example, the batch number supplied to each pharmacy or hospital is a regulatory record that must be maintained.
Quality management integration. Batches may be subject to quality holds — held pending inspection of an incoming goods receipt, held following an in-process quality failure, held pending the results of analytical testing. Quality hold status in the batch tracking system prevents held batches from being allocated to orders or picked for despatch until the hold is released by the quality function.
Quality test results — the analytical results, microbiological results, dimensional measurements, or other test data that determine whether a batch meets specification — are stored against the batch record, providing the quality evidence that the batch carries throughout its life in the system. Certificate of Analysis (CoA) generation from the batch quality data produces the document that customers frequently require with pharmaceutical, chemical, and food ingredient deliveries.
Recall management. When a batch needs to be recalled — because of a quality failure identified internally, a supplier recall notification, or a regulatory recall instruction — recall management identifies the scope of the recall and manages the operational response.
Forward traceability — starting from the affected input batch and tracing forward through all production batches that used it and all customer deliveries that included those production batches — identifies every customer who received product derived from the recalled batch. The recall scope is calculated automatically from the batch genealogy records rather than requiring manual investigation across multiple systems.
Recall notification management — generating the customer notification list, managing the notification workflow, tracking acknowledgements and returns — is handled within the recall management module with the documentation and audit trail that regulatory bodies require evidence of during recall investigations.
Mock recall exercises — the periodic drills that food, pharmaceutical, and other regulated industries require to demonstrate recall capability — are conducted through the same recall management functionality with a drill designation that prevents operational consequences while producing the evidence of recall capability that regulatory audits examine.
Batch documentation and certificates. The documentation that accompanies batches — supplier certificates of conformance, analytical test reports, certificates of origin, organic or Fairtrade certification documents — is stored against the batch record and retrievable when customers, auditors, or regulatory bodies request it. Certificate of Analysis generation from batch quality data produces the customer-facing quality document on demand rather than requiring manual assembly of test results into a formatted document.
For food businesses, the product information that HACCP and food safety management requires — the allergen status, the country of origin, the certification status — is maintained at the batch level where this information varies by batch (e.g., different origin countries for different purchase lots of the same ingredient).
Industry-Specific Traceability Requirements
Food and beverage. EU food traceability regulation (EC 178/2002) requires food businesses to be able to identify the suppliers of every food ingredient and the customers to whom food products have been supplied — the one step back, one step forward traceability requirement. For processed food, full chain traceability through the production process is required by retailer codes of practice and by the BRC, IFS, and FSSC 22000 food safety standards. Allergen traceability — knowing which batches contain which allergens and which customers have received allergen-containing products — is a specific traceability requirement with consumer safety implications.
Pharmaceuticals and medical devices. Pharmaceutical batch traceability is a GMP requirement — EU GMP Annex 11 and the broader GMP framework require batch records that capture the complete history of each batch from materials receipt through manufacturing through release through distribution. Serialisation requirements for pharmaceutical products — the unique identifier on each saleable unit that enables item-level traceability — extend batch tracking to the individual pack level.
Chemicals. REACH regulation traceability requirements for chemical substances and mixtures, combined with the Safety Data Sheet obligations that require accurate identification of the substance composition, make batch tracking a regulatory necessity for chemical manufacturers and distributors. ADR hazardous goods documentation requires batch-level identification of the hazardous substance.
Electronics and automotive components. Customer-mandated traceability requirements in the electronics and automotive supply chains — typically requiring the component lot numbers used in assemblies to be recorded and reportable — reflect the liability implications of component failures in safety-critical applications.
Integration Points
ERP systems. Exact Online, AFAS, SAP — batch tracking integrated with ERP inventory and production modules. Batch records created in the ERP from production order completion, lot numbers carried through ERP goods movements, batch valuation reflected in inventory accounting. For SAP, batch master records and batch classification integrate with the SAP batch management functionality.
Barcode scanning apps. Batch-aware scanning workflows that capture lot numbers at every scanning event — goods receipt scanning that records the supplier lot number, pick scanning that records the lot number of each product picked. Integration between the scanning app and the batch tracking system ensures that scanning events update the batch-level inventory records in real time.
Quality management systems. Quality hold status and test result data from the QMS integrated with batch tracking — holds applied in the QMS immediately reflected in the batch tracking system's availability status, test results stored in the QMS linked to the batch record in the tracking system.
WMS platforms. Batch-aware WMS operations — FEFO pick sequence driven by batch expiry data, batch-specific put-away location rules, batch-level stock inquiry from WMS interfaces — integrated with the batch tracking system's batch data.
Customer portals and EDI. Batch number information in customer-facing despatch notifications — the batch numbers despatched against each order line included in the despatch note data that EDI transmissions and customer portals present to the customer. Traceability data provided to customers through API or data feed for customers who integrate supplier batch data into their own traceability systems.
Technologies Used
- React / Next.js — batch management interface, traceability enquiry views, recall management dashboard, certificate generation interface
- TypeScript — type-safe frontend and API code throughout
- Rust / Axum — high-performance batch genealogy traversal, recall scope calculation, large-volume traceability query processing
- C# / ASP.NET Core — ERP integration, QMS connectivity, Certificate of Analysis generation, EDI batch data exchange
- SQL (PostgreSQL, MySQL) — batch records, genealogy relationships, allocation history, quality data, recall records
- Redis — batch availability state cache, recall calculation coordination, real-time stock alert processing
- GS1 barcode parsing — lot number and expiry date extraction from GS1-128 and GS1 DataMatrix barcodes
- Exact Online / AFAS / SAP — ERP batch and inventory integration
- OpenXML / PDF generation — Certificate of Analysis, batch documentation, recall notification generation
- REST / Webhooks — scanning app, WMS, QMS, and ERP integration
- SMTP / push notifications — expiry alerts, quality hold notifications, recall initiation alerts
Traceability as Risk Management
The cost of batch tracking software is easy to quantify — the development investment, the integration work, the ongoing maintenance. The cost of inadequate batch tracking is harder to quantify in advance but very easy to quantify after a recall, a regulatory inspection, or a customer dispute reveals that the traceability record is incomplete. A food recall that requires every customer who received product from a specific ingredient lot to be notified, conducted without a batch tracking system that can identify those customers automatically, involves manual investigation across despatch records, invoices, and warehouse records that may take days and may still produce an incomplete list. The regulatory, reputational, and commercial consequences of an incomplete recall follow.
Batch tracking software that maintains the complete chain of custody from supplier lot to customer delivery converts the recall investigation from a manual reconstruction exercise into a database query. The recall scope is known within minutes. The customer notification list is generated automatically. The evidence of traceability capability is available for the regulatory inspection.
Traceability From First Supplier to Final Customer
Complete batch traceability — knowing exactly which supplier lots are in any finished product batch, and exactly which customers have received any finished product batch — is the operational capability that product liability management, regulatory compliance, and customer confidence require. Custom batch tracking software built for the specific products, processes, and traceability requirements of the operation is the infrastructure that makes this capability reliable rather than theoretical.