ERP for restaurant groups: food cost and the books

A multi-location restaurant group adds an ERP when recipe cost, commissary transfers, and the close across companies outgrow the POS and QuickBooks. Food and labor each account for about 33 cents of every sales dollar, and a typical pre-tax margin is about 5 percent, the National Restaurant Association estimates. QuickBooks Online Plus lists at USD 140 a month, as of October 2026, and tracks up to 40 locations in one company. Business Central Essentials lists at USD 80 per user per month on annual billing for the finance and inventory users who take over those books. The POS your team already likes can stay.

The guest check, the card batch, and the shift still belong on the POS. An inventory app can keep counts and a theoretical recipe cost. The ERP becomes the ledger those systems post into, once you have more than one set of books or a kitchen that sells to your own stores. That split is the decision. License math below prices it for a group in the 20 to 100 employee range.

What the POS keeps and what the books have to absorb

Operators shop for a restaurant ERP and get three different products under one label. Supy describes the loose usage this way: "In the restaurant technology market, ERP is often used loosely to describe specialist back-of-house software." A back-of-house suite prices food, purchasing, and often a location-level P&L. A general ERP prices named users and posts a general ledger, inventory, purchasing, and more than one company.

Rand Group's hospitality comparison states the practical boundary. Restaurant ERP usually does not replace the POS, labor scheduling, inventory counts, recipe costing, loyalty, or online ordering. The ERP is the financial backbone that receives that data for accounting, consolidations, purchasing, and inventory visibility. If the dining room system is fine, replacing it is a second project with its own training cost and its own card-processing contract.

A buyer on the same decision wrote that "for an ERP company, the pos is generally an after thought" (comment). The useful reply on that thread was to keep the system the floor already knows: "don't build your own ... Get the one you like the best and most cost efficient and integrate with the ERP of your choice ... I've integrated with Toast, Micros, Simphony" (comment). Treat that as a design rule for your shortlist. Ask each bidder to show yesterday's sales, tenders, discounts, and tax posting into the ledger from your POS, on your menu, before you talk about a new register. Our guide to POS system and ERP integration walks through what that handoff has to carry.

Odoo is a partial exception on the dining-room side, and only if you want it. Odoo 19 restaurant POS documents floors and tables, bookings, courses, order transfer, bill splitting, and tips, including a tip-after-payment path marked US only. That is floor service. It is not a named restaurant ERP module, and it does not decide your books.

When QuickBooks location tags stop being a close

Intuit's US price page, checked 5 October 2026, lists QuickBooks Online before the displayed 50 percent discount for three months. There is no annual contract.

• Simple Start (List price: USD 38 a month · What the page allows: Entry plan on the same page)
• Essentials (List price: USD 85 a month · What the page allows: Step up from Simple Start)
• Plus (List price: USD 140 a month · What the page allows: Classes and locations up to 40, inventory, 5 users)
• Advanced (List price: USD 340 a month · What the page allows: 25 users, unlimited classes and locations)

The three-month promo shows Plus at USD 70 and Advanced at USD 170. Budget the list price after month three. Plus is enough for many single-entity groups that only need a location tag on each deposit and each food invoice. Forty locations is a high ceiling for a 3 to 20 unit group, so the location cap is rarely the trigger.

The trigger is legal structure. Intuit's pricing FAQ separates QuickBooks Online Advanced, capped at 25 users, from Intuit Enterprise Suite, which it describes as an AI-native ERP for multi-entity organizations. QuickBooks Online itself is not presented as multi-entity consolidation software. A class or a location will not eliminate a sale from your commissary LLC to your store LLC. It will not produce a royalty accrual from a franchisor entity. It will not stop being one company file when an acquisition arrives with its own tax ID.

Rand Group lists the readiness signals as multiple locations or brands, separate legal entities or franchises, a commissary or central kitchen, outgrowing QuickBooks, consolidated reporting, food-cost control, and acquisitions. For a 3 to 20 location operator, read that list from the bottom of the complexity scale. One entity, no commissary, and a food-cost app the chef trusts can stay on Plus or Advanced. Two LLCs, or a kitchen that invoices the stores, is the ERP conversation.

A stack of point tools creates the same pressure even inside one entity. One operator put it as "purchasing software specific solutions (Accounting, Scheduling, HR, inventory, Customer Loyalty, etc) would all add up very quickly with all your data being siloed" (thread). Scheduling and loyalty can stay in the systems the floor already uses. Cash, inventory, and the P&L still need one owner each, or the month-end close becomes a hunt across exports.

How recipe cost becomes a bill of materials

Food is about a third of the sales dollar, on the Association's split, and the same research note says total expenses for an average restaurant jumped 36 percent between 2019 and 2026. The 12 February 2026 State of the Industry release projects US restaurant and foodservice sales of USD 1.55 trillion in 2026 and 15.8 million jobs. It also says 42 percent of operators reported their restaurant was not profitable last year, and more than 9 in 10 cite food, labor, insurance, energy, and swipe fees as significant challenges.

One point of food cost is 1 percent of sales. Against the Association's typical pre-tax margin of about 5 percent, that single point is a fifth of pre-tax profit. The POS can show a void and a discount. It does not, by itself, roll a chicken invoice into the standard cost of a sauce and then into the store that sold the plate.

Neither Business Central nor Odoo sells a restaurant recipe module on the pages that document this. Recipes are bills of materials, and you should see them built on your own items before you sign.

In Business Central, production BOMs are described as recipes or formulas in some industries. They hold components, quantity per, a scrap percent, and versions. Standard cost of a production or assembly BOM rolls up only when the parent and the components use the Standard costing method, through Calc. Production Std. Cost or the Standard Cost Worksheet. If the invoice price moves and nobody rolls the standard again, theoretical plate cost stays old while purchases hit actual. The variance is an accounting balance, which is why the controller feels it before the chef's spreadsheet does.

Manufacturing, including that production path, sits on Premium. Essentials includes finance, inventory, purchasing, warehouse, and multiple companies. Manufacturing is not listed on Essentials. Premium is the license that adds service order management and manufacturing. Assembly BOMs are the lighter path Microsoft documents on the same page: assemble an end item from components without machine or work centers. Whether an assembly BOM can carry your batch yield and scrap is something to prove on a real commissary item. Ask the bidder to post one of your batches both ways and show the journal.

Business Central is not restaurant-specific out of the box. The POS, kitchen, loyalty, and food-cost features described in partner write-ups come from an industry extension such as LS Central, which is not a Microsoft first-party module. Price any extension as its own line. Do not assume it is included in the USD 80 or USD 110 user fee.

Odoo documents the manufacturing side separately from the restaurant POS. Odoo 19 bills of materials cover components, operations, and by-products. Partners use those BoMs as recipes. Odoo does not publish a separate restaurant recipe SKU on that page. Have the demo sell one covered plate and record one batch. Watch whether quantity and cost move when the check closes, or only when someone records production. Those are different operating routines, and the weekly food-cost meeting depends on which one you adopt. The Odoo inventory module is the configuration surface for that stock movement.

Theoretical cost reduces waste only if someone owns the variance. Each week, compare purchases plus inventory change with the standard cost of what you sold or transferred. A growing gap means a recipe version is stale, a yield is wrong, or receiving is loose. The ERP stores the rollup. Your chef and your bookkeeper still have to act on it.

How a commissary moves food and dollars

A central kitchen is either another location in the same company or its own company. The accounting is different, and groups blur it.

Same company: the kitchen produces with a BOM, then a transfer order moves finished goods to the store. You see the inventory in transit. You do not create a sale to yourself. Retail groups already run this pattern for warehouses and stores. The carry-over for a restaurant group is locations, transfer orders, purchasing, and standard cost, which is why our work on retail and ecommerce inventory patterns is the closest service page. This article stays on multi-unit food service: recipe yield, a commissary, and a close across restaurant entities.

Separate company: the kitchen sells to the store. Business Central intercompany partnerships let related companies exchange sales and purchase transactions, with a shared intercompany chart of accounts and dimension mapping, including partners in another tenant. The commissary issues a sales invoice. The store gets a purchase invoice. Consolidation has to eliminate that pair so group sales are what guests paid, not what the kitchen charged the stores.

Odoo handles the same shape with multiple companies in one database plus consolidation. Odoo 19 consolidation merges accounts across companies and supports an imported mapping. The plan that manages multiple companies in one database is Custom. Odoo's pricing page says the One App Free plan allows multiple companies only inside that single free app. Standard is the wrong plan if each store LLC needs its own books.

Restaurant365 publishes a commissary product beside inventory, recipes, purchasing, and accounting, so that stack is a restaurant back office with a commissary module. A general ERP builds the commissary from a company, a BOM, and either a transfer or an intercompany invoice. Ask for that flow on your item list, your units of measure, and your scrap, in a test company you can throw away.

A clean phase-one commissary looks like this:

1. Put the kitchen on its own company only if it has its own tax ID, its own bank account, or arm's-length pricing to franchisees. Otherwise keep it as a location and use transfers.
2. Code the recipes that move the most of the kitchen's output. Each needs quantity per and a scrap or yield figure the kitchen already trusts.
3. Set parent and components to the Standard costing method if you are in Business Central and you want the rollup Microsoft documents.
4. Post one production, one transfer or intercompany pair, and one store receipt. Tie the quantity to a purchase the kitchen made that week.
5. Leave the long tail of recipes for a later phase. A partial recipe file that finance trusts beats a full file nobody maintains.

How multi-entity books close

Location tags tell you which store earned the sale. Eliminations tell you what the group earned after the stores stopped selling to each other.

Picture three companies: an ownership LLC, a commissary LLC, and an operating company that holds the stores. The commissary invoices the operating company. The ownership company charges a management fee. Guest sales sit only on the operating company. A consolidated P&L that adds the three trial balances without eliminations double-counts the food and invents revenue.

Business Central moves the pair through the intercompany partnership above: a sales document in one company and a purchase document in the other. Odoo posts both companies in one database on the Custom plan, then uses an account mapping when you consolidate. In both cases the mapping is the work: the commissary's sales account has to land on the elimination account you choose, every month, including credit memos for short shipments.

Franchise royalties add another company or another dimension. If you collect a percent of sales from franchisees who are not on your books, that cash is often a receivable and a revenue line, fed by a sales report from their POS. If the franchisee is your own LLC, the royalty is intercompany and has to drop out of the group result. Write that distinction into the design. One royalty account used for both cases will misstate both.

QuickBooks Advanced can assign every store its own location, with unlimited locations and a cap of 25 users for the whole company. It still will not post the commissary invoice as a sale in one company and a purchase in another, then remove both in a consolidation. That is the moment a POS you like has nothing to add. Card batches already reached the bank. The unsolved work is the group ledger.

What licenses cost a 10-location group

Two meters get compared as if they were the same bill. ERP list prices are per named user per month. Restaurant back-office suites on the comparison below are per location per month and still need a POS. As of October 2026:

• Business Central Essentials (US) (List price: USD 80 per user per month, paid yearly · Meter: Finance, inventory, purchasing, warehouse, multiple companies. Manufacturing is not included)
• Business Central Premium (US) (List price: USD 110 per user per month, paid yearly · Meter: Essentials plus service order management and manufacturing)
• Business Central Team Members (US) (List price: USD 8 per user per month, paid yearly · Meter: Per named user, annual billing)
• Business Central Essentials (Canada) (List price: CAD 108.50 per user per month, paid yearly, plus tax · Meter: Same Essentials and Premium split)
• Business Central Premium (Canada) (List price: CAD 149.20 per user per month, paid yearly, plus tax · Meter: Manufacturing included)
• Business Central Team Members (Canada) (List price: CAD 10.90 per user per month, paid yearly, plus tax · Meter: Per named user, annual billing, plus tax)
• Odoo Standard (US) (List price: USD 31.10 and USD 38.90 per user per month · Meter: Both figures appear under yearly and monthly toggles)
• Odoo Custom (US) (List price: USD 61.00 and USD 76.20 per user per month · Meter: Multi-company, Studio, external API)
• Odoo light user (US) (List price: USD 8.90 · Meter: Includes POS and manufacturing shop floor as an employee record)
• Restaurant365 Essential (List price: USD 469 to USD 499 per location per month · Meter: Unlimited users. Accounting, inventory, core reporting)
• Restaurant365 Professional (List price: USD 689 to USD 749 per location per month · Meter: Adds analytics, AP automation, fixed assets, custom reports)

US Business Central figures are on Microsoft's US price page. Canadian figures are on the Canada price page. Odoo figures are on Odoo's pricing page. The pricing page shows both figures under yearly and monthly toggles and does not mark which figure is the annual rate, so keep both numbers until the quote marks the annual one. Restaurant365's ranges are from its April 2026 cost comparison, where Essential is described as starting at USD 469 to USD 499. The same article says entry-level restaurant management software may start around USD 150 per location per month, MarketMan around USD 149 to USD 249, and MarginEdge roughly USD 400, and that advanced platforms can exceed USD 500 per location. Those competitor figures are Restaurant365's characterizations, not the other vendors' price pages.

Assume 10 stores, a separate commissary company, and 8 people who need full ERP licenses: controller, accountant, two bookkeepers, purchasing lead, commissary manager, and two area managers who approve orders. Store crews stay in the POS.

On Business Central Essentials that is 8 times USD 80, or USD 640 a month, USD 7,680 a year, before tax and before any extension. If production BOMs on Premium are required, 8 times USD 110 is USD 880 a month, USD 10,560 a year. Team Members at USD 8 are a separate per-user price on that page. They do not replace the 8 full licenses in this example.

On Odoo, multi-company means Custom. Eight users at the two published rates is USD 488 a month or USD 609.60 a month. A light user at USD 8.90 is the shop-floor and POS employee record, not a substitute for the accountant. Standard at USD 31.10 and USD 38.90 is the lower plan, and it is the wrong plan for multiple companies in one database.

On Restaurant365 Essential, 10 locations at USD 469 is USD 4,690 a month, and at USD 499 is USD 4,990 a month, with unlimited users. Professional at USD 689 to USD 749 is USD 6,890 to USD 7,490 a month. You still pay for the POS. The per-location meter hurts a 10-store group with a small finance team. The per-user meter hurts if you put every manager into the ERP. An 80-user Business Central Essentials bill would be 80 times USD 80, USD 6,400 a month, which is a different project from the 8-user bill above. License the people who post and approve. Leave the line in the POS.

Subscription is not the project. Odoo states that implementation services are not included. Companies under 50 employees usually buy implementation as Success Packs from Odoo. Companies over 50 usually use a partner. A restaurant group of 20 to 100 people often sits across that line because headcount includes the floor, while the ERP user count stays in finance and the kitchen office. We implement both Business Central and Odoo for groups of that size. Ask Odoo, or whoever configures it, which of the two Custom rates is annual before you compare it with Business Central's yearly price.

How long the first phase takes

The same hospitality comparison says most ERP implementations take several months to a year, depending on locations, entities, and integrations, and that restaurant ERP cost depends on users, locations, entities, POS integrations, food costing, migration, and support. It publishes no dollar range for the services, so price those lines from the proposal. Our target for a first usable phase is 8 to 12 weeks.

A first phase that matches that target has a short list. One chart of accounts that every entity can map. The companies that exist today, not the brands you might buy. POS daily sales and tender summary into the ledger, with tax and discounts. The commissary path you picked, transfer or intercompany, for the handful of recipes that move the most dollars. Open items for vendors and a stock count on go-live weekend. Historical financials loaded as balances, with item-level history only where a buyer, a lender, or a franchise agreement requires it.

Data migration, the POS connector, recipe modeling, and post-go-live support are separate lines on the proposal. A single fixed fee that swallows all four will move the argument into change orders in month two. If a bidder's timeline runs several months to a year, ask which month the first store's sales hit the new ledger. The rest of the group can follow on a calendar you can staff.

Groups that also manufacture or distribute packaged product, beyond the commissary, share design choices with food plants: lots, yield, and a standard cost that purchasing can explain. A restaurant group that only plates food can keep phase one smaller than a plant.

What to require before you sign

Run the selection as a script on your data. Partner badges do not post your intercompany invoices. Named people, hours, references, a phase plan, and ownership of the configuration do.

1. Ask for the consultants who will configure the companies, by name, and the hours they will spend on the books, the POS posting, and the recipes. A slide of logos is not a staffing plan.
2. Ask for two references at a similar location count, with a commissary or with more than one entity. Call them and ask what they still do in spreadsheets.
3. Require a phase plan that names what is live at the first close and what is deliberately later. Loyalty, scheduling, and online ordering can stay where they are.
4. Require a written statement of who owns the configuration and the integration after go-live, including what you can change without a developer.
5. Have them price data migration, POS integration, recipe or BOM design, any third-party restaurant extension, and support as separate lines.
6. Have them show, in a tenant you can inspect, one production with scrap, one intercompany or transfer pair, one consolidation that eliminates it, and one day of your POS totals tied to a deposit.
7. For Business Central, have them state in writing whether phase one is Essentials plus assembly, or Premium production BOMs. For Odoo, have them state Custom, and which published user rate is annual.
8. Keep the POS unless the floor is already unhappy with it. One buyer in the platform thread was "unimpressed with their POS system" (thread). Unhappiness with the register is a reason to look at registers. The ledger project can proceed with the POS you have.

The call is useful once you know how many legal entities you close and whether the kitchen sells to the stores. Bring a location list, a company list, and a rough count of people who would post in the ERP. We will tell you if Plus or Advanced still fits, and if it does not, which of Business Central or Odoo matches the recipe and consolidation work on your list.

How Flectic can help

Flectic implements ERP on Odoo or Dynamics 365 for companies of 20 to 100 people in the US and Canada, including multi-location operators that close the books across several companies. Flectic sends a written proposal with a fixed price for each phase before work starts. Flectic's ERP implementation service sets a defined scope and price for each phase before it starts. To start, book a free discovery call.

Sources

• Business Central Pricing, Microsoft, October 2026
• Business Central Pricing (Canada), Microsoft, October 2026
• Create production BOMs, Microsoft Learn, October 2026
• Set up intercompany transaction posting, Microsoft Learn, October 2026
• Odoo Pricing, Odoo, October 2026
• Restaurant features, Odoo 19.0, Odoo, October 2026
• Bill of materials, Odoo 19.0, Odoo, October 2026
• Consolidation, Odoo 19.0, Odoo, October 2026
• Best restaurant ERP software for growing restaurant groups, Rand Group, October 2026
• Restaurant Operations Platform Cost Comparison, Restaurant365, April 2026
• QuickBooks Online Pricing, Intuit, October 2026
• Inflation, National Restaurant Association, October 2026
• Persistent cost increases and enduring demand will shape the restaurant industry in 2026, National Restaurant Association, February 2026
• ERP Software for Restaurant: Zoho vs Netsuite vs odoo vs others?, Reddit r/ERP, 2023
• Comment on POS as an afterthought, Reddit r/ERP, 2023
• Comment on keeping Toast, Micros, or Simphony, Reddit r/ERP, 2023
• Restaurant ERP: What It Is and Whether Your Operation Needs One, Supy, April 2026