Group, brand, and location hierarchy
The chain's structure is native: each level has its own rules and inherits those of the level above.
Platform · Management layer
Multi-store ERP
The rule at the center, the operation in each location, the numbers actually adding up.
The challenge
A standard ERP was designed for one company. The chain has many — with distinct brands and CNPJs — and ends up treating each store as a separate instance or as a line in a spreadsheet. The system that should provide a view of the chain becomes the place where that view is lost.
What this costs
Without an ERP built to understand the chain, month-end close becomes a sum of spreadsheets, and it arrives late. Comparisons between stores aren't reliable because each one calculates its own way. And every new store is one more manual configuration done by hand, tying up the senior resource that the expansion needed to have freed up.
The ERP is multi-store from the ground up: the group → brand → location hierarchy is native, rules flow down from the center, and each level operates within them with the autonomy that permissions define. The consolidated figure is the real sum of operations, on the same calculation basis — not a reconciliation done afterward.
Layer 02
Platform
It's the platform's center: where menu, pricing, permissions, recipe cards, and tax parameters are defined and distributed. The operation layer executes; the data layer consolidates the results across the entire chain.
What this delivers
Central rule with permission-based autonomy
What a location can change is defined by granular permissions, not by trust.
Single product record and recipe card
One product, one recipe card, one cost — shared across the chain and adjustable by brand.
Tax parameters by CNPJ
Each CNPJ operates under its own tax regime, without becoming a separate system.
Electronic invoice (NF-e) import
The inbound invoice feeds the catalog and the stock, instead of being keyed in again.
Automatic stock and COGS
Stock is fed by the operation itself and COGS comes out calculated, not estimated.
Custom reports
Beyond the multi-store reports, the chain can build the exact view it needs.
Financial and operational consolidation
Results summed by brand, region, or entire chain, on the same calculation basis.
Comparison across locations
Same indicator, same methodology, so the store ranking actually means something.
Invoices tied to the chain's product records
Each line of an incoming invoice is linked to the product in the multi-store records, with packaging conversion — stock is posted correctly without retyping.
Conversation with
- Corporate ERP
- BI
- Certified acquirers
- Delivery
Where it applies
In operation
Frequently asked questions
Does this ERP replace my corporate ERP?
It depends on the scope. It covers the food service operation end to end, and when the chain already has a corporate ERP — SAP or TOTVS, for example — it integrates with it instead of competing to take its place. The integrations page details the contract.
How do different brands and CNPJs work within the same structure?
The hierarchy is group → brand → location, and each level can have its own tax rule, menu, and permissions. A change at the brand level applies to its locations without affecting the group's other banners.
Is the consolidated view real-time, or closed by period?
Operations flow continuously up to the platform; the management consolidation keeps pace, and accounting close follows the tax period of each CNPJ.
Talk to a specialist
Your operation has grown. Is your technology ready?
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.
