Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
An invoice number is the accounting system's own to issue, and connecting Shopware to Exact Online is mostly about letting it do that as sales happen rather than in one batch at month end.
An accountant needs invoices in one unbroken run, and a webshop produces sales in whatever order people happen to buy. So the web orders get typed into Exact Online at month end, in a batch, by somebody who is also numbering them as they go, and the sequence holds because that person is careful about it. It holds until they are on holiday. Connecting Shopware and Exact Online lets the accounting system issue the number as each sale arrives, which is the arrangement the bookkeeping expected in the first place and the one that survives somebody being away.
DATA THAT FLOWS BETWEEN THEM
Orders
Order lines
Customers
Invoices
VAT rates
Payment status
Exact Online issues the number when the Shopware sale arrives, so the run stays unbroken without depending on one person keying the month's orders in the right order.
Web sales reach the books as they happen rather than in one sitting at month end, so the last week stops being the week nobody in finance can do anything else at all.
The rate the shop charged travels with the order, so the invoice in Exact Online agrees with what the customer was actually shown and paid at the point of checking out.
The arrangement does not rest on one careful person, which matters most in the month they are away and somebody else is asked to do a job they have never done before.
When a Shopware order is paid, Alumio creates the invoice in Exact Online against the customer, and the numbering is issued there, so the document exists with the right number on the same day the money actually arrived.
When a Shopware order is refunded, the correcting document points at the invoice it relates to rather than standing on its own, so the accountant can follow what happened without asking anybody what it was for.
When the shop has a month four times its usual size, nothing about the bookkeeping changes at all, because the work was never being absorbed by one person who would now have four times as much of it to get through.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
For a business that also sells time, the hour registration tool is the next one. Hours become invoice lines in exactly the way web orders do, and they are usually typed in by the same person at the same point in the month. Alumio holds that connection alongside this one, so both sources of revenue reach the books the same way.
Yes. Alumio creates the invoice in Exact Online as each paid Shopware order arrives, with the customer resolved first so the document lands against the right one. Smaller shops sometimes prefer the day's sales to reach the books as a single summary instead, and that is a setting rather than a different build. What can be created is whatever Exact Online exposes for it.
No. What goes away is the month-end batch, typed from a list of web sales by somebody holding the sequence in their head. What replaces it is a mapping between a Shopware field and the ledger, readable by whoever owns the books. If a tax treatment has to be worked out rather than copied across, the Code Transformer does that part.
Exact Online, and it is worth being firm about that. A webshop can generate a reference and many do, but an accounting system exists partly to guarantee an unbroken sequence, and two systems both numbering the same documents is how a gap appears that somebody has to explain later. The order carries its own reference for matching, and the invoice number belongs to the books.
The one an accountant will find is an invoice issued out of sequence, because a gap in the run is the first thing anybody looks for. Alumio records the numbering the document was issued under and what protected it, so a gap has an explanation rather than becoming a question at the audit. Each transfer is monitored live and logged, a refusal alerts with the reason, retries run where configured, and nothing is lost silently.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
