We connect Shopify to your ERP, warehouse and shipping systems, so stock, orders, prices and customers stay correct without anyone copying them by hand. Moving the data is the easy part: the work is deciding what happens when the systems disagree, and building for the day one of them is down.
Integrations from $10,000
“Skai Digital has been extremely skilled, service-oriented, and professionally competent in their process with us... I am extremely satisfied with the collaboration and would recommend anyone who needs similar services to speak with Skai before ordering services elsewhere.”
Simon Alert KristensenHead of Marketing at EpivityAn integration is data moving between systems, and that part is rarely hard. The work is in what the systems disagree about, and what happens when one of them is slow, wrong or down.
Shopify, the ERP and the warehouse can each show a different number for the same SKU. We give stock one owner at each Shopify location, so a product update can’t overwrite newer quantities. An order placed a minute ago may not be in the ERP yet, so a stock update mustn’t put those sold units back on sale. Writes use Shopify’s compare and swap, which refuses a change if the quantity moved after we read it. Missing stock data is an error, never a zero.
Picked, invoiced, shipped and delivered are separate events, and each system names them differently. An invoice doesn’t prove a parcel left, so we map every status by hand and check it against real orders. A partly shipped order stays partly shipped until the last line has gone, a status never moves backwards, and a customer doesn’t get a second tracking email because a sync ran twice.
A timeout doesn’t tell you whether the write happened. Shopify can also deliver the same webhook twice, and it doesn’t guarantee the order webhooks arrive in. So each change carries a key and a repeat has no effect: one Shopify order stays one order in the ERP. Temporary failures retry with growing delays. Bad data stops with a clear error, so one broken record can’t hold up the rest.
Webhooks get missed, which is why Shopify’s docs tell developers to run reconciliation jobs. We run small, frequent syncs with a full comparison behind them and report anything that doesn’t match. A sync only records its progress after every write has succeeded, so a failed run repeats the work instead of skipping it. We check the counts too: a short page from a source API doesn’t always mean the list has ended.
A price that differs from the list could be an agreed price or a discount, and the amount alone can’t tell you which, so we carry the source of each price through to the order. Currency is requested explicitly on every read. Customers need the same care: a contact with a malformed email or no parent company gets reported for someone to fix, not guessed at.
The worst failure is a silent one. A job that crashes halfway can look busy forever while every later run waits for it, and Shopify deletes a webhook subscription created through the Admin API after 8 consecutive failures. We log every run with its counts, expire abandoned jobs, catch up on missed schedules and alert when a queue backs up.
Every integration starts with this table. Most of the arguments later come from a row nobody filled in.
| Data | Usual direction, and what to decide |
|---|---|
| Products and SKUs | ERP or PIM to Shopify. Decide what happens when two active variants share a SKU. We stop and report it rather than pick one. |
| Stock | ERP or warehouse to Shopify. Decide how warehouses map to Shopify locations and which system owns each one. |
| Orders | Shopify to ERP. Decide how tax, rounding, discounts and shipping lines are booked, and what an edited order does. |
| Order status and tracking | ERP, warehouse or carrier to Shopify. Decide which event counts as shipped, and which system emails the customer. |
| Prices | ERP to Shopify. Decide how customer-specific prices, currencies and discounts are represented. |
| Customers and companies | Often both ways. Decide which system wins a conflict and how contacts map to companies. |
| Refunds and returns | Shopify or warehouse to ERP. A refund isn’t a return: money back doesn’t prove the item is back on the shelf. |
| Invoices and payments | ERP to wherever your team reads them. A zero balance doesn’t prove payment, because a credit note can clear it too. |
Running NetSuite? A NetSuite Shopify integration moves the same data over NetSuite’s SuiteTalk REST web services: Shopify orders become sales orders, item fulfillments and tracking come back, and inventory follows the location rules you set. The hard parts are the ones above. One example: a sales order becomes an item fulfillment at a named inventory location, so your NetSuite locations have to line up with Shopify’s before stock and shipments can.
On Microsoft Dynamics 365 Business Central? We start the same way, with the map of what moves and who owns it, then read real data from its API before anything is written.
Nothing writes to a live system until we’ve seen what it would do.
We list what moves, which system owns it, how often it runs and what should happen when it fails. The scope and price come from this map.
We read real data from both systems to find what the documentation leaves out: SKUs that don’t match, status values nobody listed, missing fields and rate limits.
Each flow gets a queue, retries, duplicate protection and logs, and the rules from the map go into tests.
The integration runs without writing and logs every change it would make. We compare that with what your team expects, and check how many SKUs match.
We start small, read back what was written and widen the scope only when it’s correct. Then we compare the frequent syncs with full reads of the same data.
We monitor the runs and the queues after go-live. We stay on if you want us to, and you own the code either way.
Integrations from $10,000
We map the flows with you on a discovery call, then agree the scope and price before any work starts.
Book a callPrices are in US dollars. Your ERP licence, Shopify subscription and hosting are separate. Changing platform as well? Integrations are rebuilt as part of a Shopify migration. Need screens for your staff too? See Shopify app development. For everything else we build, see Shopify development services.
“You will never work with anyone that is as painless, as good, as creative and as knowledgeable as you guys … I have only praise to say”
Luisa ArangoHead of Marketing & Ecommerce at Kastel ShoesTell us what’s getting in the way or what you’d like to build. We’ll talk through the options and whether we’re the right team to help.
Book a call