Multi-store network
One central bakery. All your shops in sync.
From per-shop forecasting to the morning delivery run: BakeWise aggregates demand at the central bakery, generates the production plan and documents every transfer with its delivery note — automatic and idempotent. And if your network spans several companies, the head office publishes catalogue, suppliers and quality standards across the whole network.
How does one central bakery plan for every shop at once?
Each shop is forecast on its own, and the central bakery adds those forecasts into one production plan. What leaves it moves as a transfer with a delivery note behind it, written once however many times the job runs. If the network spans several companies, head office publishes catalogue, suppliers and standards across all of them.
The network calculates and proposes; each shop sees its own, the head office sees it all — nothing moves without a document behind it.
What does this cost today?
- The Sunday-night WhatsApp2-3 hours consolidating messages from each shop manager to decide Monday's production. Every week, the same manual ritual.
- Goods that travel without paperworkThe run from the bakery to the shops leaves with no delivery note and no record. Impossible to reconcile waste, inventory or who received what.
- Every shop is an islandDifferent assortments, suppliers and quality standards in each location or company of the group. The brand dilutes shop by shop.
Before / After
And what changes on an ordinary Monday?
The network's Sunday
| Today | With BakeWise |
|---|---|
| Voice notes over WhatsApp from 7 shop managers. | Per-shop forecasts aggregated on their own at the bakery. |
| Adding it up by hand in Excel. | Central production plan generated on Friday. |
| A two-year-old delivery sheet. | One shipment per shop with its delivery note. |
| Transfers with no document. | Production centres, warehouses and shops declared as what they are, so a plan knows where things are actually made. |
| Each franchisee's royalty recalculated by hand in a spreadsheet every month. | The head office sees stock, expiries and deviations across the whole network. |
| Orders landing at 23:30 for tomorrow's production. | The royalty computed on the month's sales, with its invoice and its trail. |
| The order cutoff enforced by the server; the exception carries a name and a reason. | |
| Every shop visit leaves a score, photos and corrective actions comparable across shops. |
Which numbers can you check?
30min
The weekly coordination ritual
100%
Transfers with automatic delivery note
5–20shops
Per chain with one central bakery
3catalogues
Published across the network
What is underneath?
- Central bakery loopPer-shop forecast → demand aggregation → central production plan → documented transfer → shipment. Idempotent per day.
- Plan of the DayThe morning screen: what to bake, what to send to each shop and which purchases to approve.
- Network catalogueThe head office publishes ingredients, suppliers and HACCP templates to the child companies, with per-child status (in sync / drifted / orphaned) and one-click resync.
- Network governanceDepartment-based permissions (DBAC), persistent network alerts with ack/resolve, and an aggregated view of catalogue and stock per company.
- Network, company, shop — in the address barWhere you are reading from is part of the URL, not a hidden setting. A link to Chamberí's Tuesday opens on Chamberí's Tuesday for whoever you send it to, the back button behaves, and nobody argues about which shop a screenshot came from.
- Who buys, who ships, who owns the recipeThree switches per company decide whether purchasing is central or local, whether stock is pushed or pulled, and whether recipes and processes are locked, overridable or freely editable. Franchise networks get the legally-aware defaults: a franchisor cannot force a franchisee to auto-execute a purchase or fix a price.
- Royalties and brand fees, computed on real salesOne contract per franchisee — flat, a percentage of sales, or both with a floor and a ceiling — and a monthly close that computes each statement and issues its invoice. If the month's sales base is missing, that statement waits for data instead of being invoiced on an estimate. Group only: a fee between two shops under the same tax ID is not a document.
- Shop audits with a derived score and corrective actionsThe visit runs against one of the quality templates you already use: tick the points, attach photos, and on close the system computes the score. A critical failure is flagged beside the number, not inside it — a 92 with a critical is still a critical. Corrective actions are recommendations and stop no order or delivery, and the audited shop signs an acknowledgement of receipt: proof it was received, not that it is agreed. Chain+.
- The order cutoff is enforced by the serverA cutoff time per weekday, a grace margin, and local wall-clock time with the DST shift resolved. In block mode a late order is refused with the next serviceable date — whether it arrives from the app, the B2B portal or the API, not only from the screen that shows the warning. Overriding it is an explicit admin act, with a written reason and an audit record.
What else gets asked before deciding?
How do I designate the central bakery?
During onboarding or in Settings ▸ Locations. Any location can be the central bakery; from then on the shops' demand is aggregated there and the production plan is generated for that bakery.
Invoice or delivery note between my shops?
Same company (same tax ID): delivery note with no VAT — the fiscally correct way for internal movements. Different companies in the group: delivery note + mirror invoices with transfer pricing (Group).
I have 12 shops — how long to set them all up?
Bulk creation by paste or CSV with duplicate detection. And you can delegate the upload of each shop's history to its manager via a link, without giving them an account or platform access.
Chain or Group?
One company with N shops = Chain. Several companies with their own tax ID (subsidiaries, franchises) = Group. Group adds cross-company orchestration: transfer pricing, network catalogue and consolidation.
What happens if a shop changes a shared template?
Per-child drift detection and resync from the head office. Nothing is overwritten silently: you see which child is in sync, which has drifted and which was orphaned.
Can you compute each franchisee's royalty?
Yes, on Group. You declare the contract per franchisee (flat, a percentage of sales, or mixed, with an optional floor and ceiling) and each month every statement is computed and its invoice issued. If a month's sales are missing, that statement waits instead of being invoiced on an estimate. The franchisee sees its own statements whatever its own plan is: it is their bill. What the platform does not do is set resale prices or execute purchases on their behalf.
How do I hold the brand standard across shops?
With shop audits, from Chain. You schedule the visit against a quality template, fill it in on site with photos, and on close the system computes the score and leaves the corrective actions open. The per-shop summary and the trend over time come from that same data. If your network is separate companies, the audited shop signs the acknowledgement — receipt, not agreement — and the actions are recommendations: they stop no order.
Can I close orders at a set time?
Yes, and the server enforces it, not the screen. You set the time per weekday, a grace margin, and whether the cutoff warns, blocks or is off. In block mode a late order is refused with the next serviceable date, whether it comes from the app, the B2B portal or the API. An admin can override it, but has to write the reason and it is recorded.