Order-to-books and stock syncs
Orders, refunds and payouts posted to accounting with tax, discounts and shipping mapped, and one stock count shared by Shopify and the warehouse or ERP.
Shopify runs the storefront and the checkout. Your accounting, stock, shipping and customer records usually live somewhere else, and every order has to reach them. Some of those links are an App Store install. Some need a custom integration. n-frames builds the ones a connector can't handle, so an order placed on Shopify reaches every system behind it without anyone retyping it.
Orders get re-keyed into accounting, the ERP and shipping tools, and stock drifts out of sync across channels.
Stuck on Shopify? Let's solve it →Start with the cheapest option that works. The right-hand column is where stores usually outgrow it.
Ask the app vendor, or whoever is building it for you. Vague answers here become manual work later.
Most connectors handle a full refund. Partial refunds, restocking fees and refunds to a different payment method are where entries go wrong.
If Shopify and the ERP both think they're in charge, the last write wins and counts drift. One system should be the source, the other a copy.
Shopify deposits sales minus fees and refunds. If the connector only posts gross sales, someone rebuilds every payout by hand.
You want a list of failures and a way to resend them, not a gap you find at month end.
POS, marketplaces and several warehouses often sit outside what a simple connector maps. Check against your multichannel setup.
A food business selling direct to consumers on Shopify and to wholesale buyers by email and phone.
Retail and wholesale ran as two separate operations with no shared inventory.
A large wholesale order would use up stock that Shopify still showed as available, so the store oversold.
Processing a single wholesale order took about 20 minutes.
Wholesale buyers order through a B2B portal on Shopify with their own prices, net terms and catalogs.
Both channels draw from one inventory source in the ERP.
Retail orders reach QuickBooks as individual invoices and wholesale orders as net-terms invoices.
ShipStation applies parcel rules to retail and freight rules to wholesale, and customers from both channels sync to HubSpot.
Overselling stopped, wholesale order processing went from about 20 minutes an order to almost nothing, and the ops team moved from order entry to sourcing new products.
Orders, refunds and payouts posted to accounting with tax, discounts and shipping mapped, and one stock count shared by Shopify and the warehouse or ERP.
Buyer logins with negotiated prices, restricted catalogs, net terms and quick reorders, kept in step with your ERP.
New customers and their order history in your CRM, deduplicated, so the sales team sees who's buying what.
Order, shipment and return status in front of the agent, with refunds and reships triggered from the ticket.
A front end built your way, with Shopify still handling the cart, checkout, payments and inventory.
A custom integration is an app installed on your store that uses Shopify's Admin GraphQL API and webhooks. Since 1 January 2026, new custom apps are created in Shopify's Dev Dashboard rather than as legacy custom apps in the admin. Existing legacy apps still work, but anything new starts there. The technical side is covered on our Shopify API integration page.
Before going custom, check two cheaper routes. Shopify Flow handles rules inside the store and can call other systems on Grow and above (see Shopify Flow). And plenty of App Store connectors do the job well for a single location and straightforward refunds. Custom makes sense when the data has to be matched, reconciled or reshaped between systems that don't share a model. If you're still choosing a platform, our Shopify vs WooCommerce, BigCommerce vs Shopify and Shopify vs Wix comparisons cover how each handles integrations. Marketing data is covered under Shopify marketing automation, and checkout logic under checkout customization.
n-frames builds Shopify integrations to accounting, ERP, 3PL and CRM systems, in an app your store owns, with a record of every order that synced and every one that didn't. Bring the system that's causing the most retyping and we'll start there.
Start with our worst-synced system →An App Store connector is usually enough for one location, simple refunds and a standard accounting setup. Custom work pays off when you sell wholesale and retail from the same stock, run several warehouses or a 3PL, or need payouts, fees and refunds to reconcile in your books.
Yes, through several connector apps in the Shopify App Store. The common problem isn't the connection itself, it's that Shopify payouts arrive net of fees and refunds. Our Shopify to QuickBooks guide breaks a payout down line by line.
Deciding which system owns products, prices and stock, then syncing orders into the ERP and stock levels back to Shopify, with a way to catch and resend anything that failed. NetSuite and similar ERPs often need custom mapping for locations, tax and wholesale terms.
Shopify agencies, freelance developers and integration specialists. n-frames focuses on the back-office side: connecting Shopify to accounting, inventory, shipping and CRM systems and keeping those connections running after launch.