Shopify ↔ Sage 200 Integration
ShopifyEcommerce platformOrders into SOP, stock/prices back out, B2B pricing tiers, multi-store fulfilment — bespoke where Shopify connectors fail (complex price lists, SOP workflows, multi-warehouse).
Shopify runs the storefront; Sage 200 runs the commercial side — stock, cost prices, customer accounts, nominal posting, order workflow. The integration is the loop that keeps them in sync: Shopify orders import to Sage 200 SOP with the right analysis codes, shipping treatment and payment state; Sage stock and web pricing push out so the store can't sell what isn't there or charge what isn't permitted; despatch/tracking status travels back so customers see 'shipped' in Shopify without logging into Sage. Where Shopify's standard connector apps work for simple stores, we build bespoke where off-the-shelf fails: complex price bands, multi-warehouse allocation, multi-store Shopify Plus to single Sage ledger, SOP workflows that need custom routing and approval, or multi-channel where Amazon/eBay needs eSellerPro while Shopify needs this bespoke layer.
Data Flows
- 1
Orders → SOP
Shopify orders import to Sage 200 SOP — customer matched or created under a web umbrella account, lines mapped by SKU, shipping as a proper charge line, payment status driving allocation or hold (cash-with-order, account). Multi-store Shopify Plus feeds into single Sage 200 company; per-store routing handled via analysis codes or SO logic.
- 2
Stock & prices → store
Free stock minus allocations feeds Shopify storefront on a schedule; backorderable lines get their own handling. Customer-specific pricing tiers, price bands and quantity breaks resolve in Sage the way they do at trade counter — complex discount rules that go beyond Shopify's native price rules. Prices push out — so a Sage price change updates the storefront without a separate login.
- 3
Despatch & tracking → Shopify
Sage despatch status + carrier tracking writes back to Shopify order, firing its 'shipped' emails and keeping the customer self-served. Multi-warehouse despatch requires explicit mapping of warehouse to store (so Shopify Plus store A sells from warehouse X, store B from Y) — tracked via analysis codes or SO routing.
- 4
Customers → Shopify
Customer records publish to Shopify for segmentation, marketing and self-service — name, address, payment terms, tax codes, credit status. Where Shopify Plus multi-store maps to single Sage account, we handle the ownership split via customer groups or tags to avoid duplicate records.
Where These Integrations Go Wrong
The failure modes we design around — most Shopify ↔ Sage projects hit at least two of these.
Multi-warehouse ↔ multi-store mapping
Each Shopify store may ship from different Sage 200 warehouses; the mapping must be explicit data, not code, or stock sync gets confused. We model each store-warehouse pair as a rule table (store → warehouse → allocation method) so you can sell to multiple stores without double-counting stock.
B2B pricing complexity
Shopify's price bands don't easily map to Sage's price-band matrix, negotiated prices, trade counters and quantity breaks. We handle the Sage-side hard parts — exposing the right price for each customer, the right stock for their branch, and the right order state flows (proforma, backorder, cash-with-order) so the store behaves like your trade counter, not like a generic cart.
SOP workflow customisation
Off-the-shelf connectors import orders as standard SOP, but some businesses need custom workflows (approval before despatch, credit check per customer, routing to specific warehouses, multi-currency handling). The integration builds these SOP rules in Sage rather than baking them into code.
Multi-store ownership split
Shopify Plus stores are separate entities but may share the same Sage 200 company. The integration handles ownership without duplicate customer records, and maps sales to the right analysis codes per store while maintaining a single ledger.
What's Included
- Shopify order import to Sage 200 SOP with customer matching, payment-state gating and multi-warehouse routing
- Stock and pricing sync out to Shopify including B2B price bands, negotiated prices and quantity breaks
- Despatch/tracking writeback for Shopify 'shipped' emails with warehouse-to-store mapping
- Customer records sync to Shopify for segmentation and self-service (credit status, tax codes, payment terms)
- Multi-store ownership split with analysis-code routing for Shopify Plus multi-store to single Sage ledger
- SOP workflow rules (approval, credit check, routing) embedded in Sage, not code
Who It's For
Sage 200 businesses selling through Shopify where the off-the-shelf connector fails to cover complex B2B pricing, multi-warehouse allocation, multi-store ownership or custom SOP workflows. Includes Shopify Plus multi-store setups feeding single Sage company, distributors with trade-counter pricing complexity, and businesses where Shopify's standard integration can't handle the Sage-side hard parts.
FAQ
How does this handle Shopify Plus multi-store to single Sage 200?
Each store maps to a warehouse and analysis-code rule set — sales post to the same Sage 200 company, but split per store. Customer ownership is unified to avoid duplicate records, while sales attribution and reporting stay per store via tags or analysis codes.
Can complex B2B pricing be mirrored in Shopify?
Yes — Sage pricing (price bands, negotiated prices, trade counters, quantity breaks) resolves in Sage and pushes out as the single price the store shows. Custom discount logic lives in Sage; Shopify just reflects what Sage decides is correct for that customer.
What if we need custom SOP workflows (approval, routing, credit check)?
We build the workflow rules in Sage 200 rather than code — approval stages, credit-check logic, warehouse routing and multi-currency handling all live as Sage SO configuration. Shopify just triggers the workflow on import; the rest is Sage-side routing.
Scope Your Shopify Build
Fixed quote once we know your Sage version, the flows you need and the volumes.