How PrepTable fits with Saavor
PrepTable and Saavor are two halves of the same workflow. The point of this page is to draw the line clearly so neither system is asked to do work that belongs to the other.
The boundary
| Saavor owns | PrepTable owns |
|---|---|
| POS transaction workflow, payments (PCI) | Inventory tracking + low-stock alerts |
| Online and mobile ordering | Vendor management + purchase orders + per-vendor pricing |
| Sales, transaction, and reconciliation reporting | Recipe and plate cost (COGS) |
| Workday, CSGold, TouchNet, StarRez integrations | Kitchen display (live prep queue) |
| Menu sell pricing | Menu display content: availability, dayparts, scheduled changes, allergens |
The headline: PrepTable is never the system of record for a sale. Anything that originates an order, prices it, or settles money belongs to Saavor. When the kitchen display ingests orders from Saavor, the kitchen queue is a read-only projection of what Saavor pushed. PrepTable advances prep state (queued → preparing → ready → fulfilled). It doesn't create, edit, or price orders.
What this looks like in practice
Pricing
If you change the sell price of an entrée, you do it in Saavor. If you change the cost of an ingredient, you do it in PrepTable. The two systems compute margin separately and report it together.
The plate-cost number on a PrepTable recipe is cost only — it deliberately has no sell-price field. The margin report that joins the two reads the sell price from Saavor and the COGS from PrepTable at query time.
Orders
When a cashier rings up an order in Saavor, the order flows to the PrepTable kitchen display as a queued ticket. The line cooks it, taps Start preparing, then Ready. The order is fulfilled in Saavor at the pass. PrepTable never sees the payment, the tip, or the customer's saved card.
If a line cook needs to change an order — substitute a side, void a dish — they do it in Saavor, not in PrepTable. PrepTable can show a "no longer cookable" indicator (the inventory is out) but cannot edit the order.
Recipes
A "meal" or "recipe" in PrepTable is a list of ingredient lines with quantities. It exists to compute plate cost and to drive the menu. A Saavor "menu item" is the thing the cashier sells. PrepTable recipes are not sellable. They are the cost behind sellable items.
Reporting
PrepTable reports inventory usage, low-stock value, waste, and plate cost. Saavor reports sales, voids, labor, and reconciliation. The two systems export CSVs that the business office joins in a spreadsheet; the production reporting pipeline is Saavor's.
What is intentionally not in PrepTable
- Sell pricing, dynamic pricing, or margin configuration. All pricing lives in Saavor.
- Customer records, balances, transactions, loyalty. That's Saavor's domain.
- Online and mobile ordering flows. That's Saavor's domain.
- Payment and PCI. Saavor is the system of record; PrepTable never sees a card number.
If you find yourself wanting to add a "sell price" field to a PrepTable recipe, that's the signal to stop and ask whether the change belongs in Saavor. Crossing the line turns PrepTable back into a POS.
Next
- What is PrepTable? — the orientation, if you skipped it
- For Managers → Par levels — the daily inventory workflow at one campus