Integrations
You already have an ERP and a POS. We adapt.
We read sales, purchases, stock and the product master from the systems you already run, read-only. Your ERP remains the system of record. Your POS remains your POS.
Does BakeWise write into your ERP?
No. We read sales, purchases, stock and the product master from the systems you already run, and the column mapping is declared once rather than guessed on every upload. Your ERP stays the system of record and your POS stays your POS; what comes back is a proposal your team executes.
BakeWise occupies that layer. We read your systems, calculate what they do not, and hand back proposals your team executes. Nothing gets replaced.
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.
What does this cost today?
- Replacing the ERP is not on the tableYou have run yours for five to fifteen years. Accounting, accounts payable and payroll live there. Migrating it is a twelve-month project and zero value for the customer walking through the door.
- And it still doesn't tell you what to bake tomorrowA financial ERP looks backwards. It doesn't know there is an event two streets away on Saturday, that Monday is a public holiday in your province, and that it will rain in one neighbourhood and not the other.
- Between the two systems there is nothingThe ERP closes the month. The POS takes the payment. Between them — forecasting, production, waste, distribution — sits a layer that today is a spreadsheet and a messaging group.
Before / After
And what changes on an ordinary Monday?
Your stack today vs. your stack read.
| Today | With BakeWise |
|---|---|
| Somebody exports from the ERP into a spreadsheet once a month, by hand. | The files arrive on their own over SFTP, or whoever you choose uploads them. |
| The POS and the ERP call the same product different things, and nobody has fixed it. | Every product has one identity, mapped across systems and maintained. |
| Nobody knows whether yesterday's file landed whole or stopped halfway. | Every load leaves a trail: what came in, where from, and when it changed at source. |
| The report your ERP produces changes its columns and nobody notices until month seven. | The column map is declared: a re-ordered report fails loudly instead of quietly changing meaning. |
Which numbers can you check?
7
Columns in the published delivery format
100%
Of the access to your systems is read-only
1000
Detail lines per invoice in the TicketBAI schema
3
Languages, and hosting in the EU
What is underneath?
- A published delivery formatSeven columns for sales, plus profiles for products, suppliers, purchases and stock. An open document your accountant can read without calling us. Column order is free: they are detected by their header.
- Product identity solved onceThe same product carrying different codes in four systems is the number-one integration cost. It is solved during discovery with an external-identifier map, and maintained afterwards.
- Reprocessable loadsEvery record keeps where it came from, under which external identifier, and when it last changed at source. If a file lands wrong, it is reprocessed without duplicating anything.
- A revocable read keyThe read API uses prefix-identifiable keys, shown exactly once, revoked by you from the panel. Per-resource permissions and deny-by-default.
- A native connector where one is worth buildingMicrosoft Dynamics 365 Business Central is read through its own API on a schedule. Everything else — SAP, Oracle, whatever you run — is read through its export in the format we publish, delivered over SFTP or uploaded. Both routes land in the same tables.
- Alerts on the channel your managers actually readEmail and in-app notices are there; WhatsApp is the one that gets opened. Each person chooses their channels and their quiet hours in their own time zone, and an unanswered alert is escalated rather than repeated.
- The report your ERP already produces, read properlyYou declare once which column of your file is which field — we do not guess it on every upload — so a re-ordered or re-headed report fails loudly instead of quietly changing meaning. Three streams: products, sales and production. No fiscal opinion, so a German or Portuguese export ingests unchanged, and price is optional on sales because a volume-only history still forecasts. Every file leaves a row-by-row report that names your columns, not ours. Within Group.
What else gets asked before deciding?
Which systems do you connect to?
In two states, with no ambiguity. Available today: data delivery by CSV or SFTP in the format we publish, native POS connectors, a read API with your own key, and delegated upload so your accountant or your vendor can upload the files for you. Every other system — including the ERPs from SAP, Microsoft, Sage, a3ERP and ICG — is connected with a native connector built inside the integration project. The full list and its legal notice sit in the systems block on this same page.
Our ERP is on-premise and has no API. Now what?
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 on your network; or assisted manual delivery in the format we publish. All three start producing results in days, not months.
We are in the Basque Country. Can you read our TicketBAI?
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, so it works the same with an old terminal as with a new one. Reading those files is available today; the scope per provincial tax authority and per model is confirmed during discovery.
Do you write into our ERP?
No. Today we read. The proposals — orders, transfers, the production plan — are executed by your team in your system. Pushing accounting summaries back into your ERP is a later phase and is agreed by contract.
How long does an integration take?
The diagnostic starts with file delivery, in days. A native connector is a project of its own, four to six weeks — discovery, mapping and testing — and it is signed inside the agreement, never before.
Our ERP is not Dynamics and the file is ours. Does that work?
Yes. You upload a sample file, the platform proposes which column is which field, you correct it and confirm: that map is then declared, and from there uploads are validated against it instead of being guessed each time. Three streams — products, sales and production — with no fiscal interpretation, and price is optional on sales because a volume-only history still forecasts. Every file leaves its report with the rejected rows and the reason, naming your columns. Within Group.