Shopify SAP Business One Integration

If your business runs SAP Business One as its ERP and Shopify as your storefront, the two systems need to talk to each other constantly. Customers, pricing, stock, orders, payments. When they do not, someone on your team quietly becomes the integration, rekeying orders by hand, checking stock across two screens, chasing payment status that should already be visible.

We build Shopify to SAP Business One integrations using BPA Platform as the middleware. This page covers what we actually sync, what takes the real work, and what it costs, based on a project we delivered for a Shopify Plus retailer running SAP Business One on-premise.

What we actually sync

Business partners. When a business partner in SAP B1 is marked visible for B2B, it syncs to Shopify as a company. The business partner group assigned in SAP drives which price list the customer lands on in Shopify, so the two stay linked rather than needing separate maintenance.

Contacts. Only the main contact on the account syncs, not every contact. That is a deliberate choice, not a limitation we ran out of time to fix. It keeps Shopify login access tied to the person who should actually have it.

Addresses. One billing address and one shipping address per business partner by default. If your business needs to support dropshipping to multiple addresses, that is handled by placing the relevant customers in an approved group, not by syncing every address on the account. It is worth deciding early which customers actually need this, because it changes the shape of the project.

Pricing. Price lists in SAP are tied to customer groups. The integration creates the matching catalogue in Shopify and writes the catalogue ID back into SAP, so a new business partner is assigned the correct pricing automatically the moment they are created.

Payment terms and credit limit. These sync to Shopify as metafields, so the storefront can show a customer their terms and their available credit without anyone checking SAP by hand.

Products and stock. Products flagged for web visibility sync to Shopify as drafts, with description, SKU and the fields your business actually uses. Stock is pulled from one nominated warehouse, on a schedule.

Orders and payments. Orders placed in Shopify create sales orders in SAP B1. Discounts and freight are included. When an order is marked fully paid in Shopify, an incoming payment is created in SAP B1 automatically. Partial payments are handled separately, not silently approximated.

Change monitoring. Once live, the integration checks for business partner changes on a schedule (typically every 30 minutes) and keeps SAP and Shopify aligned without anyone needing to trigger it manually.

What takes the real work

Deciding what “one address” means for your business. If customers dropship or need multiple delivery addresses, that is a real design decision, not a checkbox. It gets scoped as its own piece of work, not bolted on afterwards.

Mapping SAP price lists to Shopify catalogues. SAP B1 and Shopify structure pricing completely differently. Getting the customer group to catalogue mapping right, and making sure the catalogue ID writes back to SAP correctly, is where the design time goes. The development itself is usually the easy part.

Payment sync only fires on fully paid orders. If your business takes deposits or partial payments, we tell you that up front rather than quietly building something that half-works. It gets scoped as a separate process.

Rounding between two systems. Shopify and SAP B1 do not always calculate to the same number of decimal places, so a line total or tax amount can come out a penny different in each system. It is a small difference that causes real problems, from order totals that do not match to payments that will not reconcile. We raise it at scoping and agree how differences are handled before development starts, because an integration that is confidently wrong on pricing is worse than one that is honestly incomplete.

VAT and tax logic stays where it already lives. Trying to make the integration the source of truth for tax calculation is one of the more common ways projects like this overrun. We keep it in whichever system already owns it.

If your setup is different

The project above was a B2B retailer, but most Shopify and SAP Business One integrations look different in at least one way. These are variations we have delivered, and each one goes into your estimate at the start rather than being discovered halfway through.

Selling direct to consumers. The customer side is lighter, with no company accounts, catalogues or credit limits to sync. Orders, stock and payments still flow the same way.

Multiple warehouses. Stock can come from more than one SAP B1 warehouse, either combined into one available figure or kept separate, depending on how you fulfil orders. Which one fits is part of the design.

Deposits and partial payments. Set up as their own payment process, designed around how you actually take money, rather than waiting for an order to be fully paid.

Selling in more than one currency. Each currency on your storefront maps to a business partner account in SAP B1 held in that same currency, so orders post in the currency they were placed in and no conversion is needed.

Returns and credit notes. Returns handled in Shopify create the matching documents in SAP B1, so refunds and stock are reflected in both systems.

Each of these adds time to the project, so tell us early which apply and we will include them in the day-by-day breakdown.

What it typically costs and how long it takes

As an indicative estimate, a full end-to-end Shopify to SAP Business One integration, covering business partners, pricing, products, stock, orders and payments, typically runs 10 to 15 days of delivery. At our current standard rate of £150 per hour plus VAT (a day is quoted as 7.5 hours), that is roughly £11,000 to £17,000 plus VAT for the consultancy work described above.

That covers the delivery work: installing and configuring BPA Platform, building the staging database, building and testing each sync individually, user acceptance testing, go-live support, and technical documentation handed over at the end.

The BPA Platform software licence is separate from the consultancy cost. We show you what it costs in your quote, so you can budget for the full picture before committing rather than finding out halfway through.

This is a guide, not a quote. The real figure depends on how many of these areas apply to your business and how much of your existing SAP B1 setup needs mapping before development starts. Final pricing is confirmed in writing, at our rates at the time, with a day-by-day breakdown agreed before any work begins.

Frequently asked questions

Does this work with on-premise SAP B1 and hosted SAP Business One?

Yes, both. SAP B1 itself works the same way in either case. What differs is access. On-premise, BPA Platform usually runs on a server on your own network alongside SAP B1. With a hosted deployment, including SAP Business One Cloud or a hosting partner, the approach depends on what the host allows: whether BPA Platform can run on their infrastructure or needs its own server, and which interfaces and connections they make available. We confirm this with you and your hosting provider during scoping, before committing to a timeline.

Is the BPA Platform licence included in the price?

No. The day rate covers our consultancy and delivery work. The BPA Platform licence is priced separately, and we show you that cost in your quote so there are no surprises later.

Can it handle multiple delivery addresses for the same customer?

Yes, but through an approved customer group rather than syncing every address by default. Worth raising early, since it changes the scope.

What happens if a sync fails partway through?

Failed tasks are logged and trigger an email notification. Once the underlying issue is fixed, the task reprocesses automatically. Nothing fails silently and sits unnoticed.

Do you handle VAT and rounding as part of this?

VAT, no, deliberately. We leave it with whichever system already owns that calculation, because making the integration responsible for tax logic is one of the more common ways these projects go wrong. Rounding differences between the two systems, yes: we raise them at scoping and agree how they are handled before development starts.

We already have an integration that does not quite work. Can you take it over?

Yes, but we review the current implementation before we quote: what is running, how it is configured, and where and why it is failing. Taking over an existing build is a different job from starting fresh, and an honest quote depends on seeing it first. In our experience, an integration that used to work and has stopped usually comes down to a process that changed, data that is wrong, or an environment change such as a server, network or firewall update.

If you are running Shopify and SAP Business One and want to know what a proper integration would look like for your setup, get in touch and we will talk it through. For the other systems we integrate, see our integration solutions overview.