For an independent restaurant or small group, procurement connects what the team orders, what the receiving shift accepts, and what a later stock count finds. Those handoffs affect food cost percentage and total prime cost, alongside labor and other operating costs. A changed produce delivery, an unplaced bar order, or a supplier substitution can leave the next shift and bookkeeper working from different records.
This guide follows the order, receive, count workflow for restaurant teams. Start with usable stock, supplier packs and a delivery checklist. Recipe costing and mapped POS sales can add planning detail when the team needs it; they are not prerequisites for organizing purchasing.
If you're an independent restaurant operator or running a small restaurant group, this is for you.
Quick answer: connect ordering, receiving and counts
Keep each supplier PO connected to proposed changes, the buyer's decisions, actual receipts and the quantities still due. A physical count then establishes what is on the shelf for the next buying decision. The order, receive and count workflow shows these handoffs without requiring a recipe rollout first.
Read before ordering
A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.
That is upstream reconciliation. The buyer reviews the supplier's proposed changes; a confirmation alone is not buyer approval. The receiver checks what arrived against the current approved order. Accounting reviews the order, receipt and invoice together while retaining its coding, payment and exception controls. See Three-Way Matching vs. the Living PO.
What's different about restaurant procurement
Three restaurant purchasing conditions deserve particular attention:
1. Purchase units and kitchen units differ. A supplier may sell a case while the team counts cartons, bottles or kilograms. Record the pack conversion before ordering or receiving. Recipe mappings can estimate ingredient usage from menu sales, but physical counts remain useful whether or not recipes are configured.
2. Usable stock changes between deliveries. Review the condition and remaining usable quantity of produce, dairy and proteins before buying more. Use observed consumption and recorded losses to adjust quantities and delivery frequency. A modeled stock buffer does not establish shelf life or replace the kitchen's food-safety procedures.
3. Supplier changes arrive through different channels. An illustrative produce reply might say "blueberries out till Friday, can substitute strawberries, +$0.50/lb." The buyer needs to review the item, price and delivery change, then make the decision visible to the receiving shift. Confirm which email, messaging and portal workflows the chosen system supports.
Test those handoffs with the owner who approves the investment and the employees who will order, receive and count.
The complete restaurant procurement loop
Here's what the loop should look like end-to-end:
1. Start with usable stock and open orders
Count the items needed for the next supplier cycle in a consistent unit. Check what is usable, what is already committed and which outstanding deliveries are confirmed to arrive before the next need. Incoming stock is not the same as stock available now.
A buyer can begin with a count and an order guide. Review the supplier, pack conversion, quantity, price and destination before sending. Assign responsibility for any proposed substitution or price change so the receiver knows which version was accepted.
Add POS and recipe mappings when they answer a specific planning or costing question. Validate their sales feed, yields and location scope before relying on estimated ingredient usage. They supplement the order and physical checks rather than replacing them.
2. PAR levels per ingredient, not per dish
This is a common mistake in early restaurant inventory: thinking in terms of finished dishes rather than ingredients. Your supplier does not deliver sandwiches. They deliver flour, turkey, and lettuce.
When recipes are mapped, estimated ingredient usage can be calculated across the menu items that use it:
estimated ingredient usage = Σ (menu items sold × configured ingredient quantity per item)
A periodic-review target can combine expected demand over the review and lead-time period with a justified buffer:
target stock = demand over the protection period + safety stock + manual buffer
The target is not the quantity to buy. Deduct usable stock and eligible incoming quantities in the same units, then review supplier packs and delivery timing. The PAR level calculator explains its assumptions; any modeled loss allowance needs measured inputs rather than a generic spoilage percentage.
Choose the planning method against the item's actual history and service needs. Intermittent bar supplies and daily coffee staples may need different treatment. A statistical model is useful only if its inputs and ordering recommendations survive review against actual counts and deliveries.
3. Counting cadence by category
Category
What to consider when setting the count schedule
Premium proteins
Purchase value, usage variability and the consequences of a shortage
Liquor / bar
Open-container measurement, service patterns and unexplained differences
Fresh produce
Delivery frequency, condition and usable quantity before the next order
Dairy and eggs
Delivery timing, storage procedures and actual usage
Dry goods
Order cycle, shelf capacity and recurring stock differences
Cleaning and paper
Criticality, available storage and supplier lead time
There is no universal daily or weekly schedule for every kitchen. Assign an owner and a practical cadence, then adjust it using the differences found and time required. A variance can come from usage, waste, transfers or recording errors; it is not proof of theft or any other cause. The inventory count checklist helps record the physical quantities.
4. Supplier roster: build for redundancy
Decide where a qualified backup would reduce a meaningful supply risk. There is no required number of suppliers per ingredient: alternatives bring their own minimums, delivery schedules and review work.
Identify items whose absence would disrupt service.
Check a potential backup's item specification, pack size, availability, delivered cost and lead time.
Agree who can approve an alternate product before the receiving shift is offered a substitution.
Keep current quoted terms and relevant price history with the supplier record. Compare the full delivered offer, not just a unit price, and verify availability before treating an alternative as a committed delivery.
5. The supplier reply parsing problem
When a supplier proposes a change, inspect how the team records and communicates it:
Can the buyer see the original message beside the proposed quantity, item, price and delivery changes?
Is the buyer's decision distinguishable from the supplier's proposal?
Can the receiving shift and bookkeeper find the accepted terms without reconstructing the email thread?
A closed-loop procurement platform keeps those handoffs connected. LineNow can read supported supplier messages into reviewable order updates. The buyer checks the message and proposed changes; extraction is not approval of a substitute, proof of delivery or payment authorization.
Test the actual supplier channels during setup, including a change that needs clarification rather than acceptance.
6. Receiving discipline
When the truck arrives:
Check item identity, pack size and physical quantity against the current buyer-approved PO.
Distinguish accepted, rejected and held quantities under the operation's receiving and safety procedures.
Retain the delivery documents and notes; an invoice or uploaded photograph alone does not confirm what arrived.
Record the receipt once in the agreed system and leave the unresolved quantity visible. Confirm mapped stock updates before repeating an action.
If your receiver is also your prep cook, this is hard. Schedule receiving responsibility within paid working time, with enough coverage to check the delivery before prep consumes it. The required time depends on the order and the receiving checks.
7. Add recipe costing when you need dish-level estimates
Recipe costing is an optional layer alongside ordering, receiving and counts. Link ingredient quantities, purchase-pack conversions and usable yields to recorded prices when you need to estimate the ingredient cost of a dish.
recipe contribution before other variable costs = menu price − sum(as-purchased unit cost × usable recipe quantity / usable yield fraction) − packaging
Check the price basis, yield and portion quantity before interpreting a cost change. For example, a recipe recorded at 100g but portioned at 110g understates that ingredient's usage. The food cost calculator supports an illustrative dish-level calculation. Recipe contribution is not net profit after labor, rent and other costs, and estimated usage does not establish the physical stock remaining.
8. The waste log
Track waste. All of it. Spoilage, breakage, comps, employee meals, mistakes. Tag each event with quantity, item, and reason. Over a quarter you'll see patterns: a particular protein spoils more, a specific shift has more breakage, certain dishes get comped disproportionately.
Separate spoilage from trim, breakage, staff meals and complimentary items. Those events can improve planning, but their combined percentage is not automatically a daily decay rate.
9. Accounting handoff to QuickBooks/Xero
Keep the PO, supplier invoice and receiving record distinct but connected. For a supported QuickBooks or Xero setup, verify the vendor, item and account mappings and agree which system creates each bill or credit. A partial receipt does not automatically establish what the supplier should invoice.
Have the bookkeeper review one changed order, partial receipt and invoice during the trial. Inspect the resulting accounting record and recovery process rather than assuming the connection handles every exception.
What to look for in a restaurant procurement system
Six requirements:
Orders from usable stock. Check current counts, eligible incoming quantities, supplier packs and destination before sending.
A delivery-specific checklist. Give the receiving shift the approved order and a way to record partial quantities and differences.
Counts that inform the next order. Enter physical quantities in consistent units and review differences before applying an adjustment.
Reviewable supplier changes. Keep proposed prices, substitutes and dates beside the buyer's decision and supporting message.
A supported existing-stack setup. Verify the required POS and communication channels. Add recipe and sales mappings when needed; do not assume every edition or portal is supported.
A reviewed accounting handoff. Test PO, invoice, receipt and credit handling with the person responsible for the books.
LineNow's restaurant workflow connects supplier orders, printable receiving checklists, phone receiving at supported locations, and physical count checklists. The team records and reviews what arrived and what remains; the owner can follow purchasing across locations. Supplier messages and delivery documents provide context, not a substitute for physical checks.
Evaluate it when an owner has delegated purchasing but still needs visibility into changes, receipts and the next order. Keep the existing POS and accounting system, and verify the required connections during setup. Recipe costing can support the workflow without being the starting requirement. See current pricing and trial terms for the offer.
A 60-second diagnostic
Three questions:
Can the next shift distinguish the original order, supplier proposal and buyer-approved change?
Can the receiver record a partial delivery, then can a later count inform the next order without forgetting what is still incoming?
Can the bookkeeper explain the invoice using the approved order, accepted quantities and unresolved exceptions?
If an answer is unclear, identify the missing record or owner and test that handoff first. A clearer process may be enough; use a software trial to establish whether the team can complete and maintain it.
Procurement for Bars and Cocktail Bars — spirits, draft beer, and wine-by-the-glass procurement under three-tier distribution, with cocktail BOM demand inference and peak-night PAR planning
