Central Kitchen

Track a central-kitchen dispatch through branch receipt

Keep prepared, dispatched, received and held quantities separate so a branch can explain each transfer difference.

One dispatch, four quantities to keep distinct
Kitchen dispatch48Portions released
Branch arrival47One missing
Held for review2Arrived, not accepted
Accepted45Available under local procedure

Illustrative count only. Apply your own food-safety and stock procedures.

By OX Labs team · A practical guide for restaurant operators. Adapt the steps to your policies, units and approval process.

One question, four practical steps
  1. 01Identify the dispatch
  2. 02Count what arrived
  3. 03Separate held goods
  4. 04Resolve the gap

Agree what is leaving the kitchen

Give each dispatch a reference, date, origin, destination and responsible people. Identify each prepared item by a name and unit that both teams use. Record batch or date information where your food-safety procedure requires it.

Separate production yield from dispatch quantity. A kitchen may prepare 60 portions but dispatch only 48; the remaining 12 are not a transport discrepancy. Check packaging, labeling and the relevant storage or transport controls before release.

Record the physical handoff

Count the quantity actually loaded and record who released it and when. The branch should compare the received goods with the dispatch record using the same unit, then record arrival time, condition and quantity accepted for use.

Temperature-sensitive food needs the handling and checks required by the operation's food-safety plan and local rules. Do not infer that a quantity match means the food is safe. Hold questionable items for a qualified decision under the local procedure rather than silently adding them to usable stock.

Explain the difference before closing it

Keep dispatched, arrived, held and accepted amounts distinct. If 48 portions left the kitchen, 47 arrived and 2 of those were held, the branch has 45 accepted portions, 2 held portions and 1 missing portion. These are different questions with different follow-up.

Record the evidence for a missing or damaged item, the person investigating it and the outcome. Reconcile both locations' records only after the teams agree what moved and what was accepted. Avoid creating a balancing adjustment that hides an open issue.

Review the recurring pattern

Look for repeated differences by item, route, packing method or branch. Review the handoff with production, dispatch, receiving and finance where relevant. Correct the process and check whether the next dispatch shows improvement.

Example: one dispatch, three outcomes

Prepared at kitchen60 portions
Dispatched to branch48 portions
Physically arrived47 portions
Held for review2 portions
Accepted for use45 portions
Missing in transit1 portion

The 12 portions not dispatched remain a kitchen question. The 2 held portions arrived but are not usable stock. The 1 missing portion needs investigation. This is an illustrative count, not a food-safety decision.

Record both sides of the handoff

Download a CSV with separate fields for prepared, dispatched, arrived, held, accepted and missing quantities. The example is illustrative; store actual records in your approved system.

Download the transfer worksheet ↓

Food handling references: UK Food Standards Agency Safe Catering guide discusses delivery condition and checks; the US FDA Food Code describes receiving controls. These are examples of official guidance, not universal legal requirements. Follow your local rules and food-safety plan.

Use this guide as a discussion aid. Confirm the actual ITS V.Pro workflows available for your setup before relying on a product-specific process.

ITS V.Pro software

Put connected stock work in one place.

Free guides and interest forms are separate from the 30-day software trial.

Start your 30-day ITS V.Pro software trial