Connecting SAP Business One to Shopify means synced inventory, automated orders, and one source of truth. This guide covers 4 integration methods, real data flows, common pitfalls, and how to scale beyond a single channel.
Running your back office on SAP Business One while selling through Shopify is increasingly common — and increasingly painful when the two systems don’t talk to each other. Your finance team works in SAP. Your ecommerce team works in Shopify. And somewhere in between, someone is manually copying orders into SAP, reconciling inventory in spreadsheets, and praying nothing falls through the cracks during a flash sale.
Over 70% of mid-market companies using both an ERP and an ecommerce platform report data consistency as their top operational challenge, according to Statista’s enterprise software survey. The fix isn’t working harder — it’s connecting the systems properly. This guide walks through exactly how to integrate SAP Business One with Shopify, the trade-offs between different methods, and what to watch out for when your business inevitably grows beyond a single sales channel.
SAP Business One handles your financials, purchasing, inventory valuation, and warehouse management. Shopify handles your storefront, customer experience, and online transactions. Without integration, you get two separate systems that each believe they are the source of truth — and neither is fully correct.
Here is what changes when they are connected:
Inventory accuracy goes from “roughly right” to real-time. When a customer buys a product on Shopify, the stock count in SAP adjusts immediately. No more overselling because someone forgot to update a spreadsheet. No more blocking stock that’s actually available because the systems are out of sync. (For a deeper look at Shopify-side inventory tools, see our Shopify inventory management guide.)
Order processing drops from hours to minutes. Instead of someone manually entering Shopify orders into SAP for invoicing and fulfilment, orders flow automatically. The sales order appears in SAP, triggers your existing approval and fulfilment workflows, and updates Shopify with tracking information when the shipment goes out.
Financial reporting becomes trustworthy. Revenue, cost of goods sold, tax collected — all of it lands in SAP automatically, coded to the right accounts. Your finance team stops spending the first week of every month reconciling ecommerce transactions.
Actionable Insight: If your team spends more than 2 hours per day on manual data entry between SAP and Shopify, the integration will likely pay for itself within the first month. Track the hours for one week before starting — it makes the business case concrete.
The problems compound as you grow. At 50 orders per day, manual entry is tedious but manageable. At 200 orders per day, it requires dedicated staff. At 500+ orders per day, errors become inevitable — wrong items shipped, inventory mismatches, delayed invoicing, and customer complaints that damage your brand.
Companies running SAP and Shopify without integration typically report 3-5% order error rates, compared to under 0.5% with automated data flows. That gap represents real revenue: returns, reshipping costs, customer churn, and marketplace penalties if you also sell on platforms with strict fulfilment SLAs. If you are evaluating ERP options alongside this integration, our ERP systems in Singapore guide covers the broader landscape.
Before choosing an integration method, you need to understand exactly what data moves and in which direction. Most SAP-Shopify integrations handle these core flows:
| Data Type | What Syncs | Frequency |
|---|---|---|
| Products | Item name, description, images, weight, dimensions, variants | On change or scheduled batch |
| Inventory | Available stock quantities per location | Real-time or near-real-time |
| Pricing | Base prices, promotional pricing, tiered pricing | On change |
| Fulfilment updates | Tracking numbers, carrier info, delivery status | On shipment |
| Data Type | What Syncs | Frequency |
|---|---|---|
| Orders | Line items, quantities, customer details, shipping address, payment status | Real-time |
| Customers | New customer records, updated addresses | On order or on change |
| Returns/refunds | Return requests, refund amounts, restocked items | On event |
| Tax collected | Tax amounts per jurisdiction | With order data |
| Data Type | Why Two-Way | Conflict Rule |
|---|---|---|
| Inventory levels | SAP adjusts for purchasing/receiving; Shopify adjusts for sales | SAP is master for total stock; Shopify reflects allocated/available |
| Product status | Items activated/deactivated in either system | SAP is master (active in SAP = publishable on Shopify) |
Actionable Insight: Define your “master system” for each data type before starting integration. The most common — and usually correct — setup: SAP is master for products, pricing, and inventory. Shopify is master for orders and customer interactions. Trying to make both systems master for the same data type is a recipe for sync conflicts.
There is no single right way to connect these systems. The best method depends on your order volume, technical resources, budget, and whether Shopify is your only sales channel.
Several apps on the Shopify App Store offer SAP Business One connectors. These are the fastest to deploy and require no custom development.
How it works: Install the app, enter your SAP Business One credentials (or connect via SAP’s Service Layer API), map your data fields, and the app handles sync on a schedule or in near-real-time.
Pros:
Cons:
Best for: Businesses with straightforward product-order-inventory flows and no plans to add additional sales channels beyond Shopify.
Integration platforms like MuleSoft, Boomi, or Celigo act as a middle layer between SAP and Shopify. You configure data flows visually, with pre-built connectors for both systems.
How it works: The middleware connects to SAP’s Service Layer (REST API) or DI API and to Shopify’s Admin API. You build integration flows that map data between the two, handle transformations, and manage error handling.
Pros:
Cons:
Best for: Companies with complex data transformations, multiple ERP modules involved, or plans to integrate additional systems (CRM, WMS, BI tools).
Build a bespoke integration using SAP Business One’s Service Layer REST API and Shopify’s Admin REST/GraphQL API. This gives you full control but requires significant development resources.
How it works: Your development team (or a consultant) builds custom code that reads from one system’s API and writes to the other, handling authentication, data mapping, error handling, rate limiting, and retry logic.
Pros:
Cons:
Best for: Companies with unique business logic that no off-the-shelf connector supports, or those with in-house development teams experienced in both ecosystems.
Platforms like OneCart connect SAP Business One to Shopify as part of a broader multichannel integration. Instead of a point-to-point SAP↔Shopify connection, you get SAP connected to Shopify plus every other channel you sell on.
How it works: OneCart connects to SAP Business One via its standard integration and to Shopify (plus Shopee, Lazada, Amazon, TikTok Shop, WooCommerce, and others) through a single unified layer. Products, inventory, orders, and fulfilment data flow through OneCart’s hub.
Pros:
Cons:
Best for: Businesses selling on Shopify AND other marketplaces or planning to expand. If Shopify is your only channel and always will be, a simpler connector may suffice — but most growing businesses add channels over time. See our comparison of the best multichannel inventory management software for a broader look at the landscape.
| Criteria | Native App | Middleware | Custom API | Multichannel Platform |
|---|---|---|---|---|
| Setup time | Days | Weeks | Months | 1-2 weeks |
| Monthly cost | $100-$500 | $500-$2,000+ | Hosting only | Varies by plan |
| Customisation | Low | High | Full | Medium |
| Maintenance | Vendor | Shared | You | Vendor |
| Multi-channel | No | Possible | Build each | Built-in |
| Best for | Single channel | Complex logic | Unique needs | Multi-channel sellers |
Regardless of which method you choose, the planning process is similar. Here is how to set yourself up for success.
Before connecting anything, document exactly what data lives where and how clean it is.
The most common integration blocker is mismatched identifiers. If your SAP item code is “WH-BLK-M-001” but the same product in Shopify has SKU “black-widget-medium”, you need a mapping table before any integration will work.
Not everything needs to sync on day one. A phased approach reduces risk:
Phase 1 (Critical): Inventory levels (SAP → Shopify) + Orders (Shopify → SAP) Phase 2 (Important): Product data sync (SAP → Shopify) + Fulfilment updates (SAP → Shopify) Phase 3 (Nice-to-have): Customer sync, returns handling, financial reconciliation automation
Use the comparison table above. Key questions:
Create a spreadsheet mapping every field from SAP to its Shopify equivalent:
| SAP Field | Shopify Field | Direction | Notes |
|---|---|---|---|
| ItemCode | SKU | SAP → Shopify | Must be unique |
| ItemName | Title | SAP → Shopify | Max 255 chars in Shopify |
| QuantityOnHand | inventory_quantity | SAP → Shopify | Per location |
| Price (PriceList 1) | price | SAP → Shopify | Excluding tax |
| DocEntry (Sales Order) | order_id | Shopify → SAP | For reference tracking |
Both SAP Business One and Shopify offer test environments. Never test integration against production data first. Set up a Shopify development store and use SAP’s test company database. Run through your core scenarios: place a test order, verify it appears in SAP, ship it, confirm Shopify updates with tracking.
Actionable Insight: Create 10 test scenarios that cover your edge cases before going live. Include: out-of-stock items, partial fulfilments, cancelled orders, refunds, variant-level inventory, and multi-location stock. If all 10 pass, you are ready.
Even with the right method, these issues trip up nearly every SAP-Shopify integration. Knowing them in advance saves weeks of troubleshooting.
SAP uses “ItemCode” as its primary product identifier. Shopify uses “SKU” at the variant level. If these don’t match — and they often don’t — every sync breaks silently. Products appear duplicated, inventory counts apply to the wrong items, and orders reference non-existent SAP items.
Fix: Establish a single SKU format and enforce it in both systems before integration. If you cannot change existing codes, maintain a mapping table in your integration layer and audit it monthly.
SAP Business One calculates tax based on tax groups, business partner tax status, and item-level tax codes. Shopify calculates tax based on the store’s nexus settings and Shopify Tax or a third-party tax engine. When both systems calculate tax independently, discrepancies are inevitable.
Fix: Choose one system as the tax authority. For most businesses, Shopify calculates tax at point of sale (it knows the customer’s jurisdiction) and passes the tax amount to SAP as a line item. SAP records it — it does not recalculate.
SAP’s inventory updates happen in batches (e.g., when a goods receipt is posted or a delivery note is created). Shopify’s stock changes happen in real-time as orders are placed. If your integration syncs inventory on a schedule (e.g., every 15 minutes), you have a window where Shopify’s stock count is stale — and customers can buy items that are already committed elsewhere.
Fix: Use real-time or near-real-time sync for inventory. If your integration method only supports scheduled sync, reduce the interval to the minimum supported (ideally under 5 minutes). For high-velocity SKUs, consider reserving a safety buffer in SAP.
SAP Business One supports multiple warehouses natively. Shopify supports multiple locations. But the two systems model locations differently — SAP warehouse codes rarely match Shopify location IDs, and the allocation logic differs.
Fix: Map each SAP warehouse to a corresponding Shopify location explicitly. If you want Shopify to show aggregate stock (total across all warehouses), your integration must sum the quantities before pushing to Shopify.
SAP generates its own document numbering (Sales Order DocEntry/DocNum). Shopify generates its own order numbers. Without a clear cross-reference, your team will struggle to look up orders when customer service calls come in.
Fix: Store Shopify’s order number as a reference field on the SAP Sales Order (use a User-Defined Field). Likewise, store SAP’s DocEntry on the Shopify order as a note or metafield. Both teams can then search by either number.
Here is the scenario that catches most businesses off guard: you set up a clean SAP-Shopify integration, it works beautifully, and then six months later you add Amazon. Or Shopee. Or TikTok Shop. Or your wholesale team asks for a WooCommerce B2B portal.
Now your point-to-point SAP↔Shopify integration needs a sibling: SAP↔Amazon. And another: SAP↔Shopee. Each integration is a separate project, with its own maintenance, its own failure modes, and its own inventory allocation challenges.
This is where multichannel integration platforms earn their keep. Instead of building N separate integrations from SAP to N sales channels, you build one integration from SAP to the platform, and the platform handles distribution to every channel.
OneCart connects SAP Business One to 13+ sales channels — including Shopify, Shopee, Lazada, Amazon, TikTok Shop, WooCommerce, and more. Inventory is managed centrally, so stock allocated to Shopify is automatically unavailable on Shopee, preventing the cross-channel overselling that plagues businesses running separate integrations.
If you are reading this because you already sell on marketplaces beyond Shopify, or plan to within the next year, starting with a multichannel platform saves you from rebuilding later. If Shopify is genuinely your only channel with no plans to expand, a simpler point-to-point connector is fine — but in our experience, that is rare for SAP Business One users. Companies running SAP tend to sell across multiple channels.
Actionable Insight: Before choosing an integration method, list every sales channel you plan to use in the next 24 months. If the list has more than one entry, a multichannel approach will cost less in total than building separate integrations for each.
These apply regardless of which integration method you choose.
1. SAP is the master for products and inventory. Always. Shopify is a presentation layer for selling — SAP is your system of record. Product data, pricing, and stock levels originate in SAP and flow outward.
2. Sync inventory in real-time, not on a schedule. Every minute of delay is a window for overselling. If real-time is not possible, sync at least every 5 minutes and maintain a safety stock buffer.
3. Use a single SKU format everywhere. SAP ItemCode, Shopify SKU, and any other channel’s product identifier should all be the same string. This eliminates the most common integration failure point.
4. Log everything. Every data sync — whether it succeeds or fails — should be logged with timestamps, record counts, and error details. When something breaks at 2 AM on a Saturday, logs are how you diagnose it Monday morning.
5. Set up alerts for sync failures. A broken integration that nobody notices for 48 hours causes more damage than a broken integration caught in 5 minutes. Configure alerts for: sync job failures, inventory discrepancies above a threshold, and order import errors.
6. Test with real volume before peak season. Your integration works fine with 20 orders per day during testing. Will it handle 2,000 on Black Friday? Load-test before you need to.
7. Plan for returns from day one. Returns and refunds are the most commonly forgotten integration flow. When a Shopify customer returns an item, does the stock reappear in SAP? Is the credit note created automatically? Sort this out during implementation, not after your first return hits.
It depends on the method. A native Shopify app can be running in 1-3 days. Middleware solutions typically take 2-4 weeks including data mapping and testing. Custom API builds range from 4-12 weeks. A multichannel platform like OneCart usually requires 1-2 weeks for SAP onboarding and configuration.
Yes. SAP Business One HANA exposes the same Service Layer REST API as the on-premise version. Any integration method that uses the Service Layer works with both deployment models. Some native Shopify apps may only support one version, so check before purchasing.
SAP Business One stores attachments and images via its Attachments module, but it is not optimised for ecommerce image management. Most businesses manage product images directly in Shopify or in a DAM (Digital Asset Management) system rather than syncing them from SAP. If you do need image sync, confirm your chosen integration method supports SAP’s attachment API.
Most integration tools perform an initial “matching” step — they compare SAP items with existing Shopify products using SKU as the key. Matched items get linked; unmatched items are flagged for review. Always run this matching in a test environment first to catch duplicates or mismatches before they hit your live store.
Shopify discounts (percentage off, fixed amount, free shipping) are applied at checkout and reflected in the order total. When the order syncs to SAP, the discount typically appears as a line-level discount amount or a separate discount line item. Your integration should map Shopify discount codes to SAP’s discount mechanisms so reporting is accurate.
Connecting SAP Business One to Shopify eliminates the manual busywork that slows growing ecommerce operations. Whether you choose a native app, middleware, custom code, or a multichannel platform, the goal is the same: one source of truth for inventory, automated order processing, and financial data that your team can trust.
If you sell on Shopify plus other channels — or plan to — OneCart connects SAP Business One to Shopify and 13+ other platforms through a single integration. Real-time inventory sync, automated order flows, and no more building separate connectors for each sales channel. Start your free trial and see your SAP data flowing in minutes.
Automate & Scale Your Online Business with OneCart
Start a Free TrialUsed by hundreds of merchants in Singapore & Southeast Asia