A caterer buys thirty pounds of halibut for a Saturday wedding and sells five-course dinner plates. The POS records "Wedding Dinner — 125 guests." The procurement system needs to know that before Saturday, you ordered the halibut, the lemon beurre blanc ingredients, the garnish herbs, the back-up protein in case of substitutions, the linens, the rental dishware, and the disposable chafing fuel — from six different suppliers — and that all of it had to land at your commissary kitchen no later than Thursday morning.
That is the structural problem with catering procurement. Every demand signal is an event booking, not a steady sales rate. Every purchase order has a hard deadline — the event date — not an implied "whenever." Every menu is a bill of materials that must be fully sourced before execution, not a week-over-week average that self-corrects through reorder cycles. And every substitution a supplier throws at you two days before the event is not an inventory adjustment — it is an operational emergency.
Most catering companies run this on a combination of spreadsheets, shared Google Docs, and supplier phone calls. That works for a few events per month. It stops working when you are running three events in a weekend, managing fifteen suppliers, and a produce distributor tells you on Thursday afternoon that the arugula you ordered for two events is out.
Quick answer: caterers need living POs
Catering procurement works best when the purchase order for each event stays live from menu BOM to supplier confirmation to receiving to accounting. A living PO absorbs substitutions as negotiated updates rather than email surprises, captures what was actually received against what was confirmed, and closes out the event with a clean food cost number before accounting sees the bill.
That is closed-loop procurement applied to event-driven buying: demand comes from the event booking, fulfillment is measured against the event menu, and the PO closes when the event is served and the food cost is reconciled — not when the invoice hits accounts payable.
See Three-Way Matching vs. the Living PO for the full upstream reconciliation model.
The event BOM is the procurement engine
For a restaurant, the bill of materials is a recipe attached to a menu item. For a caterer, the BOM is the entire event menu scaled to confirmed headcount.
A corporate luncheon for 80 guests might require:
- Chicken breast: 24 lbs from the main food distributor (3-day lead time)
- Penne pasta: 12 lbs from the main food distributor (3-day lead time)
- Mixed greens: 10 lbs from the produce supplier (2-day lead time)
- Heavy cream: 3 liters from the dairy supplier (2-day lead time)
- Dinner rolls: 100 units from the local bakery (1-day lead time)
- Chafing dishes and fuel: 8 sets from the restaurant supply house (5-day lead time)
When the client confirms final headcount — often 2–4 weeks before the event — every quantity in the BOM scales proportionally. Add 20 guests and you need 6 more pounds of chicken, 3 more pounds of pasta, and 2.5 more pounds of greens. Miss that update and you are short on the day.
The procurement system needs to hold the scaling relationship between headcount and ingredient quantities so that a confirmed headcount change flows into updated purchase orders, not through a manual recalculation in a spreadsheet.
This is structurally different from restaurant procurement where demand is continuous and the reorder math is based on consumption rates. Catering demand is event-discrete: you need exactly 24 lbs of chicken for this Saturday, not "approximately 8 lbs per day."
Perishable lead times control event execution
Not all catering ingredients are ordered on the same timeline. The ordering window for each category is constrained by both supplier lead time and the ingredient's shelf life relative to the event date.
For a Saturday event with commissary receiving on Thursday:
Specialty proteins (fish, dry-aged meat): Order by Monday — five-day lead time, short shelf life. A fresh halibut fillet ordered Tuesday for Thursday delivery may not meet quality standards. No flexibility on this category.
Fresh produce: Order by Wednesday morning — two-day lead time. Even shorter windows for ultra-perishables like microgreens, fresh herbs, or ripe avocado. Once produce is ordered, it is committed.
Dairy: Order by Wednesday — two-day lead time. Must arrive fresh. Cannot be pre-frozen and thawed without quality loss on cream, soft cheeses, or fresh butter.
Dry goods and pantry staples: Order Monday–Tuesday — three-to-five-day lead time, but multi-day shelf life gives flexibility. No urgency, but do not let it slip to Thursday.
Alcohol and beverages: Order Monday–Tuesday depending on state distributor delivery schedules. Distributor routes are fixed; missing the Tuesday cutoff means waiting until the next route day.
Disposables and non-food supplies: Order by prior Wednesday — seven-day lead time from restaurant supply. These have no perishability but the longest supplier lead time of any category.
Rentals (linens, china, flatware): Commit two to four weeks out. Rental companies require reservations well ahead; last-minute requests often cannot be filled at peak weekend times.
The failure mode in catering is treating all procurement as the same urgency. A procurement system for catering should surface these ordering windows relative to each event date — not just flag "low stock." For a Thursday–Saturday event run, the produce order trigger should appear in your workflow by Tuesday morning. The specialty protein order trigger should appear the Friday before.
Running parallel POs across multiple events
The operational complexity that breaks manual catering procurement is not a single event — it is simultaneous events with overlapping supplier orders.
Consider a catering company running four events in one weekend: a Friday corporate cocktail reception, a Saturday wedding dinner, a Saturday afternoon birthday brunch, and a Sunday barbecue fundraiser. Each has its own menu, its own headcount, its own food cost target, and its own ingredient requirements.
The procurement challenge compounds quickly:
- The same food distributor receives four separate orders with different required delivery dates
- The produce supplier receives two consolidated orders — the Friday event needs Wednesday delivery, the weekend events need Thursday delivery
- Some ingredients overlap across events (chicken breast, butter, mixed greens) — order consolidation might hit a volume minimum, but event-level cost accounting must stay separate
- A substitution from the distributor on Tuesday could affect one event, two events, or all four, depending on which menus use that ingredient
Without a system that tracks which ingredients belong to which event PO, you are managing this in your head. The moment a supplier calls with a substitution, you have to mentally reconstruct which events are affected, what the substitute costs, whether the client's contract allows a substitution, and how the margin changes.
A system that connects each PO to the event BOM can surface that instantly: "halibut substituted for cod affects Saturday wedding dinner (87 guests), increasing food cost by $210 and reducing per-head margin by $2.41."
Supplier substitutions under event pressure
In restaurant procurement, a substitution is a menu adjustment. In catering, a substitution is a contractual situation. Your client booked and paid for a specific menu. A protein substitution two days before the event may require client notification, menu reprinting, and in some cases a partial credit.
This is why supplier communication tracking matters more in catering than in almost any other food service segment. When a substitution comes in:
- Assess whether the substitute is acceptable on quality and cost
- Determine whether client notification is required under your contract
- Update ingredient quantities — the substitute may come in different pack sizes with different yields
- Update food cost calculations for the affected event
- Confirm new pricing in writing with the supplier
- Document the change so the event food cost reconciliation is accurate
A procurement system that captures supplier replies as structured updates to the living PO creates an audit record of what the caterer was told and when — which matters if a client ever disputes an unexpected substitution.
For last-minute substitutions within three days of an event, dual-sourcing critical proteins and specialty produce is the operational hedge. Caterers running significant volume in a category often maintain backup suppliers for their highest-risk ingredients — not to split every order, but to have a confirmed line when the primary supplier cannot deliver. See Dual Sourcing: When to Add a Backup Supplier.
Food cost per event, not per month
For a restaurant, food cost percentage is a monthly P&L line. For a caterer, food cost is an event-level metric. You quoted the client at a specific per-head price that embedded a food cost target. Whether that target held depends on what you actually paid for ingredients, how headcount changed after the quote, and what substitutions affected pricing.
The event food cost formula:
Event food cost % = Total ingredient cost for event ÷ Event revenue × 100
Where total ingredient cost includes everything charged to the event PO — proteins, produce, dairy, pantry, disposables, and any non-food consumables.
At $125 per head for a 100-person wedding dinner with a 30% food cost target, you have $3,750 in ingredient budget. If substitutions and last-minute additions push the actual food cost to $4,200, the event margin takes a 3.6-percentage-point hit. A caterer running 50 events a year at similar scale would see that variance become material if it is not tracked per event.
The reconciliation happens across four states: what was ordered on the event BOM, what the supplier confirmed (with any substitutions and price changes), what the receiver counted when it arrived, and what the invoice actually charged. Each state should be visible in the purchasing record before accounting closes the event.
This is why three-way matching — where AP compares PO, receipt, and invoice after the fact — is insufficient for catering. The operational decisions (can we absorb this substitution? does this price change blow the event margin?) need to be made when the supplier communicates them, not when the invoice arrives post-event.
Headcount changes cascade through the BOM
One of the most common catering procurement problems is a headcount change that does not propagate through the ingredient order.
The client calls two weeks before the event to add 20 guests. You update the event booking. But if the procurement system does not hold the headcount-to-ingredient relationship, someone has to manually recalculate every line in the BOM and call suppliers with updated quantities. That works once. It stops working when headcount changes come in for three events in the same week.
The relationship is simple but needs to be tracked:
Ingredient quantity = (Per-head serving size × final headcount) × (1 + waste and yield factor)
For the 20-guest addition to the luncheon example: chicken at 0.3 lbs per head adds 6 lbs to the order. Greens at 0.125 lbs per head add 2.5 lbs. Each ingredient scales from the per-head recipe, not from a fixed event quantity.
The decay rate overlay matters for perishables: the receiving quantity should buffer for the portion of an ingredient that will degrade before use. A caterer receiving fresh fish on Thursday for a Saturday event is holding it under refrigeration for 48 hours; the yield may be marginally lower than the ordered quantity by event time. That buffer should be built into the order quantity, not discovered during Saturday morning prep.
Receiving at commissary and on-site
Most catering companies receive ingredients at a central commissary kitchen where prep happens. Some also receive directly at the venue for day-of deliveries. Both require documented receiving against the confirmed PO.
Commissary receiving should capture: quantities counted, any shorts or overs against the confirmed order, lot or expiry information for proteins and dairy, and any quality issues that need to go back to the supplier. If you ordered 24 lbs of chicken and received 22 lbs, the event ingredient record needs to reflect 22 lbs — not 24. The two-pound discrepancy changes the event food cost and may mean a credit memo from the supplier.
Venue-day receiving is higher-pressure: the event is hours away, the delivery window is narrow, and there is no practical recourse if something is wrong. The operational answer is that anything with quality or quantity risk should arrive at the commissary two to three days before the event — not day-of. Day-of deliveries should be limited to what genuinely cannot be staged earlier: ice, certain fresh florals, same-day bread from a local bakery.
When receiving discrepancies happen, they should update the PO immediately so the event food cost reconciliation starts with accurate quantities — not with what was ordered and the assumption that everything arrived correctly.
What to look for in catering procurement software
A procurement system for catering companies should handle:
- Event-based BOM construction with headcount-proportional quantity scaling
- Per-event PO creation and tracking with event-date-aware ordering windows by ingredient category
- Supplier communication capture — substitutions, price changes, short deliveries, ETA updates — as structured PO updates
- Multi-event supplier order management, including order consolidation where volume minimums justify it
- Receiving workflows tied to event POs with quantity variance and lot capture
- Per-event food cost reconciliation against confirmed headcount, substitutions, and actual received quantities
- Supplier management across food distributors, produce suppliers, dairy, alcohol, specialty vendors, and disposables — with different lead time profiles per supplier
- QuickBooks or Xero handoff with event-level cost coding
- FIFO/FEFO enforcement for perishable receiving
- Audit trail of substitutions and price changes for event documentation and client communication
The system should understand that demand comes from event bookings, not from POS sell-through. The reorder logic for catering is not "when stock falls below PAR" — it is "event booked for this date, BOM has these items, ordering windows open on these specific days for each supplier category."
Where LineNow fits
LineNow is closed-loop procurement software built around living purchase orders for SMB operators. For catering companies doing $500K–$5M in revenue, the practical fit is:
- Per-event purchase orders linked to event BOMs and scaled to confirmed headcount
- Supplier communication captured as structured PO updates — substitutions, price changes, ETAs, shorts — before receiving starts
- Receiving workflows that record what actually arrived against what was confirmed, creating an accurate event food cost record
- Accounting handoff to QuickBooks or Xero with clean per-event purchase data
- Supplier management across your full vendor mix — food distributors, produce suppliers, alcohol distributors, disposables, equipment rental — with supplier-specific lead time awareness
- Multi-event visibility so parallel event POs do not cross-contaminate receiving or cost records
$100/month flat. 90-day free trial. No per-event fees, no percentage of catering revenue, no per-seat charges.
The goal is not to add another system to the pre-event production checklist. The goal is to replace the combination of spreadsheets, Google Docs, and text threads that currently hold together the procurement side of your operation — and to surface substitutions, headcount changes, and cost variances when they happen, not after the event closes and the invoice is already in QuickBooks.
A 60-second diagnostic
Three questions:
- When a client confirms a headcount change four weeks before the event, do you automatically know which ingredient quantities need to change and which supplier orders need updating?
- When a supplier emails a substitution on Thursday for a Saturday event, can you see in under two minutes which events are affected, what the per-head cost impact is, and whether you need to notify the client?
- After each event closes, can you calculate the actual food cost percentage against the quoted food cost, broken down by the original BOM, supplier substitutions, and receiving variances?
If any answer is no, your procurement loop is open. The most expensive cost variances in catering are not bad supplier prices — they are untracked substitutions, headcount changes that did not flow through the ingredient order, and receiving discrepancies absorbed without reconciliation.
Closing the loop means the event BOM, the PO, the supplier's confirmation, the receiver's count, and the accounting record all tell the same story — and that story is visible before the invoice arrives.