Company-owned shop
Executes
Production volumes and orders applied with no intervention, each with its audit record. The company's recipes and flows arrive locked at the shop, unless the company allows a local variant.
Groups and franchises · 20–200+ shops
One engine. Several companies. One plan.
Every company with its own tax ID and its own numbering. Intercompany transfers come out with their delivery note and both mirror invoices, at the price you agreed. And the same agent executes in a company-owned shop and only recommends in a franchised one, because the law allows nothing else.
Read-only · EU hosting · DPA on request · No data migration
What only the whole network reveals
What does the group see that a shop does not?
Three readings a single company never has. Where each margin sits against the network, which fiscal status each country is in, and how the bake-off is planned in the franchisee that has an oven. Each one is a comparison, never an instruction: nobody is told what to charge.
- Transparent P&L and network percentile
Each franchisee sees its own P&L and where it sits in the network distribution —p25, p50, p75— for each line: gross margin, flour cost, labour cost. When a line falls outside the band, a recommendation comes out: “your flour cost is in the network's 80th percentile, alternative supplier suggested”. Never an imposed price — setting resale prices or forcing purchases on a franchisee is prohibited by franchise and vertical-agreement law.
- Fiscal status per country, at a glance
Each company with its country and its regime: Spain, ready for VeriFactu 2027. A packaged-or-unpackaged status per country —Portugal included— says which jurisdiction has a fiscal pack and which does not yet. Without pretending to cover what isn't covered yet.
- Bake-off window for the franchisee with an oven
In the shops that finish product —the “shop with an oven”—, the engine lays out the day: when to defrost, when to proof, and which oven slot each item takes. The plan runs hour by hour, bounded by that shop's oven capacity and its demand forecast.
Every franchisee sees itself against the network, with nobody imposing a price.
The network dialect
How are several tax IDs kept apart and consolidated?
Each company keeps its own tax ID, its own gap-free numbering and its own fiscal regime, and the group reads them together in one consolidated P&L with intercompany movements eliminated. A chain under a single tax ID needs none of this. A group needs it on day one.
What changes when the network is several companies.
- One tax ID per company, with its own numbering
Every company in the network is a tenant with its own tax ID, its own gap-free invoice series and its own fiscal hash chain. We consolidate for reading; we never merge fiscal identities.
- Transfer pricing, frozen onto the document
The markup resolves per parent-child pair — child override, child class, group default — and is frozen together with the VAT rate when the transfer is created. If it cannot be resolved the transfer stops: it is never quietly valued at zero. With the group's special VAT regime elected, the transfer is valued at cost and the markup is held at zero.
- Intercompany transfers, with their paper trail
Request, approval, delivery and paperwork on one thread. When a transfer crosses two tax IDs, both mirror invoices are issued in the same transaction, each in its own company's numbering and fiscal chain. Each tax ID records its own fiscal event.
- Consolidated group P&L, with intercompany elimination
The group result with internal operations eliminated pair by pair. If one company's month is missing, the consolidation is withheld and we name what is missing, instead of estimating it.
- SAML 2.0 SSO with your identity provider
We publish the service-provider metadata per company and consume your IdP's assertion. The session that comes out carries the same permissions, the same expiry and the same immediate revocation as a password login.
- Governance that tells company-owned from franchised
Who buys, who ships and who owns the recipes are three switches per company. A corporate subsidiary is created central; a franchisee is created on hybrid purchasing, with pricing and purchasing in advisory mode.
The governance switch
Can head office impose a price on a franchisee?
No, and the engine is built so it cannot. The production agent computes the same plan for all forty shops. In a company-owned shop it applies it; in a franchised one it proposes and waits. That distinction lives on the company record and the server checks it on every write.
The same agent. Two legal postures. Enforced in code.
Franchised shop
Advises
The plan arrives as a suggestion: the franchisee approves or rejects it, and the signature is recorded. Neither resale prices nor purchases are executed on their behalf.
A franchisee can never grant itself authority
Authority over the brand's master recipes and flows is granted by the parent only. This is not a screen check. The field does not exist on the form a child company can write, the database carries a constraint that refuses it, and a continuous-integration sentinel fails if anyone adds it.
Coexistence
Nothing that already works gets touched.
Your ERP remains the system of record: accounting, accounts payable and payroll are untouched, now and in the last phase. The POS stays in every shop — we read its data, we do not swap the terminal. Your accountant still closes the month and receives exactly what they receive today, in their format. Access is read-only, through a service account you create and revoke, never a person's credentials. And there is no lock-in: your data comes out in CSV or JSON whenever you want, with no exit fee. At this altitude coexistence is not a concession: it is the operation. A group does not stop its invoicing to try something out.
- The ERP, system of record
- The POS, in every shop
- The accountant, closing the month
- A read-only service account of yours
- Exit in CSV or JSON, at no cost
What your ERP does not calculate
We don't compete with your ERP. We occupy what it leaves out.
A financial ERP closes the month very well. None of these five calculations is its job.
- Per-SKU, per-shop forecasting
Your ERP looks backwards. We look forwards, with the weather in each neighbourhood, the public holidays of each province and the events on each street.
- Waste with attributed cause
Not just how much was thrown away: why. Overproduction, expiry, quality or return — attributed per product and per shop. And recorded, wherever the rule demands a documented prevention plan — in Spain, Ley 1/2025: that plan comes out of the forecast-to-production loop itself.
- Per-location P&L in under 24 hours
Sales, true product cost, labour and expenses, per shop, without waiting for the accounting close.
- Coordination between bakehouses and shops
A central production plan, cold-chain distribution, and inter-company transfers with their paperwork. A generic MRP treats a bakery like a factory.
- Network alerts, not network reports
What has drifted in any subsidiary, prioritised by euro impact, not a list of KPIs.
The network screens
The three screens a group COO actually lives in.
Network panel
9 entities · 41 shops
Aggregated network forecast
184,200 units
Next 7 days
Alerts prioritised by euro impact
Waste sustained above targetCritical
Panadería Alde Zaharra · 5 days running · estimated impact €1,840/month
Purchase price deviationImportant
T65 flour · +9% over the framework agreement across 3 entities
Stock-out forecastImportant
82% butter · cover below 2 days in 2 bakehouses
Aggregated forecasting across every entity and the alerts from any subsidiary, in one view.
A reproduction of the real BakeWise interface, with example data.
Two ways to start. Neither forces you to change systems.
Pick the one that fits your structure. Both begin by reading what you already have.
Group route · an intelligence layer on your ERP
- We read, we don't write
Read-only access to sales, purchases, stock and the product master. Your ERP remains the system of record.
- We calculate what your ERP does not
Per-SKU per-shop forecasting with weather and public holidays, waste with attributed cause, per-location P&L in under 24 h, network alerts.
- You adopt modules at your own pace
Intelligence first. Then production, workforce and distribution, if and when it pays off. Accounting stays where it is.
The systems we work with
Two states, no ambiguity: what runs today, and what gets built inside a signed integration project.
Available today
- Data delivery by CSV / SFTP in the published format
- Native POS connectors
- Read API with a bk_live_ key
- Delegated upload (your accountant or your vendor uploads the files for you)
- Ingestion of signed TicketBAI / LROE files (Basque Country)
- Native Microsoft Dynamics 365 Business Central connector (cloud)
Native connector within the integration project
- SAP Business One
- SAP S/4HANA
- SAP Business ByDesign
- Microsoft Dynamics NAV
- Sage 200
- Sage X3
- a3ERP
- ICG Manager
- hioPOS
- Odoo
- Holded
- Glop
- Ágora
Product names and trademarks are used for identification purposes only and are the registered trademarks of their respective owners. BakeWise is not affiliated with, sponsored by, certified by, or endorsed by any of these companies. Connector availability and scope are confirmed during discovery.
The adoption ladder
How do we start?
With the diagnostic. Then three phases you only climb if the previous one paid off: intelligence, execution and platform. No phase starts because the calendar says so — it starts because your team asks for it, and each one is measured against what the last one returned.
Four phases. You only move up if the previous one paid off.
| Phase | Duration | What happens |
|---|---|---|
| Diagnostic | 4 weeks, no cost | You hand over a sales history. We measure how good your data actually is and run a blind backtest over your last 90 days. You come out with a business case in euros, or with a documented “no”. |
| Intelligence | months 2–6 | Read-only across your systems. Forecasting, waste, per-location P&L, alerts and a monthly report in the CFO's language. With actionable proposals from month one: draft orders, transfer suggestions, a production plan. You execute them, in your ERP. |
| Execution | months 6–18 | When your team asks to work inside BakeWise, and not before. In this order: production, then workforce and compliance, then distribution. Purchasing, inventory and invoicing are deliberately left out. |
| Platform | month 18+ | Only if it pays off. General ledger, accounts payable and payroll stay in your ERP for good; in this phase we are the ones sending accounting summaries into it. |
Start by measuring, not by signing.
Four weeks on your real data, at no cost. We measure the quality of your history, run a blind backtest over your last 90 days and put the waste and the hours into euros. If the numbers don't add up, we say so and that is where it ends.
Request the 4-week diagnosticEntry requirements and the scoring rubric are published. You can rule yourselves out without spending a meeting.
Security, data and SLA
What procurement is going to ask, answered in writing.
With the real status of each commitment. What is not done is stated as not done.
- A data processor, not a controller
For the data coming from your systems we are a processor: a DPA per customer, minimisation by default in the extraction profiles, and per-company deletion on request.
- EU hosting and a guaranteed exit
Your data stays on EU territory. Exportable in CSV or JSON at any time, without asking permission and without an exit fee.
- Isolation between companies
Row-level isolation with a parent-child hierarchy and department-based access control. Parent-to-child reads are governed by an explicit authorisation, not by the role.
- Your directory is in charge
SAML 2.0 single sign-on and automatic user provisioning and deprovisioning over SCIM 2.0. When someone leaves your payroll, their access here goes with them without anyone having to remember.
- Certifications: the real status
We are implementing an information security management system. Its scope, policy, risk assessment and a Statement of Applicability covering all 93 Annex A controls are drafted and await management approval. We do not hold the certification and have not engaged a certification body. Independent penetration test: Not yet performed. No date committed. SOC 2: Not started. No date committed.
Questions groups ask
Do we have to replace our ERP?
No. Not in phase 1 and not in phase 4. General ledger, accounts payable and payroll stay where they are, indefinitely.
Exactly what access do you need to our systems?
A read-only service account, created and revocable by you, over sales, purchases, stock and the product master. Never a person's credentials.
What if our ERP is old or on-premise, with no API?
That is the most common case. Three routes, in order of preference: your system drops the files on an SFTP; a lightweight agent that only makes outbound connections, opening no inbound port; or assisted manual delivery in the format we publish.
Every shop is a separate company. How do you handle that?
Each company is a tenant with its own tax ID, its own invoice numbering and its own row-level isolation. A parent's read over a subsidiary is not granted by the role: an explicit per-network authorisation enables it, and a subsidiary never reads another subsidiary or the parent.
How is a transfer between two of our companies valued?
At the markup you set: a group default on the parent, a class for a set of subsidiaries, or an override for one specific subsidiary. It resolves when the transfer is created and is frozen there, together with the VAT rate, so a tariff change never rewrites an already-issued document. If the markup cannot be resolved the transfer stops rather than being valued at zero. And if you have elected the group's special VAT regime, the transfer is valued at cost and the markup stays at zero.
Can we sign in with our identity provider?
Yes, SAML 2.0. We publish the service-provider metadata per company, your IdP posts the assertion to our endpoint, and the resulting session carries exactly the same permissions, the same expiry and the same revocation as a password login. Joiners and leavers too: with SCIM 2.0 your directory creates, updates and deactivates the accounts, so offboarding is one action in one place.
We are in the Basque Country. Is TicketBAI any use?
Yes, and it is the shortest route. The TicketBAI / LROE files your company already issues by law carry line-level sales detail: description, quantity, unit price, discount and per-line VAT. It does not depend on your POS vendor. Reading those files is available today; the scope per provincial tax authority and per model is confirmed during discovery.
Can you invoice on our behalf?
In connected mode, no: your invoicing stays in your ERP, and with it every VeriFactu, TicketBAI or SII obligation. If you later decide to invoice from BakeWise, the platform generates, signs and submits the required records and shows you the real status of each submission, one by one; TicketBAI's provincial homologation is still running its course, and we say so in writing before you sign.
How do you isolate one subsidiary's data from another's?
Row-level isolation with a parent-child hierarchy, department-based access control, and parent-to-child reads governed by an explicit authorisation rather than by the role. We hand over the detail before you sign.
What happens to our data if we stop working with you?
It comes out in CSV or JSON at any time. We are a data processor, not a controller: we sign a DPA per customer and host in the EU.
How much does it cost?
It depends on the number of companies, the number of shops and the scope. The reference we always use: one regional manager costs between €42,000 and €55,000 a year fully loaded, and covers one area. We cover the whole network, every day. The concrete figure comes out of the diagnostic.
We charge our franchisees a royalty. Do you handle it?
Yes. One contract per franchisee — flat, a percentage of sales, or mixed, with a floor and a ceiling — and a monthly close that computes each statement and issues its invoice. If a month's sales are missing, that statement waits instead of being invoiced on an estimate, and the franchisee reads its own statements. What we do not do, under franchise law, is set resale prices or execute purchases on their behalf.
How do we measure the brand standard across the network?
With shop audits against your own quality templates: they are filled in on site with photos, on close the system computes the score, and the per-shop summary and the trend over time come from that same data. A critical failure is flagged apart from the score. The audited shop signs an acknowledgement of receipt — receipt, not agreement — and corrective actions are recommendations: they stop no order or delivery.
Can you prepare the direct-debit collection file?
Yes. With the signed mandates registered and the IBAN validated, the platform builds the SEPA pain.008.001.02 file from the outstanding invoices and your company presents the collection at its bank. Invoices with no mandate come back separately with their reason, and the file — which carries full IBANs — is only handed over through its download, which is recorded.
The conversation starts with a measurement.
Four weeks on your data, at no cost and without changing a single system. At the end there is a business case in euros — or a “no” with its reasons.
Nothing gets migrated. Your ERP remains the system of record.