POS and inventory integration: connect sales to expected ingredient usage
Map sales, recipes and modifiers to ingredient units. Reconcile returns and sync failures, then compare expected usage with counted stock.
A point of sale (POS) records what guests buy. Inventory integration converts each sale into expected ingredient usage with a recipe. It cannot count deliveries, waste or actual portion size. Keep those records and physical stocktakes so automatic depletion remains a benchmark you can check.
The working method
- Recipe mapping: link each POS item identifier to ingredients and measured portions. A double portion, milk choice or extra topping needs its own quantity adjustment.
- Unit conversion: convert pack sizes and usable yields before depletion. Record recipe versions and their effective date so old sales use the correct recipe.
- Transaction rules: a void before preparation may reverse expected usage. A refund after food is served does not put ingredients back; record the loss instead.
- Sync control: retain a unique transaction identifier, retry failures without duplicate deductions and show the last successful sync time.
- Physical consumption = opening stock + receipts + transfers in − transfers out − closing stock. Waste and staff meals explain part of its gap from sales-based usage.
A worked example
The POS records 120 burgers. Each recipe uses 180 g of beef. Twenty guests buy an extra 50 g portion.
| Standard burgers | 120 × 180 g = 21.6 kg | Recipe quantity for sold items |
|---|---|---|
| Extra portions | 20 × 50 g = 1 kg | Modifier mapping is required |
| Expected usage | 21.6 + 1 = 22.6 kg | Sales-based benchmark |
| Physical consumption | 24 kg; gap 1.4 kg | Check counts, waste and portion size |
Without modifier mapping, the system would report a 2.4 kg gap. Correct mapping removes 1 kg of false variance; it does not explain the remaining 1.4 kg.
Keep the routine
- 1Start with a small group. Map high-volume items and their modifiers. Test recipes, yields and unit conversions before enabling automatic depletion.
- 2Test transaction rules. Run a sale, modifier, void, refund and retry. Check that each produces the expected ingredient movement once.
- 3Reconcile each day. Compare POS totals with imported transactions. Review errors and the sync timestamp before trusting depletion.
- 4Count and improve. Count high-value stock weekly. Reconcile usage, deliveries, transfers, waste and staff meals; fix the source of each gap.
Frequently asked questions
FAQ
- Does integration replace a stocktake?
- No. It estimates recipe usage from sales. Physical counts show what is actually left.
- Should a refund restore stock?
- Only if the ingredients were never consumed. A served dish refunded to the guest remains consumption or recorded waste.
- What happens when sync fails?
- Keep failed events visible and retry using the same transaction identifier. Reconcile source totals to imported totals before closing the period.
- Can I start without full automation?
- Yes. Export sales and multiply by recipes in a spreadsheet first. Validate units and modifiers before automating.
Keep reading
- Inventory management for restaurants: the system that keeps your margins honest
What restaurant inventory management actually covers, where losses hide, and how to build a system that catches them.
- Restaurant par levels: set stock targets that protect cash and service
Set replenishment targets from usage, delivery intervals, a measured buffer and shelf life. Order only the gap after stock and confirmed deliveries.
- Recipe costing: know the real cost of every plate
Convert pack prices into usable ingredient cost, batch cost and cost per serving. Include sauces, oil, garnish and the measured portion.
Browse by category
Want to review your purchasing?
Submit the details and we will confirm which invoices are useful.
Review 3 invoices free