Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Account-specific contract pricing and branch stock from Kerridge reach Shopify, so a trade customer who logs in sees the terms they agreed rather than a public list price they will phone to dispute.
Kerridge is built for merchants, so pricing is agreed per account and stock sits in branches rather than one pool. Shopify starts from a single published price and a single inventory number, so the two disagree from day one. Trade customers are quoted list prices online and then phone for their real ones, and large orders get re-entered by hand. A Shopify to Kerridge integration through Alumio moves merchant logic onto the storefront: contract prices resolve per logged-in account, branch availability is exposed, and orders return as documents. The counter and the website quote one business.
DATA THAT FLOWS BETWEEN THEM
Contract pricing
Customer accounts
Branch stock
Product records
Sales orders
Order status
Credit position
Kerridge contract pricing resolves for each logged-in Shopify account, so trade customers self-serve at agreed rates and stop calling the counter to check what they should pay.
Branch-level stock from Kerridge is exposed on the Shopify product page, so a customer sees what is collectable near them rather than a single national figure that misleads.
Shopify orders arrive in Kerridge as documents against the right account, which removes the rekeying step where large multi-line trade orders usually pick up errors.
Staff working in Kerridge and customers browsing Shopify read the same prices, stock and order status, so nobody reconciles two versions of one account by phone.
A logged-in trade customer browsing Shopify is priced against their Kerridge contract rather than the public list, so a buyer who used to phone for a quote on every order completes it themselves without losing the agreed terms.
Alumio surfaces Kerridge branch stock against the Shopify product, so a customer choosing collection sees which branch can actually supply the quantity today and the order is raised against that location rather than central stock.
Past Kerridge order lines are made available in the Shopify account area, so a repeat buyer rebuilds a regular order from what they bought last time instead of searching the catalog or emailing a list to the counter.
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.
More can be connected, and for merchants the next one is usually a carrier or delivery management system, because branch collection and delivery need to be priced and tracked separately. Alumio connects Kerridge, Shopify and the carrier on one platform, so a delivery promise made at checkout reflects what the branch can actually dispatch rather than an assumption built into the storefront.
Yes. Alumio reads contract pricing and branch stock from Kerridge and applies them to the Shopify catalog, refreshed on change or on a schedule you set. Because merchant pricing is per account rather than per product, the price is resolved for the logged-in customer instead of published once, which is what makes trade self-service work on a storefront designed around a single list price.
Alumio is configured, not coded, so the mapping between Kerridge accounts, contract prices and Shopify customers is built in the interface rather than in a bespoke middleware script. Merchant ERPs like Kerridge tend to carry pricing rules specific to one business, and if a discount structure sits outside what configuration can describe, the built-in Code Transformer takes custom JavaScript for that rule alone.
Yes, and it is the flow most trade merchants start with. Alumio resolves the Kerridge price for the account behind the Shopify login, so the same product shows different agreed rates to different buyers, including quantity breaks where the contract defines them. That removes the phone call that normally follows a trade customer seeing a list price, and it lets counter staff spend their time on orders rather than price checks.
A failed price or stock update is caught before a customer trades on it. Alumio watches both connections in real time, keeps a logged copy of every message exchanged with Kerridge, and alerts the team immediately when one is rejected, showing which account or product line failed and why. Retries run automatically where configured, and unresolved messages remain visible in the queue rather than vanishing.
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)
