Eight kitchens, one calendar, one supply loop.
A multi-location restaurant group runs on three coupled primitives. The recipe BOM that defines what a plate is supposed to cost. The prep line that defines how many plates a kitchen can produce inside a service window. The procurement loop that keeps the prep line fed across many locations and many suppliers. When any of the three drifts, plate cost, guest wait, and food-cost percentage move the wrong way at once. Polymr keeps the three on a single operational loop so the central culinary lead, the regional director, and the location GM read off the same surface against the same week.
Six failure modes that govern a multi-location hospitality group.
Each is what a corporate culinary lead, a regional director, or a location GM names when asked why the period close surfaced a four-point food-cost variance the operations team had no view of in time to act on. Each is what Polymr is configured against in the first 30 days.
- Plate-cost drift via recipe driftRecipe PMR-HP-22 specifies 240g protein but Location-Region-North trains chefs to 280g
The HQ recipe library lists 240 grams of the headline protein per plate at a target food cost of $4.85. The opening chef at Location-Region-North was trained four years ago to a 280-gram portion under a prior menu rev, and the muscle memory carries forward through every shift handoff. Plate cost on PMR-HP-22 runs $5.24 at that location, an eight-percent drift against the central target, and the variance does not surface until the monthly P&L closes three weeks after the period.
- Expiry write-off on a forecasted weekendLot L-2204 lettuce expires Friday; the location bought Wednesday for the Saturday rush
The general manager at Location-Region-East placed the produce order Wednesday morning against a forecast that anchored on the Saturday weekend volume. The lettuce lot landed Wednesday afternoon with a three-day shelf life that put expiry on Friday close. Eighteen percent of the lot writes off because the inventory was sized for the wrong consumption window and the prep team has no view of the per-lot expiry against the per-day forecast.
- Prep-line throughput below plan at peakLocation-Region-East peaks at 92 covers/hr but the staffing plan assumes 110
The Friday evening service plan was built against a 110-cover-per-hour throughput pulled from the regional average. The actual prep line at this location tops out at 92 covers per hour because two of the four cold-line stations share a single chef on Fridays and the proteins station hits a salamander queue at peak. Guest-wait times spike nineteen percent against the standard, comp tickets rise the same evening, and the variance only gets discussed at the weekly GM call four days later.
- Consolidated RFQ slips four daysSupplier V-218 RFQ across eight locations consolidates late because each GM signs separately
The corporate procurement team builds a consolidated RFQ on the headline protein across eight locations to capture a volume tier with V-218. The intended window is a Monday RFQ for a Friday award and a following-Monday delivery. Each location GM has to sign their portion of the quantity commitment before the consolidated RFQ goes out, the sign-off flows asynchronously through email, and the consolidated send slips to Friday. The tier discount is missed and the week-over-week food cost holds at the contract price rather than the negotiated tier.
- Menu revision rollout out of syncMenu rev v22 launches Monday; Location-Region-South prints v21 for four service days
The seasonal menu rev v22 was approved at the central culinary review on a Thursday and pushed to the HQ recipe BOM that evening. The printed menu file synced to seven of eight locations through the print-vendor portal by Sunday night. Location-Region-South was missing from the print-vendor distribution list because their GM had been added to the regional roster only six weeks prior. The location runs four service days on v21 with the wrong plate costs in the POS and the wrong allergen disclosures on the printed card.
- Substitute rejected on Friday by location chefHQ-approved substitute PMR-HP-PROT-2 is rejected by the location chef at service start because the texture missed spec
The headline protein is short across the supplier base for a long weekend, and the corporate chef approves an alternate protein under SKU PMR-HP-PROT-2 with a sensory note that the cut and texture sit inside the tolerance for the dish. The Friday opening chef at Location-Region-East tests the substitute on the line, rejects the texture as out of band against the brand standard, and removes the dish from service. Two hundred covers across the evening default to the second-choice dish and the substitute lot sits in walk-in until the Tuesday return-to-supplier window.
Built for the hospitality shape.
Polymr parses CAD and CAM files for custom hospitality equipment. Cookline drawings, bar lines, buffet stations, walk-in panel schedules: the fabricator drawing comes in as PDF, DWG, or DXF, and lands as a typed BOM with a vendor catalog match per line.
Architectural drawings (PDF, DWG, RVT) parse into the same BOM grammar. A new location build-out becomes a customer-ready quote with millwork, equipment, FF and E broken out by area, with cost basis attached to every line from the live vendor catalog. The BOM auto-rolls when the architect re-issues a revision, and the per-line delta surfaces on the open quote.
A reservation calendar that also raises POs.
A 60-top anniversary booking on Saturday is not a sales event for the corporate team and a procurement event for the location chef. It is one event that lands on the calendar and shifts the dairy and bread order on Friday by 38 percent above the rolling baseline. Polymr keeps the reservation surface and the supply surface inside one calendar, so the per-day cover forecast and the per-dock PO sit on the same grid.
Shelf-life is inventory math, not chef memory.
Friday weekend write-offs on produce lots ran twelve to eighteen percent at the locations with the strongest weekend skew. The lot is in the walk-in. The expiry date is on the box. Nobody has the rollup against the forecast until the GM walks the cooler Saturday morning and adds the soft items to the feature board.
Polymr keeps every perishable on hand against a days-to-expiry rollup, scopes against the forecast for the next four services, and routes anything with a coverage gap into the daily feature, a half-pallet adjustment on the next inbound, or a redirected internal transfer between two locations on the same corridor.
| Item | Location | On hand | Received | Expires | Days |
|---|---|---|---|---|---|
PR-LAMB-04 Lamb shoulder, boneless | walk-in 2A | 38 lb | Jun 01 | Jun 04 | 2d |
PR-HAL-12 Halibut fillet | walk-in 2A | 22 lb | Jun 02 | Jun 04 | 2d |
PR-CHX-30 Airline chicken breast | walk-in 2B | 64 ea | Jun 01 | Jun 05 | 3d |
PR-MIX-22 Mesclun mix, prep | walk-in 1A | 14 lb | Jun 02 | Jun 04 | 2d |
PR-CRM-08 Heavy cream 40 percent | walk-in 1B | 6 gal | Jun 02 | Jun 09 | 7d |
PR-TOM-44 Heirloom tomato | walk-in 1A | 28 lb | Jun 02 | Jun 06 | 4d |
Every inbound PO carries a freight ETA and a risk flag against the service it feeds.
Two POs at risk this week. PO-88423 was rerouted Tuesday and now lands Friday 06:30 instead of Thursday 18:00, which puts the Friday lunch protein on the back foot. PO-88438 is on a lane with weather risk against Sunday morning. Both surface against the dock window and the tied event before the planner has to chase the carrier.
What this looked like at an eight-location restaurant group.
- Situation
- Eight locations across three regions ran a 142-item core menu plus four to six rotating seasonal dishes per quarter. Each location operated its own GM-approved produce and protein procurement under a corporate-tier contract list, with a monthly portfolio P&L close that surfaced plate-cost variance four to six weeks after the affected service period.
- What was breaking
- Recipe drift on the headline dishes ran two to nine percent against the central target across the portfolio depending on location, and the variance only landed at the monthly close. Consolidated RFQs on the top-five SKUs missed the supplier tier discount in nine of twelve months because per-location GM sign-off ran asynchronously by email. Friday weekend write-offs on produce lots averaged twelve to eighteen percent at the locations with the strongest weekend skew.
- Recipe BOM + per-location costing
- Consolidated procurement RFQ
- Menu revision rollout
- Per-lot expiry routing
Three workflow families carry the portfolio.
- Recipe BOM + per-location costing
Recipe library in, per-location plate cost out. POS modifiers recompute the BOM at ticket time; recipe drift surfaced shift by shift.
- Consolidated procurement + menu rollout
Per-location forecast roll-up, parallel sign-off, consolidated RFQ against supplier tier thresholds. Versioned menu bundles (recipe BOM, plate cost, allergen footprint, POS modifiers) roll out across locations with miss-detection at first service.
- Per-lot expiry + substitution routing
Per-lot expiry against forward forecast surfaces write-off risk before the lot ages. HQ-approved substitutes carry a service-time veto with a recorded reason from the location chef.
Where this page neighbours.
Hospitality shares operational shape with several other industries; the links below explain the kinship in production-system terms.
- Food and beverage manufacturing
Per-lot trace, per-lot expiry, and per-lot cost flow through hospitality recipes the same way they flow through F&B manufacturing batches. The recall-trace primitive on the F&B side is the same primitive a hospitality group uses when an ingredient lot has to be pulled from service across every location it landed at.
- Furniture / configurable BOMs
Recipe BOMs with substitutions, options, and modifiers behave like configurable product BOMs in a furniture context. The same library-plus-variant pattern that lets a furniture maker reuse 80% of a sub-assembly across configured orders lets a hospitality group reuse 80% of a recipe across dish variants and location-specific tweaks.
- Industrial / multi-location
Multi-location procurement aggregation, per-location operating budgets, and central-versus-local approval flows are the same primitives industrial multi-plant operations rely on. A hospitality group with eight locations is operationally a multi-site shop and the consolidation, sign-off, and variance-reporting patterns carry over directly.
