Connecting Shopify to Sage 200, Sage 300, Sage 100, Sage X3 or Sage Intacct

None of Sage 200, Sage 300, Sage 100, Sage X3 or Sage Intacct connects to Shopify on its own. Sage doesn't ship a first-party Shopify connector for any of them. Each one does have a programming interface, so a connection can be built, and for each one there are off-the-shelf connectors from integration vendors, sold by subscription or by quote. Which route makes sense depends on the product, because the five are very different pieces of software with very different interfaces.

This post goes through them one at a time: what the product is, how a program gets data into it, what a Shopify sync looks like in practice, and what's on the market. Then it covers the decisions every build has to make, whichever Sage you run, and what the published prices and timelines look like. ezApps scopes custom integrations for these products; our packaged product, Sagify, covers only Sage 50 and Sage Accounting, which are different products again (see Sage and Shopify integrations for the whole range).

At a glance (November 2026):

Product	Formerly	Typical customer	Runs	Interface for a connector
Sage 200	Sage MMS, Sage 200cloud	UK and Irish mid-market, Standard or Professional	Standard: Sage-hosted data with a desktop client. Professional: on-premise or partner-hosted	Sage 200 REST API, OAuth via Sage ID, under a paid developer programme from 2026
Sage 300	Accpac	Canada, US, Asia-Pacific, Africa; multi-company, multi-currency	Windows and SQL Server, on-premise or hosted	Sage 300 Web API (REST), installed with the web screens; older COM and .NET interfaces
Sage 100	MAS 90, MAS 200, Sage 100cloud	US distributors and light manufacturers	On-premise or partner-hosted, ProvideX or SQL Server	Business Object Interface (COM) on the server; no REST API from Sage
Sage X3	Adonix, Sage Enterprise Management	Manufacturing and distribution, 60+ country localisations	On-premise, single-tenant cloud, or the new Sage-managed X3 SaaS	SOAP and REST web services, GraphQL in recent releases
Sage Intacct	Intacct (acquired 2017)	Mid-sized and larger finance teams, multi-entity	Multi-tenant cloud	XML Web Services API and a REST API (general availability 2025), both behind a Web Services licence

In this post:

• Sage 200
• Sage 300
• Sage 100
• Sage X3
• Sage Intacct
• What every build has to decide
• Buy a connector or have one built?
• How ezApps builds one
• FAQ

Sage 200

What it is. The UK and Irish mid-market product, launched as Sage MMS in 2002, renamed Sage 200 in 2007, and sold today as Sage 200 Standard (smaller teams, data held by Sage in Azure, still used through an installed desktop client) and Sage 200 Professional (the former Sage 200 Extra, on your own server or partner-hosted, up to 999 companies). It's the natural step up from Sage 50 Accounts for a UK business that has outgrown it.

How a connector gets in. Through the Sage 200 API, a REST interface that covers both editions. Access is by OAuth through a Sage ID, with a client ID and secret issued by Sage; a Standard site has the API on by default, a Professional site may need the API enabled on the server. The important change in 2026: Sage has moved Sage 200 API access into a paid developer programme with subscription tiers, in force for new applicants from 1 September 2026 and for existing integrations from 1 November 2026, and customers are no longer meant to obtain API credentials on behalf of a developer. Any connector you buy or commission has to be registered under it, so ask the vendor.

What a Shopify sync looks like. Orders become Sage 200 sales orders (with the customer, the stock items and the VAT rate per line), despatches can be reported back to Shopify with tracking, stock by warehouse flows the other way, and Shopify Payments payouts are posted against the sales ledger with fees to a nominal account. Customers are matched by account reference or email, with guest checkouts under a web-sales account.

On the market. The UK has the most choice: Codeless Platforms' BPA Platform (published from about £175 a month), Zynk Workflow (a one-time setup fee plus annual licence, running on a Windows machine that stays on), DataLink (from £395), Patchworks, Realnet and several Shopify agencies. All are configured, not just installed, so budget for setup days.

Sage 300

What it is. Accpac, under the Sage 300 name since 2012. A Windows product on Microsoft SQL Server, on-premise or hosted by a partner, strong in Canada, the Caribbean and Asia-Pacific, with Standard, Advanced and Premium editions and solid multi-company and multi-currency support. Sage 300 2027 shipped in autumn 2026.

How a connector gets in. The Sage 300 Web API, a REST interface installed alongside the web screens on the Sage 300 server, with HTTP basic authentication and a "Web API" permission in the user's security group. Older integrations use the COM and .NET interfaces. The Web API covers customers, items, orders and shipments, with gaps that matter for e-commerce: the orders endpoint doesn't return closed orders, and shipping a sales order and invoicing it is done through the shipments endpoint rather than a single call. Because the API lives on the server, something has to be reachable from the internet, or a small agent on the server has to poll Shopify, the same question Sage 50 raises.

What a Shopify sync looks like. Orders become order entry (OE) orders, invoices are raised when shipped, customers sync both ways, stock by location feeds Shopify's inventory levels, refunds become credit notes, and shipment status goes back to Shopify.

On the market. APPSeCONNECT (from $99 a month, with shipments and tracking back to Shopify), Commercient SYNC (integrations from $199 a month per connected source, with the sync itself quoted, and a typical 1 to 8 week setup), Codeless Platforms (around £350 a month for Shopify Plus), Acute Data, and eBridge (now Jitterbit), whose Sage 300 Shopify specifics are not published.

Sage 100

What it is. MAS 90 and MAS 200, rebranded Sage 100 in 2012 and briefly Sage 100cloud. A US product for wholesale distributors and light manufacturers, with 20-odd modules. Standard and Advanced run on the ProvideX database; only Premium runs on SQL Server. Sage 100 2026 is the current release, 64-bit only, on-premise or in Sage's partner cloud.

How a connector gets in. Sage 100 is the hardest of the five for a cloud service to reach. Sage doesn't publish a REST API for it. The supported write path is the Business Object Interface (BOI), a COM layer on the Sage 100 server that runs the same business logic as the screens, so an order created through it is validated the way a typed one would be. BOI can't notify an outside system of changes, so integrations poll. Reading through ODBC is fine; writing through SQL bypasses the business rules and is a bad idea. The older SData web interface was deprecated with the 2025.0 release and withdrawn in September 2025, so any connector still built on it is on borrowed time. In practice, a Shopify integration for Sage 100 is a program on the Sage 100 server (or a vendor's REST layer sitting on BOI) talking to Shopify's API.

What a Shopify sync looks like. Orders become Sage 100 sales orders with the customer, items, pricing and tax; inventory by warehouse goes to Shopify; tracking numbers come back from Sage 100 shipping; and, on the better connectors, Shopify payout reports are imported to apply cash receipts and post fees to the general ledger.

On the market. IN-SYNCH (developed by ROI Consulting, sold by DSD Business Systems, on the Sage Marketplace ↗), Web-Stor by Kissinger Associates (Sage Marketplace ↗, real-time two-way with multi-warehouse), Clarity Connect ($599 a month billed annually, 2 to 4 weeks to go live), Greytrix GUMU, BirdDog, Commercient and nChannel. One Sage 100 reseller publishes project ranges of $10,000 to $20,000 for a small distributor and $40,000 to $80,000 or more for a large one, implementation and a year of support included; most of that is configuration and testing rather than software.

Sage X3

What it is. The enterprise ERP, built for manufacturing and distribution, with localisations for more than 60 countries. Historically on-premise or in a single-tenant cloud run by Sage or a partner. In November 2025 Sage announced a next-generation X3 delivered as a fully managed cloud service, branded Sage X3 SaaS, available in the UK and US from mid-2026 with a wider rollout planned, with feature parity across the three deployment models.

How a connector gets in. Three interfaces, which is a strength and a trap. SOAP web services are the classic route: published objects and subprograms that can read, create and modify, throttled by licence parameters that limit how much data third parties can push per period. REST web services (from Update 7 on) read almost anything, but a successful read doesn't guarantee a write for the same object. GraphQL, with mutations for the active operations, is the newest and is what Sage's own samples now target in X3 2026 R1, with connected applications and tokens in place of basic authentication. Which one a connector uses determines what it can do and how it survives upgrades, so ask.

What a Shopify sync looks like. Orders become X3 sales orders on the right company and site, with the Shopify location mapped to the X3 stock site; customers and ship-to addresses sync; stock by site feeds Shopify; deliveries and invoices in X3 send fulfilment and tracking back; refunds become credit memos. Multi-company and multi-site are where X3 builds spend their time.

On the market. Commercient SYNC, Clarity Connect ($599 a month billed annually), APIWORX (flat-fee, around $299 a month), Codeless Platforms, and commercebuild, which is a Sage-specific web store rather than a Shopify connector. Celigo and eBridge are often named but don't publish an X3-to-Shopify product.

Sage Intacct

What it is. Sage's cloud financial system, bought in 2017, used by mid-sized and larger finance teams in the US, Canada, the UK, Australia and elsewhere. Multi-tenant, so there is nothing to install and nothing to host. Every environment created since 2020 is multi-entity: customers, vendors and the chart of accounts are shared lists edited at the top level, and each entity is a separately balancing set of books.

How a connector gets in. Two interfaces, both behind the same licence. The XML Web Services API (one endpoint, POST only) has been the workhorse for years and is still maintained. The REST API reached general availability in 2025 R1 and is where new objects appear first, with OAuth client credentials from Sage's developer console. Either way, you need a Web Services developer licence, which gives a sender ID that the company administrator authorises. Connector vendors handle this one of two ways, and it shows on their Intacct Marketplace listings: some use their own sender ID, so you buy nothing extra from Sage; others require you to hold your own licence.

What a Shopify sync looks like. Orders become Order Entry transactions or AR invoices on the right entity, with a location on every line; customers are created in the shared list; Shopify Payments payouts are posted as receipts with fees and refunds broken out, which is usually the part finance cares about most; and dimensions (department, location, class) are set from Shopify data so the reports work. Inventory is often left to a separate system.

On the market. On the Intacct Marketplace, Venn Technology (contact for pricing, your own sender ID) and Stock2Shop (setup fee plus tiered subscription, their sender ID). Elsewhere, Commercient, Clarity Connect (around $595 a month), Codeless Platforms (from about £350 a month), Synder (accounting-style summaries rather than order entry), Greytrix GUMU and MindCloud. The general iPaaS platforms, Celigo, Boomi and Workato, can all do it; a third-party estimate puts those at $6,000 to $30,000 a year plus a $5,000 to $20,000 build. Sage's own "Sage Network" and "Sage Connect" services don't offer a Shopify link to Intacct as of this writing.

What Every Build Has to Decide

The product changes the mechanics. These decisions are the same for all five, and they're the ones a scoping call is for.

1. Order to what document? A sales order that is later shipped and invoiced, or an invoice straight away. Wholesale orders on terms want the first; prepaid retail orders often want the second. See invoice or sales order for the reasoning, which doesn't change with the ERP.
2. Who is the customer? Guest checkouts under a single web-sales account with the right tax group and terms, named accounts matched by email, reference or a Shopify metafield, and Shopify B2B companies mapped to ERP accounts. Retrying a failed sync must not create a second customer.
3. Which items, which site? Shopify SKUs matched to item codes, with a rule for SKUs that don't exist. Stock to Shopify isn't a copy of on-hand: it's available-to-sell after reservations, safety stock and backorders, per warehouse, mapped to Shopify locations.
4. Tax. What Shopify charged must land as the ERP's tax codes, to the cent, by jurisdiction or VAT rate. Every ERP handles this differently and every one of them has a way to get it wrong.
5. Fulfilment back to Shopify. When the ERP ships, Shopify needs the fulfilment and tracking number, or customers get no shipping email and support gets the call.
6. Refunds and payouts. Refunds as credit notes against the original document. Shopify Payments payouts matched to the orders and fees behind them, so the bank deposit reconciles. This is the step most connectors skip, and the one finance notices.
7. Multi-company, multi-entity, multi-currency. Which Shopify store (or market) posts to which company, entity or site, and in which currency, before the first order goes through.
8. Failure handling. What happens when an order can't post: it waits with a reason, someone is told, and nothing half-posts. An integration is judged on its worst day, not its best.

Buy a Connector or Have One Built?

Off-the-shelf connectors suit a standard setup: one store, one company, orders in, stock out, and a vendor whose mapping options cover your rules. The published prices cluster between $99 and $600 a month for a single Shopify-to-Sage pair, plus setup, with the larger platforms quoted. Setup times published by vendors range from days to eight weeks. Ask three things before signing: which interface they use (and whether it's the one Sage still supports for your version), whether payouts are reconciled or only orders posted, and what happens to an order that fails.

A custom build suits a setup that doesn't fit a vendor's mapping screen: several stores into several entities, rules that depend on tags or customer groups, an existing warehouse or shipping system in the middle, or a product (Sage 100 especially) where the interface itself needs a program on the server. It costs more up front and less per month, and it does exactly what you specified.

How ezApps Approaches One

We take these on as custom projects, scoped before anything is quoted:

1. A scoping call through your Shopify setup and your Sage, mapping what has to sync, in which direction, and what already sits in between.
2. A written scope and a quote for that scope, so you know what you're getting before the build starts. Timelines depend on the scope: one-way order sync is the quickest, two-way inventory, payout reconciliation and multi-entity take longer.
3. Build, test on your data, go live, with support after launch.

We've shipped the same workflow for years in Sagify, our packaged connector for Sage 50 and Sage Accounting, and the failure modes we've already met there (partial refunds across line items, gift cards, multi-currency payouts, Shopify Plus B2B, draft orders that become invoices) are the same ones a Sage 200 or Intacct build hits. Tell us which Sage you run on the custom integrations page.

Frequently Asked Questions

Does Sage 200 integrate with Shopify?

Not out of the box. Sage 200 Standard and Professional expose the Sage 200 REST API, and connectors from Codeless Platforms, Zynk, DataLink and others use it to post Shopify orders as sales orders and send stock back. From 2026 the API sits under a paid Sage developer programme, so confirm your connector is registered.

Does Sage 300 integrate with Shopify?

Not on its own. The Sage 300 Web API, installed with the web screens, lets a connector create customers, order entry orders and shipments and read stock by location. APPSeCONNECT, Commercient and Codeless Platforms sell Shopify connectors for it, and custom builds use the same API.

Does Sage 100 have an API for Shopify?

Sage doesn't publish a REST API for Sage 100. Integrations write through the Business Object Interface on the Sage 100 server, which applies Sage's business rules; the older SData interface was deprecated in 2025. Connectors such as IN-SYNCH and Web-Stor, and custom builds, run on or next to the server for that reason.

Which Sage X3 interface should a Shopify connector use?

It depends on your version. SOAP web services are the longest-standing and most complete for writes; REST reads widely but doesn't write every object; GraphQL is the newest and what Sage's current samples use in X3 2026 R1. Ask the vendor which one they use and what it means for your next upgrade.

Do I need a Sage Intacct Web Services licence to connect Shopify?

A Web Services developer licence, which provides the sender ID, is required for both the XML and REST APIs. Some connectors use the vendor's own sender ID so you don't buy one; others require yours. The listing or the proposal will say which.

How much does a Shopify to Sage ERP integration cost?

Published subscription connectors run from about $99 to $600 a month per Shopify-to-Sage pair, plus setup. Integration platforms are quoted and often land in the thousands a year. Custom builds are priced per project, after the scope is agreed.

Can Sagify connect Shopify to Sage 200, 300, 100, X3 or Intacct?

No. Sagify is built for Sage 50 US, Sage 50 Canadian Edition and Sage Accounting. For the products in this post, ezApps builds a custom integration instead.

---

Related Reading

• Sage and Shopify integrations - Which Sagify fits which Sage, and the products we build custom
• Custom Shopify accounting integrations - Tell us which Sage you run
• How to Choose a Shopify Accounting Integration - A checklist that applies to any ERP
• Does Sage 50 Integrate with Shopify? - The same question for the small-business product