Every plate, on the ledger.
Your POS sells a chicken quesadilla. PlateLedger writes the tortillas, chicken and cheddar off your stock, tells you what runs out next, and drafts the order before it does.
Start free trial See how it works
3 × Chicken Quesadilla−6 tortillas · −378 g chicken · −180 g cheddar
The order closes on the POS. That is the only thing you do.
PlateLedger connects to Square and Clover with one click and pulls your menu, modifiers and the last 30 days of orders. When an order is completed and paid, it lands on the ledger within seconds. Refunds and voids reverse it.
On Toast, Shift4 or SkyTab? Upload the day's sales-mix CSV whenever you want stock updated. The same file uploaded twice does nothing the second time.
- Square
- Live: menu sync, orders, refunds, webhooks
- Clover
- Live: one merchant per location
- Toast, Shift4, SkyTab
- Sales-mix CSV import with a saved column mapping
- Anything else
- Generic CSV template: date, item, quantity
Every line is multiplied through its recipe.
A chicken quesadilla is 2 tortillas, 120 g of chicken at 5 % trim waste and 60 g of cheddar. Sell three and the ledger reads −6 tortillas, −378 g chicken, −180 g cheddar. Modifiers adjust the maths: extra cheese adds 30 g, no onions gives some back.
Recipes can nest one level, so a taco that uses 60 g of your salsa depletes the salsa's tomatoes and onions in proportion. Sizes are a multiplier: Large is 1.5 × the recipe.
Scroll to replay the depletion. Every quantity is stored in the ingredient's base unit; recipes can use any unit that converts to it.
You hear about it before the shelf is empty, with the maths shown.
Alerts are checked every 15 minutes. "Runs out within lead time" emails you immediately; the rest wait for the daily digest at the hour you choose, and go quiet during quiet hours.
Every alert has a why? that explains itself in plain words, so you can decide whether to trust it or go and count.
Runs out within lead time
Chicken thigh, diced
Based on 14-day average of 12/day; 10 on hand; supplier lead time 2 days.
AcknowledgeSnoozeOrder
- Below reorder point
- Runs out within lead time
- Negative stock
- Unmapped menu items
- POS needs re-authorization
The purchase order is drafted. You approve it.
Suggested orders groups everything that needs ordering by its preferred supplier: par, minus on hand, minus what is already on order, rounded up to whole packs. Need 70 tortillas and the pack is 24? It suggests 3 packs, 72.
Approve, then send: the supplier gets an HTML order with a PDF attached and reply-to set to your address. When the delivery lands, enter the packs received; stock goes up and the ingredient's cost updates itself.
- Draft PO-0142
- Valley Produce · lead time 2 days
- Tortillas, 10 in
- 3 × 24 each
- Chicken thigh, diced
- 2 × 5 kg
- Cheddar, shredded
- 1 × 2.27 kg
- Send order
- Email + PDF, reply-to you
Once a week, reality gets the last word.
The count sheet is built for a phone in a cold room: one card per ingredient, grouped by storage area, big numeric inputs, and the conversion hint beside each field. Count in cases, bags or grams; the sheet stores the base unit.
Submit and the ledger is corrected to what you counted. The difference is the variance, reported per ingredient with its dollar impact, so you can fix a recipe or a portion instead of guessing.
- Walk-in
- Chicken thigh, diced · 1 case = 5 kg
- Counted
- 3.6 kg
- Expected
- 3.82 kg
- Variance
- −220 g · −$2.31
Start with your twenty best sellers.
Connect the POS, build twenty recipes, do one opening count. Tomorrow morning the dashboard tells you what runs out next.