Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Order status and stock from Orderwise appear on a WordPress site in the form a customer can usefully read, rather than in the operational detail that the warehouse itself has to work in.
Orderwise knows a great deal about an order, because it runs the warehouse and the back office together. It knows the order is part-picked, that one line is short, and which bay the rest is sitting in. Almost none of that helps a customer, and some of it actively worries them. What they want is whether it has been sent. The WordPress to Orderwise integration decides which of those operational states a customer sees and what each one is called on the site, so the page answers their question without exposing a warehouse process. Warehouses and customers want different words for the same thing.
DATA THAT FLOWS BETWEEN THEM
Orders
Order status
Stock levels
Customers
Dispatch details
Tracking references
Order progress appears on the site in language a customer understands, so the questions that used to arrive by email are already answered before anybody sends one.
Only the states you choose are shown, so a customer sees that an order is being prepared without also seeing that one line is short and becoming alarmed about it.
Availability comes from Orderwise, so the site sells what the warehouse holds rather than a figure that was true at whatever point somebody last remembered to run an upload.
Because status and tracking are on the site already, the team answering enquiries spends its day on the ones that genuinely need a person to think about them properly.
An order moves through Orderwise and the WordPress account page reflects the stages you chose to show, so a customer checking on progress gets a real answer without having to contact anybody about it in the first place.
Once Orderwise records a dispatch, the tracking reference appears on the site, so the customer can follow the parcel themselves rather than emailing in to ask whether it has actually gone anywhere at all just yet.
Stock levels from Orderwise reach the site, so a customer sees what can be supplied before they order it rather than finding out afterwards that part of what they ordered is going to be delayed by a couple of weeks.
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 review request service is the usual addition, because the moment an order is genuinely delivered is the moment worth asking, and Orderwise is the system that knows when that was. Connecting it means requests go out on real dispatch data rather than a fixed number of days after the order, which is what makes them feel timed rather than automated.
Yes, and which statuses are customer-facing is the decision to make first. Orderwise tracks stages that exist for the warehouse, and showing all of them creates questions rather than answering them. Alumio publishes only the states you nominate, under the labels you choose, and stock travels on the schedule you set.
No, and the thing worth asking is what happens the first time you want to rename a status. Customer-facing wording changes more often than anybody expects, and if each change is a development request the labels stay wrong. Held in a form, they belong to whoever owns the customer experience. The Code Transformer covers the unusual case.
Enough to answer the question they came to ask, and less than the warehouse can see. Being told an order is part-picked with one line short invites a phone call. Being told it is being prepared, then that it has been sent, with a tracking reference, does not. The useful rule is to show states that are true, stable and actionable, and to keep the operational detail where it is useful.
Three things happen: the failure is detected as it occurs, the attempt is logged with the order reference it carried, and somebody is alerted with the reason it was refused. Retries run where configured. What that prevents is a site saying dispatched while the parcel is still in the building, which is the version of this failure that reaches a customer rather than staying quietly internal.
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)
