A resin certificate, a molding order, and a dispatch note can all be correct on their own. The question is whether they describe the same material journey. Batch traceability software connects those records so a manufacturer can follow an input into its output and find where that output went.
In an ERP system, that connection should survive ordinary factory work: opening a bag, changing a source lot, splitting a container, or fitting a molded component into an assembly. A record that stops at the molding machine leaves the next department to rebuild the history.
The clearest way to explain the software is to open a batch file. The example below follows covers molded for a sensor assembly. All identifiers and quantities are illustrative; the important part is what each record establishes and what it leaves unproven.
What batch traceability software actually records
Batch traceability software records the relationships between identified material lots, production outputs, stock movements, and delivery records. A backward trace starts with an output and finds its recorded inputs. A forward trace starts with an input and finds its related outputs and destinations.
Product genealogy is the name often given to those parent and child relationships. Inventory tells you how much remains; genealogy explains how the material or product reached its present form. The two records should agree without being treated as interchangeable.
For an injection molding company, an output can have several parents. Resin, color concentrate, inserts, and approved recovered material may all contribute. Later, that output can become an input to a different product inside the same factory.
Open the example batch file
An electrical equipment manufacturer molds a cover, then uses some covers in its own sensor assemblies. It also sells covers as spare components. One molding order therefore feeds two different delivery paths.
The file contains these main references. Other assembly components have their own records, but are outside this compact example.
| Record | Identifier | Quantity or relationship |
| First resin lot received | R640 | 400 kg received |
| Molding order | MO840 | Uses R640, R641, and MB18 |
| Accepted molded cover lot | H840 | 8,400 covers |
| Recovered runner batch | RG19 | 18 kg from MO840 |
| Sensor assembly lot | A915 | Uses 5,400 covers from H840 |
These references are useful only if transactions connect them. Typing H840 into a comment on an assembly order will not necessarily make it part of a searchable genealogy. Define where the relationship lives and how the software uses it in a trace query.
The receipt establishes the supplier link
The receipt for R640 connects the exact purchased grade, supplier lot reference, received quantity, and relevant certificate. If R640 is an internal code, retain the supplier’s original reference alongside it. Different suppliers can use similar lot strings, so the wider identity matters.
Now split the delivery across several containers. Each container must retain a reliable association with R640 as it moves or opens. A new container label can identify the smaller physical unit without pretending that the resin itself has become a new supplier batch.
The receipt proves what the factory recorded as arriving. It does not prove that the same resin later reached MO840. That requires the production input record.
The molding order establishes the actual inputs
MO840 records 140 kg from R640, 95 kg from R641, and 5 kg from masterbatch lot MB18. Total feed is 240 kg. The bill of materials describes the approved recipe; these consumption records identify the lots actually associated with the run.
Keep planned and actual information distinguishable. A default lot selected by the system is not evidence of physical feeding unless the operating process confirms it. Agree on who records the input and what happens when the expected container is unavailable.
For this example, the two resin lots are approved for the same recipe and contribute to one cofed production batch. There is no validated separation of output by individual resin source. Every cover in H840 therefore retains both resin parents in the trace record.
The output record connects weight with pieces
The run produces 8,400 accepted covers, with an illustrative average mass of 25 g each. Their combined mass is 210 kg. It also records 18 kg of recoverable runners and 12 kg of other losses, giving 240 kg accounted for in total.
This simplified balance uses measured or reconciled quantities for the closed run, with no material left in the equipment. A real plant must account for line balances and measurement uncertainty where they apply. It should also distinguish the relevant loss categories rather than hide every difference under one convenient code.
Matching 240 kg checks quantity consistency. It still cannot establish that the operator selected the correct lot. Batch traceability software needs credible input identification as well as arithmetic that adds up.
Follow H840 into the product the company sells
Of the 8,400 covers, 5,400 enter assembly lot A915. Each sensor assembly uses one cover. Another 1,200 covers ship as spare components, while 1,800 remain as loose stock.
Assembly then ships 3,600 units from A915 and retains 1,800 completed units. At this review point, there are no returns or further losses. The original covers are accounted for as follows.
| Present position | Original covers represented | Record to retrieve |
| Shipped as spare covers | 1,200 | Component delivery and H840 |
| Inside shipped sensor assemblies | 3,600 | Assembly delivery and A915 |
| Inside assemblies still in stock | 1,800 | A915 stock and location |
| Remaining as loose covers | 1,800 | H840 stock and location |
| Total original accepted covers | 8,400 | MO840 output |
The 5,400 covers consumed by assembly are an intermediate movement, not an additional final destination to add to this table. Counting that consumption alongside all A915 stock and shipments would count the same covers twice.
This is especially relevant to manufacturers making electrical devices, appliance products, or automotive assemblies with their own molding equipment. Their trace needs to cross the internal boundary between molded component and completed product. A search restricted to deliveries of H840 would miss the covers shipped inside A915.
Serial numbers can add detail when the finished product requires individual identification. They still need a maintained relationship to the component lots used. Assigning a serial number at packing does not recreate an assembly input history that was never collected.
Ask two questions of the same file
Start with a customer delivery from A915. The backward query should retrieve that assembly lot, its use of H840, molding order MO840, and the contributing material lots. It should also find the production and inspection evidence linked to those records.
Now start with R640. The forward query should find its 140 kg consumption in MO840 and follow H840 into both the spare cover and assembly paths. It should also locate the unused 260 kg of R640, assuming no other movements have occurred.
The recovered runners create another branch. RG19 retains MO840 as its source, and any later approved use must retain RG19 as an input. In this example, RG19 has not been reused; the trace should show its present location and disposition rather than invent a later production link.
These relationships follow the principle described in the GS1 Global Traceability Standard: record the connection between manufacturing inputs and outputs, and preserve relationships through packing. The software design must apply that principle to the plant’s actual material flow.
Read the limits of the evidence
A common mistake is to turn an input proportion into a supposedly exact list of affected pieces. R640 accounts for 140 kg of the 240 kg total feed. That does not identify a corresponding fraction of covers as the only ones containing R640.
The example has a cofed batch without validated output separation. A source concern therefore requires review of the full related output population and its descendants. The trace identifies potentially affected material and products; quality decides their disposition using the relevant evidence.
The same caution applies when one lot tops up a hopper containing another. A bag scan marks an event at the feed point. Residual material and the material path determine whether that event can define an output boundary.
Choose production lot boundaries that the process can support. If the available evidence supports only a mixed interval, retain that association. An exact timestamp on a dashboard is useful only when the physical process justifies the implied precision.
Keep the history intact when the physical container changes
Imagine that dispatch takes 600 covers out of a larger H840 container. The remaining covers still belong to H840, and the new container needs its own quantity and identity link. Reprinting a label must not increase stock or create another production output.
If a pallet carries more than one lot, record its actual contents. A pallet identifier describes a handling unit; it does not make every item on the pallet share one manufacturing history. Correct the contents record when cartons move between pallets.
Outsourced finishing needs the same continuity. Retain the lots and quantities sent, the processor reference, and the quantities returned or otherwise disposed of. A service invoice alone may not provide the links required to trace the returned parts.
When a customer returns product, preserve the original delivery association and record the return separately. Otherwise, a report may show where the product once went while giving an incorrect answer about its current location. Keep historical dispatch totals distinct from current stock.
Where ERP provides the foundation
Odoo’s lot tracking documentation describes identifying groups of received or manufactured products and viewing their traceability. Its manufacturing guidance explains assigning lots or serial numbers to tracked output. These are foundations for a connected batch record.
When assessing Odoo for manufacturing, ask the implementation team to populate this example and run both queries. Verify that A915 appears in a search originating from R640. Check how the report presents multiple input lots, recovered material, stock still on site, and actual delivery destinations.
Some requirements may need configuration, custom development, or integration. Define that scope for material feeding, container relationships, assembly genealogy, and the process evidence your customers require. Confirm the version, edition, and applications used in the proposed solution.
Our ERP for injection molding manufacturers page covers the broader process scope. This batch record complements the wider injection molding traceability guide by showing how input relationships continue through internal assembly and quantities can be reconciled without duplicate counting.
Give IT a correction policy as well as a scanner
The difficult software decisions often appear after an operator makes a mistake. Decide who can correct an input lot, what evidence supports the correction, and how the record retains the previous association. Related output and downstream queries must reflect the approved change.
Also test delayed entries. If a device loses connectivity, preserve when the physical event happened as well as when the system received it. An integration retry should not create a second consumption or a duplicate finished quantity.
Set record retention and access rules around actual customer and business requirements. Test whether archived records and certificate attachments remain retrievable. A backup that restores stock balances but omits the evidence needed for a past batch leaves the investigation incomplete.
For management, useful acceptance measures include missing parent links, unexplained quantity differences, and the time needed to retrieve a complete trace. Agree on targets for your operation. A Manufacturing ERP demonstration should finish with a reconciled file, including any exceptions the team could not resolve.
Frequently asked questions
Does every resin bag need a new batch number
Each bag needs a reliable identity or association with its source lot, but separate bags do not automatically represent different supplier batches. Use container identifiers where individual handling needs to be recorded. Preserve the original lot relationship when opening or splitting a container.
What happens when one molding batch uses two resin lots
Record both contributing lots and their actual quantities. Link them to the output supported by the production evidence. If the lots are cofed or their transition cannot be separated reliably, do not assign individual output pieces to just one source without a validated basis.
Can batch traceability software find resin used inside a finished assembly
Yes, when the records connect resin consumption to the molded component and that component’s consumption to the assembly output. Delivery records must then identify the assembly lot or serial numbers shipped. Test the full chain rather than assuming that tracking both products independently creates the relationship.
Does a matching material balance prove traceability is correct
No. Quantities can reconcile while a record identifies the wrong source lot. Verify input identity and production associations separately from weight or piece counts. Both checks are necessary, and neither can replace evidence that the physical process followed the recorded flow.
Do we need a new production batch after repacking parts
Repacking normally changes the container relationship rather than the manufacturing origin. Preserve the original product lot, identify the resulting containers, and record their quantities. If the operation also changes the product or its approved disposition, apply the relevant production or quality process as well.
Can we add lot tracking to old stock with missing records
Count and identify what the available evidence supports, and document unresolved origins. A newly assigned internal number can identify today’s stock group; it cannot prove its historical resin source. Decide how to segregate, assess, and use uncertain stock before including it in normal trace reports.
Will a traceability report automatically block affected shipments
A report identifies relationships; shipment control requires an implemented hold and release workflow. Verify the restriction across stock movements, assembly use, and dispatch, including user permissions. A lot appearing in a report or quality alert does not by itself prove that all affected movements are blocked.
Bring one batch file to an Apagen ERP demo
Choose a product that combines your molded parts with assembly or finishing. Bring a supplier lot reference, a production record, and an actual dispatch label. We can use them to discuss how the proposed ERP should connect the history and expose any missing links.
Book a batch traceability software demo with Apagen to review resin lots, molded output, assembly relationships, and customer deliveries in one workflow. Email sales@apagen.com or call +91-9971800665.