A case is not a reliable unit until someone defines it
For Inventory managers and supply-chain heads · Compare approaches
TL;DR — what you’ll learn
- Choose a stable stock unit and define purchasing, production and sales conversions around it.
- Treat supplier pack changes as controlled changes with an effective date.
- Keep variable weight separate from fixed pack conversions.
- Test partial packs and rounding across receipts, recipes, transfers and invoices.
Purchasing orders ten cases, the outlet receives ten trays and the stock report adds ten units. Everyone entered the number they saw. The mistake sits in the meaning of the unit, which a totals-only integration never checked.
How should food businesses manage inventory in cases, pieces and kilograms?
Choose a stock unit for each item and maintain explicit, approved conversions for fixed packs. Preserve the conversion used by each transaction. Where weight varies, record actual weight instead of treating an average as a fixed conversion.
- 01Identify the itemBase unit and pack version
- 02Map the transactionPurchase, production or sale unit
- 03Verify the conversionFixed or actual-weight basisIs the conversion valid for this item?YesPost the quantityNoAsk the data owner to resolve the unit or pack mismatch.
- 04Post the quantityRetain both units
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Fixed packs and variable weight need different treatment
For an illustrative fixed pack, one case contains twelve bottles of 750 millilitres. Ten cases are 120 bottles and nine litres per case, provided the product and pack version match. That relationship can be stored as a conversion. A seafood carton that happens to weigh nine kilograms today should not establish the conversion for every carton tomorrow.
Retain purchase, stock and sales units on the original lines, together with the conversion applied. The report can present a common unit without discarding the evidence needed to explain a supplier invoice or customer dispute.
A supplier pack change is a controlled data change
Suppose a supplier moves from twelve to ten bottles per case. Updating one global conversion must not rewrite the meaning of last month's receipts. Use an effective date, a separate pack identifier or another versioning method supported by the ERP. Review open orders because some may still refer to the old pack.
At receiving, make the expected pack visible and provide a way to record a mismatch. AI reading a delivery note can suggest the unit; it should not invent the conversion from the item description. Ambiguous labels belong in a review queue, especially where a mistaken factor affects payment or production planning.
Walk one ingredient across four transactions
Take an illustrative sauce bought in cases of six two-kilogram pouches. One case is twelve kilograms; one pouch is two kilograms. Receiving eight cases adds 96 kilograms. Issuing three pouches to a kitchen removes six kilograms. A recipe requiring 0.15 kilograms per serving would theoretically use those six kilograms for forty servings before accounting for measured loss or portion variation.
The conversion should produce the same answer in each system. If purchasing stores one case as six units while inventory assumes those units are kilograms, the receipt becomes 48 kilograms instead of 96. The error can then appear as poor yield, unexpected purchasing or a finance discrepancy. Investigating those symptoms separately misses the common cause.
| Transaction | Entered quantity | Stock-unit equivalent |
|---|---|---|
| Receipt | 8 cases | 96 kg |
| Kitchen issue | 3 pouches | 6 kg |
| Recipe use | 40 × 0.15 kg | 6 kg theoretical consumption |
What happens when the supplier changes the case?
Suppose the new case contains five pouches instead of six. Do not overwrite a global conversion in a way that changes the meaning of historical receipts. Identify the new pack configuration, its effective date and any open purchase orders still using the previous pack. In some systems a separate item or supplier-pack record is the clearest solution; in others a controlled conversion version may be supported.
Receiving staff need to recognise both packs during the transition. Show the expected pack beside the purchase order and provide an exception for a different pack arriving. A barcode helps only if its associated pack definition is maintained. The business should be able to explain a historical quantity using the conversion that applied to that transaction.
Make rounding visible at the point it matters
A recipe can require a fraction of a kilogram while purchasing can order only whole cases. Keep those two rules separate. If a calculated need is 25 kilograms and the purchasing pack is twelve kilograms, three cases supply 36 kilograms. Show the extra eleven kilograms in the replenishment proposal and shelf-life review instead of silently treating the order as 25.
For variable-weight goods, record actual weight and count rather than forcing a fixed kilograms-per-carton conversion. For fixed packs, define permitted decimal precision and the treatment of residual amounts after repeated issues. Include a full-pack receipt followed by several fractional issues in testing; that sequence often reveals a rounding problem that a single transaction does not.
Prove the conversion through a complete transaction
Take one purchase through partial receipt, warehouse transfer, production issue and supplier invoice. Include an opened case and a return. The agreed stock unit should reconcile at every step, while the original commercial units remain available.
Stock reconciliation tools, such as ERPNext's, provide a way to compare recorded and physical quantities. Use that comparison to detect recurring pack errors rather than absorb them as unexplained stock adjustments. Monitor conversion exceptions by supplier and item so the master-data owner has a manageable correction list.
Source: Frappe / ERPNext · Physical quantity reconciliation. Reference details
Summary
Unit conversions are business rules shared by purchasing, warehouse, production and finance. Their reliability depends on a clear pack definition, controlled changes and explicit rounding. When the pack or weight varies, the system must record that variation rather than hide it inside an assumed constant.
What to do next
- List the purchase, stock, recipe and sales units for five frequently disputed items.
- Reconcile one partial receipt and one partial-pack issue using those definitions.
- Assign an owner to supplier pack changes and test their effect on open orders.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Stock ReconciliationFrappe / ERPNext · Online product documentation, accessed October 2026
Reference for recording physical stock, posting time, warehouse and batch information. Proposed investigation workflows are editorial analysis.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
