Restaurant ERP Consultant, Canada

One menu, several provincial tax setups

Canadian restaurant meals attract federal GST, which is combined with the provincial portion as HST in some provinces, while others charge a separate provincial sales tax and Quebec administers QST alongside GST. Each provincial regime has its own approach to prepared food, alcohol and certain small purchases, and those rules have changed over the years. A chain operating in several provinces therefore needs a POS configured differently in each one.

The ERP's job is to receive what the POS calculated, without blending it. I specify that daily sales arrive by location, revenue category and tax type, with GST, HST, PST and QST in their own accounts, so each return is prepared from a reconciled ledger. Delivery app orders are mapped too, since their tax may be shown differently on the platform statement than on your POS. Your accountant confirms the treatment; I build tests around it.

Quebec locations add another layer. Menu items, receipts and some internal documents may need French, and supplier relationships often differ from the rest of the country. I keep the item master bilingual where needed so the same recipe and cost apply in both languages. Hotel restaurants, resorts and liquor licensing questions are covered on my Canadian hospitality ERP page, and broader tax setup on my Canada ERP consultant page.

Delivery app payouts that rarely match the POS

When a Canadian location accepts orders through delivery apps, the order total shown on the POS and the amount deposited later rarely agree. Between them sit commission, marketing programs the restaurant opted into, customer refunds charged back to the restaurant, adjustments for disputed orders and tax on the platform's own fees. A finance team that posts only the deposit cannot see the true cost of the channel or recover errors.

I design the reconciliation around each platform's payout report. Orders are matched to the POS by reference, gross sales are recognized in full, and every deduction is posted to its own account. Tax charged on platform fees is captured from the platform's invoice where one is issued, so input tax credits can be considered by your accountant. Unmatched orders are listed with dates, so the location manager can dispute them while the platform still allows it.

The same model works for your own online ordering, where the card processor's settlement replaces the platform report. Once both are in place, head office sees net margin per channel and location, and can decide where promotions on delivery apps actually pay for themselves. This analysis is often the start of conversations about growing direct ordering, which links ERP data to marketing decisions. The technical scope is part of my ERP integration work.

Franchisees, franchisors and the supply chain between them

Franchised restaurants are a familiar part of the Canadian landscape, from quick service to casual dining. For a franchisee, the ERP must calculate royalties and advertising fund contributions exactly as the agreement defines gross or net sales, and produce the reports the franchisor requires. For a franchisor, the picture is wider: corporate locations, royalty invoicing to franchisees, and often a supply arrangement where the brand or a designated distributor sells proprietary products to every location.

I document these flows before any configuration. On the franchisor side, that includes how franchisee sales data is collected when franchisees use their own POS, how royalties are invoiced and collected, how rebates from approved suppliers are tracked and how commissary or distribution sales to franchisees are priced and taxed. On the franchisee side, it covers matching royalty invoices to reported sales and comparing food cost against the brand's targets.

Some provinces have specific franchise legislation covering disclosure and the relationship between the parties. Those are legal questions for your franchise lawyer, not design questions for me; I make sure the system holds the data a lawyer or auditor might need. For the general restaurant model, including central kitchens and theoretical food cost, see ERP for restaurants.

Patios, winters and distributor pricing in Canadian dollars

Seasonality shapes Canadian restaurant demand. Patio season can lift some locations dramatically, while winter storms, holidays and tourism patterns move others. Par levels that suit February leave a downtown patio short in July. I set seasonal par levels per location and review them with managers, so ordering follows the season rather than last month's habits.

Purchasing usually runs through broadline foodservice distributors with contract pricing, plus local produce, bakery and protein suppliers. Some items are imported from the United States and priced with the exchange rate in mind. The ERP holds agreed prices, flags invoice lines above them and pushes current costs into plate costs, so menu price reviews happen with real numbers. Where a group buys directly in US dollars, purchases are converted and landed in Canadian dollars before reaching recipes.

Each location also operates under a food premises permit or license from its local public health authority, with inspection records and food handler training requirements that vary by province and municipality. I record permit details, inspection dates and trained staff on the location record, leaving interpretation to your food safety lead. If you also produce packaged goods for retail, see my Canadian food and beverage ERP page.

Platform choice, QuickBooks migration and remote delivery

A common Canadian starting point is QuickBooks or Sage for each company, a POS with basic inventory, and spreadsheets for recipes, royalties and delivery payouts. The first question is whether a specialist back-of-house stock and recipe app, linked to the existing books, would close the gap on its own. A full ERP becomes the stronger option with a commissary, several provinces and entities, a franchise system to administer or investors expecting consolidated reporting.

When an ERP fits, Zoho, Odoo, ERPNext and Microsoft Dynamics 365 go on the shortlist, and I run each through the same Canadian restaurant cases: a location day in a province with separate PST, a delivery app payout with refunds, a royalty calculation and a commissary sale to a franchisee. Migration covers items, recipes, suppliers, opening stock per location and receivable and payable balances by entity, scoped through my data migration service.

Delivery is remote. Canada spans several time zones, so I schedule live sessions in the window that suits head office and locations from the Atlantic to the Pacific, and record walkthroughs for kitchen managers who work evenings. Go-live is planned outside your busiest season, whether that is patio summer or the holiday period. More Canadian material is on the Canada hub.