Connect batch identity with production and dispatch evidence, reconcile quantities and separate physical stock from release status.
A retailer asks which cartons came from a particular production run. The workshop knows the item and the week it was made, but the dispatch sheet records only “soap, ten cartons”. Finding the right deliveries now requires searching through conversations and handwritten notes.
Batch traceability connects a defined production group to its stock movements and customer deliveries. For a Nepal manufacturer, the practical goal is to answer specific questions about a batch without assuming that an item code, a date or an invoice number tells the whole story.
Define what the batch identifies
Choose a clear rule for assigning the batch identity and retain it through production, storage and dispatch. An item code identifies the product; the batch identifies the relevant group of that product. Two batches of the same item should not become indistinguishable because staff print only the item name.
ERPNext’s Batch documentation describes grouping units of an item under a batch number and recording that number in stock transactions for batched items. It is a useful implementation reference. It does not establish that a WorkSphere configuration already supports batch genealogy, expiry controls or a recall process.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
Link the evidence across each movement
A hypothetical Nepal soap workshop assigns batch B-018 to one finished production group. Its record links the production reference, item, output quantity, warehouse receipts and later dispatch lines. If raw-material lot tracing is required, the production records must also link the actual input lots used.
| Record |
Relationship to retain |
| Production reference |
Which output group created the batch |
| Input lot references, if required |
Which actual materials entered production |
| Warehouse movement |
Where the batch quantity moved |
| Customer dispatch line |
Which delivery received which quantity |
A batch label on a carton helps identification, but the label alone does not prove which materials entered production or which customer received the goods. The corresponding records need stable references and a clear relationship. A barcode or QR code can carry an identity; it cannot supply missing history by itself.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Reconcile the batch quantity once
Assume the hypothetical batch produced one hundred cartons of the same finished item. Thirty were dispatched to retailer A and twenty-five to retailer B. Forty-five remain physically on hand. One hundred equals thirty plus twenty-five plus forty-five.
HYPOTHETICAL / same finished item / cartons. Held stock remains inside physical on-hand quantity. Do not subtract those ten twice.
During a quality review, ten of the forty-five remaining cartons are placed on hold. The remaining stock is therefore thirty-five released plus ten held, still forty-five. Do not subtract the ten held cartons again from physical stock. A change in condition or release status is not automatically a physical disappearance.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. Conceptual batch view. Hold is not a defect finding, recall instruction or accounting write-off.
The example excludes customer returns, transfers, losses and later production. If those events occur, record them as additional linked movements rather than forcing them into the original split. The quantity check is not an inventory valuation, tax calculation or estimate of a financial loss.
Distinguish a hold from a confirmed defect
A hold means a specified quantity should not be used or dispatched until an authorised decision is made under the business’s procedure. It does not establish that the whole batch is defective, unsafe or subject to a legal recall. The quality owner must define the scope and obtain appropriate technical advice where needed.
Record the reason, quantity, location, decision owner and next review. Identify already-dispatched quantities separately from stock still controlled by the workshop. The customer contact list should come from the actual affected dispatch references, not every customer who bought the same product at any time.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
Practise a trace question before an incident
Choose a sample batch and ask the team to locate its production record, remaining stock and linked deliveries. Check whether the quantities reconcile and whether the records identify the appropriate contact for each delivery. Do not contact customers merely to demonstrate that the system can generate a list.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
The suggested evidence chain below connects the production record to stock and dispatch records. It is a review exercise, not a claim of regulatory certification or a tested recall capability. If a link cannot be established, keep that gap visible and identify who can investigate it.
Suggested trace exercise, not a certification or claim of tested recall readiness.
Make corrections traceable
A mistyped batch reference should be corrected through the authorised workflow, with the original reference and reason retained as the system permits. Quietly editing the label or a spreadsheet can leave stock and customer records describing different histories.
Agree how repacking, combining material lots and splitting finished batches are represented. These operations can change the relationships the business needs to preserve. Ask for an example using your actual manufacturing process rather than accepting a generic “batch tracking available” statement.
Connect quality decisions to customer work
Inventory staff need to know which stock is available for dispatch. Production needs the relevant input and output references. CRM or sales staff need a verified list of affected deliveries when communication is authorised. Accounting may need to assess later returns, credits or write-offs through separate approved transactions.
Those are distinct responsibilities. A hold flag should not automatically issue a credit note or record a refund. For a proposed WorkSphere implementation, confirm the actual batch fields, movement rules, permissions and cross-module effects with a reviewer before relying on them.
ERPNext Batch