Allocating Frozen Food Batches by Remaining Shelf Life and Customer Requirements

Allocate frozen-food batches by checking which lots meet the customer’s requirements at the agreed delivery point, then choosing the batch with the earliest applicable end date within that eligible stock. Keep release status, existing reservations and product specifications visible. The oldest carton in the warehouse is not automatically the correct carton for every order.

Remaining shelf life becomes useful only when the date basis is clear. A buyer asking for a minimum number of days at its distribution centre has a different requirement from one measuring at shipment. The allocation record should connect that requirement to an identified batch, a realistic receipt date and an available quantity.

Build the eligible stock list before choosing a batch

Start with the customer order: product code, approved specification, pack, quantity, receiving location and required timing. Add any agreed minimum remaining life, approved origin or facility, label version and release conditions. These fields define the stock that can be considered. A broad product description such as “frozen strawberries” leaves too many differences unresolved for a reliable batch selection.

Then identify each candidate lot and its actual inventory position. Record the date information, stock location, quantity and current status. Distinguish physical stock from stock available for this order. Cartons can be present but already reserved, awaiting review, in a different approved pack or unavailable for a required dispatch date. Keep the reason visible rather than reducing every excluded quantity to an unexplained zero.

Inventory software documentation offers useful examples of this distinction. Microsoft’s batch disposition guidance separates availability for planning, reservation, picking and shipment, with behaviour dependent on system configuration. For a buyer, the operational question is whether a restriction actually prevents the relevant fulfilment step. A note on a spreadsheet does little if the warehouse continues to pick the affected stock.

Confirm who is authorised to change a lot’s status and how that decision reaches the people selecting and moving cartons. A commercial request for urgent delivery should go through that process. Where a lot is under technical review, the allocation team needs the affected quantity and the status reference; it should not infer release from a favourable date or a customer’s willingness to receive quickly.

Check whether reservations are recorded at SKU level or against individual lots. A product-level sales commitment may not yet identify a physical batch, but it still consumes capacity that another order cannot freely use. Resolve overlapping commitments before confirming a new allocation. If a reservation can be changed, record the effect on the earlier order as part of that decision.

Our traceability coordination starts with identifiable product, lot and shipment references. When reviewing a proposed supply with XMG, tell us which date fields and records your team needs to assess the batch. We confirm the available information with the relevant partner factory; the buyer and its warehouse maintain their own order reservations and stock controls.

Calculate remaining life at the agreed customer handoff

Write down the event at which the customer measures remaining life. It might be delivery to an import warehouse, receipt at a distribution centre or another agreed handoff. Identify the location as well as the event. Port arrival and receipt at an inland warehouse can occur on different dates, and the interval between them consumes time that matters to the customer’s calculation.

For a requirement expressed in calendar days, calculate the interval from the agreed receipt date to the relevant product date. Confirm the counting convention and treatment of the boundary day with the customer. If the requirement is expressed as months or a percentage of original life, document its calculation separately. Do not silently convert one form into another using an assumed month length or an unconfirmed original duration.

Consider a hypothetical batch whose relevant date mark is 30 June 2027. Using elapsed calendar days, receipt on 1 April 2027 leaves 90 days; receipt on 11 April leaves 80. The product date has not changed. A ten-day movement in the receipt plan changes the remaining interval by ten days. These dates demonstrate arithmetic only, not an acceptable duration for a particular frozen product.

Microsoft’s shelf-life planning documentation illustrates customer-specific sellable days measured from a requested or confirmed receipt date. Oracle’s remaining-life allocation documentation also makes the minimum duration and its anchor event explicit. These are examples of planning logic; the buyer still needs to establish the actual contractual requirement and how its operation applies it.

Verify the meaning of the product date before using it. Production, packing, best-before, sell-by and expiration fields describe different things. The GS1 US case-code guidance distinguishes these date types and batch identifiers within its voluntary North American scope. A packing date cannot simply be read as an expiration date, and a lot code may require a documented interpretation.

Ask for clarification where the label, stock record and supplier document disagree. Keep the original reference and the corrected explanation together. The allocation exercise uses established product information; it does not validate a new shelf life, authorise a relabelled date or determine whether goods may legally be sold after a particular mark. Those questions need their appropriate technical and market-specific review.

Allow the planning team to see uncertainty as well as the calculated interval. Record a provisional receipt date as provisional and identify when it will be checked again. A batch that meets the requirement by only a small margin deserves a clear follow-up before dispatch. Any operating allowance for delivery uncertainty should be agreed and recorded, rather than hidden inside an altered product date.

Allocate the earliest suitable batch with reservations visible

Once eligibility is established, use the agreed date-priority rule to choose between suitable lots. First-expiring-first-out, usually shortened to FEFO, gives priority to the earlier relevant end date. The Codex code for quick-frozen foods, CXC 8-1976, discusses orderly stock rotation, including first-in-first-out or the shortest durability date. Rotation still needs to respect product conditions and the requirements attached to the order.

The following example is fictional. Two customers require the same approved SKU and pack, with the same planned receipt date. North requires at least 90 days remaining and orders 80 cartons. Local requires at least 60 days and orders 60 cartons. All quantities and durations are chosen to explain allocation; they are not XMG stock figures or recommended customer limits.

Batch A cannot meet North’s 90-day requirement at this receipt date, even though it is released and has the earlier date. Batch B can meet it. Allocating 80 cartons of B to North and 60 cartons of A to Local fulfils both orders while using the earlier suitable batch for Local. The held quantity remains outside the calculation despite having the longest remaining interval.

If Local received 60 cartons of B first, only 40 unreserved cartons of B would remain for North. Batch A would not solve that shortfall under the stated requirements. This is why the team should review the demands competing for the same stock, especially orders with fewer eligible alternatives. Using a later-dated batch for an order with more alternatives can leave a stricter order short.

Reconcile the quantities after making the decision. The two released batches contain 220 cartons: 50 were previously reserved, 140 are now allocated and 30 remain free. The separate 50-carton held batch is still held. This reconciliation is a check on the example’s record, not a reason to combine statuses into one available-stock figure.

Where several allocations satisfy the same requirements, consider the agreed order priorities, delivery feasibility and handling implications. Record the selected lots and any deliberate exception to the usual date sequence. Include the order priority and any handling constraint in the decision record so another planner can review the selection.

Keep product, packing and release requirements attached

A favourable date does not make two frozen products interchangeable. Check the specification reference behind the SKU: product form, size or cut, relevant treatment and agreed quality criteria. A customer using a particular broccoli floret format in a ready meal may not accept another format merely because it has more remaining life. Confirm the proposed change through the customer’s approval process before using that stock.

Apply the same discipline to the pack. Unit weight, units per carton, bag or pouch format, language, artwork and carton marks can determine where a lot may be supplied. A bulk ingredient pack and a retail-labelled pack may contain the same type of vegetable while serving different orders. Record the approved pack reference in the allocation, especially when several versions coexist in the warehouse.

At XMG, we coordinate packing and mark requirements for the product and proposed order. Send the revision reference when asking about a different pack or label. We will review the relevant option with the partner factory and clarify which configuration the response covers. A discussion about feasibility should remain distinguishable from an accepted order change.

Customer approval may also be limited to a particular source, facility or programme. Keep those requirements identifiable and check the evidence applicable to the candidate lot. A certificate covering one holder or scope should not be used to fill an information gap for another batch. Where supporting records are incomplete, describe the unresolved requirement and request the appropriate confirmation before promising the allocation.

Separate the product’s established duration from its actual condition and handling history. A date calculation cannot resolve a damaged pack, a temperature concern or a mismatch in the lot records. Keep affected quantities under the applicable review process until the responsible team records its decision. If only part of a lot is affected, the physical and inventory controls must identify that part accurately enough for picking.

When a customer can accept an alternative, record exactly what it has accepted: the lot, quantity, product or pack difference, delivery point and any stated conditions. An exception for one order should not automatically become the default for future orders. Keep the original requirement and the accepted exception available to receiving and quality staff, who may otherwise reject a delivery that purchasing has already discussed.

This level of identification also prevents misleading stock summaries. “Two months available” or “latest crop” does not tell the buyer which date applies, which pack is proposed or whether the quantity has been released. Use the actual product and record references to support the offer, with unconfirmed fields clearly assigned for follow-up.

Recheck allocations when dates or quantities change

Revisit the allocation when a change affects its assumptions. Triggers include a later receipt date, a reduced available quantity, a new hold, a changed customer requirement or a substituted lot. The record should identify the original basis so the team can see which calculation or eligibility decision needs attention. Highlight the revised field and retain the earlier value for comparison.

A shipping delay is a common example. Update the expected handoff date and recalculate the remaining interval for each affected customer. A lot may still be suitable for one order while falling below another order’s requirement. Our guide to replanning a delayed frozen-food container covers the receiving and transport arrangements that feed into that revised date.

In the fictional allocation above, a further 25-day delay would reduce A’s remaining interval from 80 to 55 days and B’s from 110 to 85. Neither would meet the stated requirement for its allocated customer at that later receipt. The original allocation therefore needs a new decision. The arithmetic does not show that the food is unsafe; it shows that the previously stated commercial date requirements are no longer met.

Discuss the actual alternatives before dispatch. These might include another eligible lot, an earlier feasible delivery, a smaller confirmed quantity or a customer-approved change within the applicable rules and technical requirements. State which part of the order each option covers. Do not present an unconfirmed replacement lot as available stock or change a product date to preserve the appearance of compliance.

If one order is cancelled or reduced, release its reservation through the agreed process and recheck the newly available lot before offering it elsewhere. Time may have passed since the earlier approval, and the next customer may have different requirements. Conversely, when an order increases, confirm that the added quantity comes from eligible stock rather than extending the existing reservation beyond its physical balance.

Record who accepted the revised allocation and which previous version it replaces. Notify the warehouse if picking has started, and establish whether already prepared cartons need to be separated or reassigned. Update the delivery documents and stock records consistently. A revised spreadsheet alone cannot correct cartons that are still staged under an earlier instruction.

Carry lot identity into picking and delivery

Give the warehouse a picking instruction that identifies the order, product and pack, selected lot, quantity and location or handling reference. Include any required date check and the route for reporting a discrepancy. The instruction should let staff compare the visible carton or pallet reference with the authorised allocation, without having to interpret a general request for “the oldest suitable stock.”

Preserve batch separation when an order uses more than one lot. Record the quantity from each and keep the carton, pallet and dispatch information connected. Avoid reporting only an average remaining life across the delivery: that can hide a lot that does not meet the customer’s minimum. The relevant date requirement needs to be checked for each lot included under the agreed acceptance basis.

Reconcile the picked quantity with the reservation before dispatch. If the picker finds fewer cartons than expected, a different label or another lot in the location, stop the affected substitution and refer it to the responsible person. A replacement selected on the warehouse floor needs the same eligibility review as the original batch, including its remaining life at the customer handoff.

Keep the delivered lot references available for receipt and later enquiries. Confirm which fields the buyer expects on the packing list, carton marks or other agreed records. GS1’s identification guidance can support consistent data exchange where that system is used, but the actual record format must work for the parties handling the order. A readable identifier and a maintained link to the batch are essential to the review.

Close the allocation against the quantity actually dispatched and any balance still reserved. Record shortages, substitutions and accepted changes so the next stock report reflects what happened. Review recurring exceptions such as late receipt-date updates, unrecorded reservations or frequent pack mismatches. Those findings show which part of the ordering or warehouse process needs a more reliable input.

When preparing the next order, keep the accepted product and pack references but refresh the quantity, destination and timing. Reconfirm the remaining-life requirement at the new handoff date. If the previous delivery needed an exception, identify whether that exception ended with the order or has become part of an approved revised requirement.

References

• Microsoft Learn. Shelf Life in Planning Optimisation.
• Microsoft Learn. Use Batch Disposition Codes to Mark Batches as Available or Unavailable.
• Oracle. Order Management 26D: Remaining Shelf-Life Allocation Documentation.
• GS1 US. North American Guidance for Case Code Labeling, Release 3.0, December 2025.
• Codex Alimentarius. CXC 8-1976, Code of Practice for the Processing and Handling of Quick Frozen Foods; current code listing.