A wholesale order arrives for 1,200 jars. Your normal recipe batch makes about 300 jars, so the order will require four production runs.
The purchase order tells you what the buyer expects. It does not show which ingredient lots entered each run, how many jars became sellable, which cases passed review, or whether the full order is actually ready to ship.
Multi-batch food order planning needs one bridge between the customer commitment and the production evidence. A batch-to-order release map provides that bridge. It connects food production, ingredient lots, recipe batches, quality status, case counts, and shipment allocation without pretending four runs are one giant batch.
A purchase order is not a production record
A buyer may think in cases, flavors, delivery windows, and pallet counts. Production works with recipe versions, ingredient quantities, equipment, run sizes, actual yield, checks, and exceptions.
Keep those layers separate:
- Order layer: customer, item, quantity, pack size, due date, destination, and shipment terms.
- Batch layer: batch code, recipe version, ingredient lots, planned quantity, actual output, quality status, and release decision.
- Batch allocation layer: the exact released units or cases from each batch assigned to the order.
If the layers are collapsed into one spreadsheet row, a planned quantity can easily be mistaken for available inventory. The gap appears late—often while cases are being counted for pickup.
Before accepting the order, use the broader food-order readiness checklist and high-volume order preflight test. Once the order spans several runs, add the release map.
Build the batch-to-order release map
Create one row for every recipe batch that may supply the order. At minimum, include:
- customer order number and line item;
- finished product and approved recipe version;
- internal batch code;
- planned production date and planned output;
- ingredient lot or lots used;
- actual filled quantity and sellable quantity;
- cases packed and units per case;
- quality status: pending, released, held, reworked, or rejected;
- quantity allocated to this order;
- remaining unallocated quantity;
- person and date responsible for release.
The allocated quantity must come from released sellable output, not planned output. Keep samples, damaged containers, short fills, hold units, and incomplete cases visible as separate quantities.
For businesses handling foods covered by the FDA Food Traceability Rule, additional records may apply. Review the FDA’s traceability-rule overview and Food Traceability List, then confirm the requirements for your products and operation. This worksheet is an operating tool, not regulatory advice.
Worked example: 1,200 jars across four runs
Assume the wholesale order is for 1,200 jars packed 12 per case. The shipping target is therefore 100 complete cases.
Production plans four recipe batches of 300 jars each:
| Batch | Planned jars | Sellable jars | Complete cases | Status | Allocated to order |
|---|---|---|---|---|---|
| F-0814-A | 300 | 300 | 25 | Released | 300 |
| F-0814-B | 300 | 288 | 24 | Released | 288 |
| F-0814-C | 300 | 300 | 25 | Released | 300 |
| F-0814-D | 300 | 300 | 25 | Pending | 0 |
At this moment, only batches A, B, and C can support the order. They provide 888 released jars, or 74 complete cases. Batch D may eventually add 25 cases, but pending is not the same as released.
Even after D passes, the order reaches 1,188 jars, or 99 complete cases. Batch B’s 12-jar shortfall creates a one-case shortage. The release map exposes that shortage before anyone books a carrier or prints a final packing list.
The owner can now choose deliberately: produce a small approved recovery run, use released unallocated stock from a compatible batch, ask the buyer to accept 99 cases, or move the pickup date. Do not quietly borrow units from another batch without recording the allocation.
Keep ingredient-lot relationships attached to each batch
A large order may consume several deliveries of fruit, sugar, oil, spices, containers, lids, or labels. Record the actual ingredient lots against the recipe batch that used them.
If two lots of the same ingredient enter one run, preserve both relationships and the quantities when known. If one ingredient lot feeds several recipe batches, the forward trace should identify every affected batch. The earlier guide to food and beverage lot tracking explains the backward and forward views.
Do not create a new recipe version merely because a supplier lot changed. A recipe version describes the approved instruction; the batch record describes what was actually used. If the formulation, process, specification, or approved substitution changes, follow your change-control process and label the effective version clearly.
Keep held product out of the ship-ready count
Physical proximity does not equal availability. Cases can be packed and still wait for a check, label correction, seal review, documentation, or another defined release step.
Use status explicitly:
- Pending: required review is incomplete.
- Released: approved for the intended use or shipment.
- Held: separated while an issue is evaluated.
- Reworked or relabeled: not available until the corrective work and required review are complete.
- Rejected: excluded from allocation.
The order summary should calculate released allocated cases separately from packed cases. That single distinction prevents a production dashboard—or a founder’s memory—from overstating what can leave the building.
Control changes without rebuilding the order from memory
Wholesale orders change. A buyer may adjust quantity, split destinations, change the delivery date, or approve a partial shipment. Preserve the original commitment, record the accepted revision, and update allocation rows rather than overwriting the history.
If the change arrives after production starts, use the mid-run food-order recovery plan to recalculate materials, batches, packaging, and fulfillment. The release map then shows which completed or planned batches support each revised shipment.
For split shipments, assign cases by batch and destination. A packing list should not say only “60 cases shipped” when the internal record can say which 60 cases, from which released batches, went to which location.
Run a release review before booking pickup
Before confirming that the order is ready, reconcile five numbers:
- customer quantity due;
- released sellable units allocated;
- complete released cases available;
- shortage, reserve, or approved partial-shipment quantity;
- units from every batch left unallocated.
Then verify the recipe versions, ingredient-lot links, required checks, labels, case configuration, destination, and pickup timing. Name one person who can confirm the final release state. A shared record is useful; clear decision authority is what keeps a pending batch from becoming a shipping promise.
Frequently asked questions
Does every recipe batch need a different batch code?
Yes. Each distinct production event should have a unique identifier so its ingredients, actual quantities, checks, exceptions, and disposition remain clear even when several runs fulfill one order.
Can two ingredient lots be used in one recipe batch?
They can when your approved process permits it, but record both lots and quantities when known. The batch must remain traceable backward to its inputs and forward to the finished goods it supplied.
Should held cases be assigned to the customer order?
They may be reserved in a plan, but they should not count as released ship-ready inventory. Keep the hold status visible and maintain an alternate plan for the order until disposition is complete.
What changes if the buyer allows partial shipments?
Add a shipment identifier, date, destination, and batch-level case allocation for each shipment. Reconcile the remaining balance after every release so the same cases cannot be promised twice.
Practical takeaway
One large order can be one commercial commitment without becoming one production batch. Keep the order, recipe batches, ingredient lots, and allocations connected but distinct.
Build the release map before confirming pickup. When planned jars, sellable jars, released cases, and allocated cases reconcile, the business can make a clear promise—and can explain exactly what supports it.
