Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
A Shopify order either stands alone as a stock sale or belongs to an Isah project, and which of the two it is decides where the cost of filling it finally lands in the books at the end of the job.
Isah organises work as projects, and a project is where the cost of a job accumulates. A Shopify order is either a stock sale, which belongs nowhere near a project, or a line on one, which is how spares and service for a delivered machine usually arrive. Getting it wrong is invisible: the revenue posts, the cost lands somewhere general, and the project the customer is actually spending against closes looking more profitable than it was. Connecting Shopify and Isah turns that into a decision made at the point of order rather than an assumption discovered when the project closes.
DATA THAT FLOWS BETWEEN THEM
Part numbers
Project numbers
Sales orders
Project lines
Stock positions
Delivery dates
A Shopify order carrying a project number becomes a line on that Isah project, so the cost sits where the work is being run rather than in a general account nobody reviews.
Orders with no project attached post as ordinary stock sales, which keeps the simple half of the order book simple instead of forcing every sale through a project structure.
Because project lines and stock sales are separated at the point of order, project margin in Isah reflects what the job actually consumed and closes as a real figure.
A customer ordering spares for a delivered machine does so on the website against their own project, so the call to ask which reference to quote stops being necessary.
When a Shopify order carries a project number, Alumio writes it into Isah as a line on that project, so the cost and the revenue both land on the job being tracked rather than in a general account nobody reviews.
Orders without a project reference are created in Isah as stock sales instead, so a straightforward part sale does not acquire a project structure it has no use for and that somebody then has to unpick a month later.
Stock positions and delivery dates from Isah reach the Shopify product, so a customer ordering a spare for a machine already delivered sees what is available and when it can ship without phoning to ask the service desk.
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.
What happens after the machine is delivered is where the next connection goes, because that is where the long relationship is. An installation and commissioning record is the common addition, since Isah tracks the project that built the machine and the record of how it was set up on site sits somewhere else, and the spares a customer orders on Shopify depend on it. Alumio holds both connections, so the order finds the right configuration.
The project structure is read first, because it decides which shape the order takes. Alumio checks whether a Shopify order carries a project reference, creates it in Isah as a project line where it does and as a stock sale where it does not, and returns stock and dates the other way. An order with a reference Isah does not recognise is held rather than posted either way.
No, and the project is the unit rather than the order. Which Shopify field carries the project reference, what happens when it is absent, and what happens when it is wrong are settings in Alumio's interface, maintained by whoever owns the Isah project ledger. Where a business numbers projects in a way that needs interpreting, the Code Transformer takes that reading.
A stock sale when it stands alone, and a project line the moment it carries a reference to work already under way. Isah accumulates cost against projects, so a spare part bought for a machine being commissioned belongs on that project while the same part bought off the shelf does not, and only the reference on the Shopify order tells them apart. Making the reference the test, at the point of order, is what keeps project margin honest.
The project record is where this fails visibly and the general ledger is where it fails quietly. Isah is reached through the interface it makes available, so a rejected Shopify order is spotted and visible with its reason rather than lost between two systems, alerts fire at once, retries run where configured, and unresolved orders stay listed rather than defaulting to a stock sale, so no project loses the costs that belong to it.
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)
