Shopify Store Connector

A Shopify storefront and a SAP Business One company database usually start out as two separate books of record, and the gap between them gets filled by a person. Someone exports the day's orders, reformats a spreadsheet, and keys Sales Orders into SAP line by line. Someone else corrects the store's stock figures after every goods receipt and every warehouse transfer, which means the storefront is accurate for a few minutes a day and wrong for the rest of it. New buyers get entered twice because the person creating the order cannot tell whether that customer already exists as a Business Partner, so the receivables ageing report shows the same company under three different codes. Discounts agreed in SAP price lists never reach the checkout. At month end, finance reconciles gateway payouts against A/R Invoices by hand.

None of that is a Shopify problem or a SAP problem. It is an integration problem, and it gets more expensive every time order volume goes up.

What ECOSIRE builds

ECOSIRE builds a bi-directional connector for your tenant: a service that talks to the Shopify Admin API on one side and to SAP Business One through the Service Layer (OData v4 over HTTPS) on the other, with the DI API used where a document behaviour is only exposed there. It is not a generic pipe. Every mapping is set up against your chart of accounts, your tax codes, your price lists and your warehouse structure before it goes anywhere near your production company.

Orders into Sales Orders

Each paid Shopify order is translated into a Sales Order (ORDR/RDR1) on a document series you nominate. The Shopify order name, order ID and checkout ID are written into user-defined fields on the header, so any document in SAP can be traced back to the storefront record that created it and so a replay can never create a duplicate. Line items resolve to ItemCode by SKU, with a UDT-backed mapping table for the SKUs that do not match one to one. Shipping lines, gift wrapping and manual discounts post to the freight or service items you choose rather than being buried inside the line price. Tax lines map to your SAP tax codes, so the posted document carries the code your accountant expects instead of an override applied after the fact.

Business Partners and addresses

Before a document is created, the connector resolves the buyer against OCRD using an ordered rule set: the Shopify customer ID stored on a UDF first, then tax registration number, then email. A new Business Partner is created only when none of those match, and it is created from a template card so it inherits the BP group, payment terms, default price list, credit rule and control accounts you want, rather than arriving as a blank record for someone to clean up later. Billing and shipping addresses are written to CRD1 with the correct address type, which is what makes tax determination and delivery documents behave.

Items, price lists and stock

Item masters flow from OITM to Shopify products and variants: SKU, barcode, sales unit of measure, item group, web description and whichever attributes you nominate. Availability is pushed from OITW per warehouse on a schedule you set, using an availability formula you choose - on hand, on hand less committed, or on hand plus ordered - so the storefront stops promising stock that is already allocated to a picking list. Prices come from OPLN and ITM1 price lists, including customer-specific special prices in OSPP where the store supports customer-group pricing, and currency-specific lists where you sell into more than one market.

Fulfilment, invoicing and payments

When a Delivery (ODLN) is added in SAP, the connector pushes fulfilment, tracking number and carrier back to the Shopify order, so the buyer gets the notification without anyone opening the admin. A/R Invoices (OINV) are raised from the Sales Order or from the Delivery on the timing you choose. Incoming Payments (ORCT) and gateway settlements post against the clearing account you nominate, with a Journal Entry (OJDT) for gateway fees, which turns payout reconciliation into a match instead of an investigation. Refunds and cancellations create A/R Credit Memos (ORIN) or cancel the open order, with an explicit rule for partial refunds and for whether stock is returned.

Errors, retries and monitoring

Every message is queued and logged. A user-defined object cockpit inside the SAP Business One client lists queued, succeeded and failed messages with the raw payload, the exact SAP error text, and a retry action - so a failed order is a five-second fix by the person who already understands the document, not a support ticket. Service Layer session expiry, Shopify API throttling and transient network errors are handled with backoff rather than silently dropped.

Architecture and compatibility

The connector is delivered as an add-on plus a background service, built against SAP Business One 10.0 on either Microsoft SQL Server or SAP HANA, on-premise or cloud-hosted. Extensibility stays inside the supported model: user-defined fields for traceability, user-defined tables for mapping and logs, user-defined objects for the operator screens. No core table is modified and nothing is written directly to the database behind the application layer - all document creation goes through the Service Layer or the DI API, so SAP validations, approval procedures and posting rules still apply.

Who this is for

Distributors and brands running one or more Shopify stores on top of a single SAP Business One company; businesses whose order volume has outgrown manual entry; and finance teams that need the storefront and the ledger to agree without a monthly reconciliation project. It suits companies with a settled warehouse and price list structure. If that structure is still being decided, the scoping call is where we say so.

How delivery works

1. Scoping call. We walk your Shopify setup, your company database, your document flow, your tax treatment and your warehouse and price list structure, then agree exactly which objects sync in which direction. 2. Fixed quote. You receive a written scope and a fixed price before any build work starts. If something in scope turns out to be materially different, we re-quote rather than absorb it quietly. 3. Build. Typically two to four weeks depending on scope, developed against a copy of your company database. 4. Install in test. The connector goes into your test company first and runs against a development store. You get a UAT script and sign off on real documents before production is touched. 5. Install in production. Cutover, initial master data sync, and a supervised first live run. 6. Support. A defect warranty window, plus an optional ongoing support plan.

What this is not

This is not an off-the-shelf download and there is no free trial. Nothing is pre-built and waiting for you - the app is built for your tenant after the quotation is accepted. We do not claim certification or partnership with SAP or with Shopify. If your requirement is genuinely simpler than the above, say so on the call and the quote gets smaller.