Integrations
Your store, your ERP, your warehouse, your 3PL and your accounts should agree with each other, without anybody retyping anything. Getting them there is most of our Shopify work, and it's what we're best at.
You'll be talking to one of us, not a salesperson.
The website, the warehouse and the back office all say something different.
Someone spends their day moving data between systems, and sometimes it doesn't match.
Stock, fulfilment and returns live in their system and never make it back to yours.
Every return takes several people and several screens.
It handles the standard flow, and your business isn't standard.
Orders, stock, returns and finance, built for Motel Rocks and running without manual intervention.
Orders from checkout to despatch, pick and pack, returns and multi-warehouse.
Labels, despatch confirmation and tracking, through MetaPack, ShipStation, Royal Mail, DPD and others.
Order despatch, stock movement, returns and tracking with your logistics partner, including Alaiko and Rydership.
Stock and order systems kept in step with your store.
Sales and refunds into your accounts, correct to the penny, with nobody retyping them.
TikTok Shop, Amazon, eBay and others, with stock and orders in one place.
If it has an API, or a database we can reach, we can usually connect it. Some of our best work is with systems older than the people using them.
Which system owns what?
Most integrations fail because two systems both want to be the source of truth. NetSuite and Shopify are the classic example. Our job is to decide deliberately which system owns stock, orders, customers and prices, then build the link so it's predictable.
No mystery stock counts and no orders falling down the gap. Every integration has error handling, retries and alerts, so a failure gets flagged rather than quietly dropping an order.
Off-the-shelf connectors such as Celigo, Workato and Boomi are a reasonable choice for standard data flows, and if one does the job, use it. We'll say so.
They stop being enough when you need custom field mapping, complex returns with condition routing, a 3PL alongside your ERP, several channels, or your own business rules. Then you're usually paying for several connectors that have to stay in step with each other, and each one has its own limits.
A bespoke layer puts it all in one place, with no connector licence fees on top of the build, and when something changes you ring the people who wrote it.
Returns. The sale is the easy direction. A return has to cross every system: authorisation, label, goods-in, a decision about the condition of the item, stock back on sale or quarantined, and a refund or credit. For fashion retailers, with return rates of 25 to 40 percent, that's where the hours go.
Stock across several locations. Once you've got more than one warehouse, a 3PL and a marketplace, somebody has to decide what's really available and where an order should ship from. That's business logic, and it belongs in one place.
Money. Shopify payouts, refunds, gift cards and VAT all have to land correctly in your accounts. If the totals are out by pennies, someone will spend Friday afternoon finding out why.
Busy days. Integrations that look fine on a quiet Tuesday can fall over in a sale. Rate limits, queues and retries need designing in from the start, so a spike slows things down rather than losing orders.
Shopify and Oracle NetSuite, with Alaiko and Rydership, returns, finance and TikTok Shop, all through one integration.
A custom back office running orders, stock and despatch across several sites.
Shopify orders into FreeAgent, correct to the penny.
Why fashion breaks generic ecommerce software, and what we do about it.
We start by mapping every data flow: what moves, when, in which direction and which system owns it. We test against real order data, because that's where the edge cases are. Then we run it live and watch it closely.
Integrations break when the other side changes, so they need looking after. We do that too, with the people who built it. Not on Shopify? We connect all sorts of systems, so see APIs and integrations.
Not always. Sometimes the right answer is a smaller custom layer between Shopify and your warehouse. We'll tell you if a full ERP is more than you need.
Almost always. We connect to the systems you run rather than replacing them, and that includes old ones.
It shouldn't. We test against real data and bring each flow live in a controlled way.
Yes. You own the code, so you're never tied to us.
Yes, and it's often the best time to do it. See how a migration runs.
Rob on the left, Jase on the right. No sales team and no account managers. One of us is on every job, from the first chat to long after it goes live, and the people writing your code sit in the same small team.
It goes straight to Rob and Jase. You'll hear back from one of us, usually the same day, and we'll tell you honestly whether we're the right people.