Multi-unit franchise restaurants: the back-of-house stack the brand doesn't pick.

The franchisor picks your POS. Your margin lives in the systems the franchisor doesn't pick. For a multi-unit franchisee, the back-of-house layer, meaning inventory and food cost, labor scheduling, and accounting, is usually the operator's own choice, and it is where two to four points of food-and-labor margin are won or lost across a portfolio. Most operators treat the whole stack as dictated. It isn't, and the part that isn't is the part that pays.

Read Item 8 of the FDD before you assume the stack is dictated

Most franchisees overestimate what the brand mandates, and the Franchise Disclosure Document says exactly what it is. Under the FTC Franchise Rule, Item 8 (16 CFR 436.5(h)) lists every product and service a franchisee must buy from the franchisor, from an approved supplier, or to brand specification, and it must disclose whether the franchisor collects revenue from those required purchases. The POS is typically mandated, and so is loyalty and often online ordering. Inventory, food-cost, labor scheduling, and accounting are usually listed as approved rather than required. Pull your FDD, read Item 8, and mark what says “required” against what says “approved.” That one read reframes the sourcing question: the systems in the “approved” column are yours to compete, and yours to profit from getting right.

Buyer-side. Supplier-paid. Buyers pay zero. Compensation has zero weight in the Cardinal Index scoring inside the Cardinal Method. Specific commercial terms live only in the private Decision Memo a buyer signs, never on this page.

Per-store back-office reporting is the leak

The most common failure past 15 units is running the back office off each store's POS reporting and a spreadsheet. It works at three units and breaks at fifteen. A POS is excellent at recording what sold. It is not built to tell you what should have been used to make it, which means it cannot show cost variance store by store. A location running three points hot on food cost reads the same on the monthly P&L as a clean one, right up until month-end when the product is already gone and the money with it. The fix is an above-store layer that consolidates every unit into one view instead of fifteen islands of local reporting.

Actual-vs-theoretical variance is the number the POS can't give you

The metric that finds hidden margin is actual-vs-theoretical (AvT) food cost: the gap between what you actually used and what your recipes say you should have used to produce what sold. Crunchtime and PAR's Data Central (now PAR OPS) both build the back office around this: recipe-level theoretical cost, actual usage from counts and invoices, and the variance surfaced per store on a dashboard. Restaurant365 runs the same math tied into the accounting ledger, so daily P&Ls carry it. Crunchtime's own worked example: a 24-unit chain doing $1M per unit, with half the stores running hot, can bleed $200,000 or more a year to variance nobody is watching. That figure does not appear anywhere in a POS report, which is the whole point.

The disqualifying constraint is POS integration, not features

When you choose the above-store platform, the first filter is whether it has a certified, live integration with your brand-mandated POS, not the feature comparison. If sales, labor, and item detail do not flow automatically from the POS the franchisor handed you, someone re-keys it, and the numbers are stale before they are useful. Restaurant365 advertises 400-plus integrations and connections to the major POS systems; PAR OPS lists 200-plus and prices for operators at roughly 20 locations and up; the kitchen layer, such as QSR Automations' ConnectSmart (now part of Crunchtime), pulls order detail off the POS to the kitchen display so the line sees what the register rang. The takeaway is not which platform wins on paper. It is that the platform you like is only usable if it speaks fluently to the POS you were assigned, so confirm the integration is certified and current for your exact POS version before you weigh anything else.

Food safety is a back-of-house system now, not a clipboard

Temperature logging is a compliance obligation the back office can automate. The FDA Food Code sets cold holding for time/temperature-control-for-safety food at 41°F or below, defines the 41–135°F danger zone, and requires cooling from 135°F to 70°F within two hours. Across 15 rooftops, paper temp logs are effectively unauditable and easy to backfill after the fact. Above-store and kitchen platforms increasingly capture temperatures, prep tasks, and opening and closing checklists per site, which turns a health-inspection exposure into a dashboard a supervisor can see before an inspector does. If your back-of-house platform does not cover food-safety logging, price a dedicated tool into the stack rather than leaving it on a clipboard behind the line.

The 5-item vendor screen

1. Certified POS integration: show us a live, certified integration with our exact franchisor-mandated POS and version — not “on the roadmap.”
2. AvT by store: produce actual-vs-theoretical food cost variance per unit for the last 90 days, traced from recipe to invoice.
3. Above-store rollup: one login that consolidates P&L, food, and labor across every unit and legal entity, with intercompany transactions handled.
4. Item 8 fit: confirm nothing you sell conflicts with what our FDD Item 8 lists as required from the franchisor.
5. Food-safety logging: show per-site temperature, task, and checklist capture, and how a failed reading escalates to a manager.

Sources

• FTC Franchise Rule, disclosure items — Item 8 restrictions on sources of products and services (16 CFR 436.5(h)). ecfr.gov
• Restaurant365, Multi-Location Groups (all-in-one accounting, inventory, labor; 400+ integrations; connects to major POS; intercompany and daily P&L). restaurant365.com
• Crunchtime, Food Cost Management / actual-vs-theoretical (AvT) variance for multi-unit operators. crunchtime.com
• PAR Technology, PAR OPS Back Office (Data Central) — inventory, labor, and reporting; actual-vs-theoretical food costing; priced for ~20+ location operators. partech.com
• QSR Automations (by Crunchtime), Kitchen Display Controllers / ConnectSmart Kitchen — KDS integrated with the POS. qsrautomations.com
• FDA, Food Code 2022 — cold holding at 41°F or below; 41–135°F danger zone; cooling parameters. fda.gov

All linked sources were live at time of publish (August 2026). Verify before quoting in a procurement document.