Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Orders ready to leave Odoo reach Sendcloud as labels and tracking, so parcels go out on whichever carrier suits them best and the customer hears about it without having to ask anybody in the office.
The shipping option a customer picks at checkout is a promise about speed and cost, not an instruction about which van turns up. Sendcloud works out the carrier from rules you set, which is what lets a business switch carriers or split parcels between them without anybody touching the webshop. Odoo knows what has been picked and packed. The Odoo to Sendcloud integration joins those two facts together, so labels come from real orders, the tracking link reaches the customer, and the packing bench gets on with packing while the rules decide the rest.
DATA THAT FLOWS BETWEEN THEM
Orders
Delivery addresses
Parcel details
Shipping methods
Labels
Tracking updates
A packed order in Odoo produces its shipping label automatically, so the packing bench is not retyping addresses that already exist perfectly well one screen away.
Carrier choice lives in Sendcloud's rules, so switching provider or adding a second one for busy periods is a change there rather than a change to the shop and the ERP as well.
Tracking comes back to the Odoo order, so the customer can see where a parcel has got to and the support inbox stops carrying the same question all week long again.
Because each shipment is tied to the order it belongs to, a repeated attempt is recognised as one rather than turning into a second label and a second parcel going out.
An order is picked and packed in Odoo, and Alumio sends it to Sendcloud, which applies your carrier rules and returns the label, so the parcel is ready to go without anybody typing an address for a second time.
Once a carrier scans the parcel, the tracking reference reaches the Odoo order, so the customer can follow it themselves rather than emailing in to ask whether anything has actually happened to their order since they paid for it.
Heavy items go one way and letterbox parcels another, decided by the rules held in Sendcloud, so the warehouse follows a single process and the difference is handled without anybody making a decision at the bench each time.
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.
A returns portal is the natural next one, because sending parcels out well makes the ones coming back the remaining manual job. The order mapping is already there, which makes adding returns a smaller job than the first connection was, so a return is matched to the order it came from and a refund does not depend on somebody reading a note in a box.
Yes, and the moment that matters is when an order is packed rather than when it is placed. Sending too early produces labels for parcels that are not ready, so Alumio acts when Odoo says the goods are picked, and brings the label and tracking back to the same order. Nothing needs typing at either end.
No, and building it yourself would be the expensive choice here, because carrier rules and address formats change without warning and somebody would own that forever. Setting it up in a form means those changes are a setting rather than a small development job. The Code Transformer remains available if one packing rule genuinely needs it.
Because what they chose was a service, not a company. Next-day delivery can be fulfilled by more than one carrier, and Sendcloud picks the one your rules say suits that parcel, size, destination and cost included. That is a feature rather than a mismatch: it means a carrier can be swapped, or a second one added at busy periods, without changing anything a customer sees at checkout.
Two labels for one order means two parcels and a refund conversation, which is why each shipment is tied to the order behind it. Requests are monitored live, with a record kept of the shipment asked for, and a label Sendcloud will not create raises an alert at once with the reason it refused. Retries run where configured, so nothing is quietly shipped twice or left unshipped.
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)
