The first month of a Shopify ↔ NetSuite integration usually feels great. Orders flow in, fulfillment confirmations flow back, inventory updates land within minutes. Then month two starts and things get weird.
Below are the seven pitfalls we see most often after launch — in roughly the order they tend to surface.
1. Tax rounding drift
Shopify rounds tax at line level. NetSuite rounds at order level (or vice versa, depending on your config). On a small order it’s a cent. On a 40-line wholesale order it’s a dollar. By the end of the quarter your tax liability report and your store reports tell you two different stories. Fix: pick a single rounding strategy and post adjustments rather than letting drift compound.
2. Refund + partial-refund mismatches
Partial refunds in Shopify don’t always map cleanly to NetSuite credit memos. Restocking fees, refunded shipping, and gift-card refunds each follow a slightly different code path. Test all four on day one, not when the customer complains.
3. Variant-level inventory desync
Shopify treats each variant as its own inventory item. NetSuite often models the same product as a matrix item with subordinate SKUs. The mapping is fine until someone adds a new size or colour in Shopify — and then the new variant has no NetSuite counterpart, so its on-hand reads zero forever. Build the “unmapped variant” alert before launch.
4. Duplicate customer records
A guest checkout in Shopify and a logged-in account with the same email create two customers in NetSuite unless you dedupe on the integration side. Two months in, you have 4,000 customers and 5,200 NetSuite records. Pick a dedupe key (lowercased email is fine), enforce it in your sync, and run a one-time merge job.
5. Multi-currency exchange-rate lag
If you sell in multiple currencies, Shopify uses its own FX rate at checkout. NetSuite uses the rate from your configured currency provider. The mismatch is small but persistent. Decide whether revenue is reported at the Shopify rate or the NetSuite rate, document it, and tell finance.
6. Fulfillment status loops
If both systems can mark a line as “fulfilled,” they will eventually mark each other in a loop. The fix is to assign a single fulfillment-owner per warehouse, and have the other system listen-only on that state.
7. Webhook retry storms
Shopify retries failed webhooks for up to 48 hours. If your endpoint is down for an hour, you’ll get a thundering herd of replays. Make every handler idempotent on order ID. Build a dedupe table keyed on the webhook ID. Test by replaying yesterday’s events into staging.
The shape of month three
If you handle all seven of these before launch, month two looks identical to month one — boring, in the best way. We’ve seen integrations that ran for three years without a single ticket because of a careful first 60 days. We’ve also seen integrations that needed a rebuild after six months because all seven pitfalls landed at once.
The work isn’t glamorous. It’s tax rounding rules and webhook idempotency. But it’s what separates a one-line entry on a status page from a quarterly fire drill.