What is PrepTable?
PrepTable is the back-of-house module for campus dining. It runs everything before and after the sale: inventory, vendors, recipes, menus, signage, and the kitchen line. It does not process sales, take payment, or set prices — that's Saavor's job.
The boundary matters. If you're coming from a point-of-sale that attempts to do its own inventory, you'll be used to fields and features that are deliberately absent here. This page orients you in under five minutes.
The one-line summary
Saavor rings the sale. PrepTable runs everything before and after it.
What runs in PrepTable
- Inventory — stock counts, par levels, and low-stock alerts, scoped per campus
- Vendors & purchasing — who you buy from, what they charge, and the purchase orders you send them
- Recipes (meals) — ingredient lines with quantities and costs; the plate-cost rollup lives here
- Menus & signage — what cooks today, by daypart, by campus; pushed to dining-room displays that rotate on their own
- Kitchen display — a live queue of orders flowing from the register to the pass
What runs in Saavor (not here)
- The point-of-sale transaction workflow itself
- Payments and PCI compliance
- Online and mobile ordering
- Sell-price configuration and any kind of "pricing"
- Sales reporting and reconciliation
Selling price is the POS's territory. Plate cost (the cost of making the dish) is PrepTable's territory. Margin — the difference — is calculated by joining the two: Saavor holds the sell price, PrepTable holds the COGS, the report joins them.
What "multi-location" means for you
If your school has more than one campus, PrepTable treats each campus as a first-class operation. A menu is a template; a placement decides which campus it fires at, for which daypart, on which day. Inventory is per-campus. Reorder thresholds are per-campus. The same onion SKU can sit at par 30 in Harlingen and par 50 in Waco without either campus seeing the other's number.
The catalog — items, recipes, vendors — stays tenant-global, so your SKU list isn't duplicated per campus. That's the data-model detail; the experience is: one sign-in, pick a campus, work in its scope.
Where to go next
- How PrepTable fits with Saavor — the boundary, in detail, including what's deliberately out of scope and why
- For Floor Staff — task recipes for the kitchen line
- For Managers — daily workflows for campus managers