Shopify to SAP Business One Order Sync: Customers, Tax and Payments
Time-Saving Integration with Excellent Support
"I like that APPSeCONNECT saves us a lot of time by automating the import of sales orders from Shopify into SAP Business One. It helps in updating business partner contact information, which is great because before we had to hand-type the orders, but now it's all imported smoothly."

A Shopify checkout brings together a buyer, purchased items, tax, shipping, and payment activity. Reliable Shopify to SAP Business One order sync carries those details into the correct customer account and sales document. Operations can then fulfill the order, while finance can trace the sale through payment posting and reconcile its eventual settlement separately.
How a Shopify Order Moves into SAP Business One

The integration resolves identity and required data before creating a destination document. Each step should leave enough reference information for the next team to trace the transaction.
The Order and Its Shopify Reference
Capture a stable Shopify order ID with its store identity. The customer-facing order number remains useful for support, but it should not be the only matching value across multiple stores. Keep the SAP object and document key in the cross-reference after creation.
SAP's internal document key, visible document number, and external reference are different fields. Store the Shopify reference in the selected reference field, user-defined field, or integration record, alongside the SAP object and key. An operator can then find the sale even when a transfer's confirmation is missing.
Use the stored Shopify and SAP references to find the existing sale when an order changes. Keep each refund linked to that sale while recording it as a separate financial event. Define which events create records, update existing records, or reverse earlier postings.
The SAP Business Partner Match
SAP Business One records the customer relationship through a Business Partner identified by CardCode. The integration needs a valid customer match before it can create the configured sales document. A Shopify customer ID and an SAP CardCode are different identifiers.
For a known buyer, use the retained cross-system relationship. For a new buyer, apply the customer-creation or shared-account rule. Guest checkout can produce an order without a Shopify customer record, so route that order explicitly instead of repeatedly trying an empty customer lookup.
SKU and Variant Matches to SAP Items
Match each purchased variant to the correct SAP item and unit. A product title can group several purchasable options. For example, 250-gram and one-kilogram bags of coffee under one product need separate variant-to-item matches, so the warehouse picks the size the customer bought.
Shopify recommends unique SKUs but does not prevent every duplicate. Reject ambiguous matches instead of choosing the first result. If a pack is sold online while SAP records individual units, the mapping must convert quantity and price consistently so a correct total does not hide an incorrect stock movement.
The Configured SAP Sales Document
SAP B1 sales order integration follows the document path agreed by finance and operations. A sales order records a customer commitment. An invoice records the amount billed to the customer, while an Incoming Payment records the receipt posted against the sale. SAP approval procedures can also create a draft awaiting approval instead of an immediately posted order.
Specify posting dates, currency, warehouse, and downstream document rules before activation. A paid Shopify status alone should not decide every SAP document. Finance and operations need the same understanding of when the order becomes ready for picking, invoicing, and payment posting.
Customer Matching Rules

Shopify SAP Business One customer mapping determines which commercial relationship the sale belongs to. Stable identifiers should take priority over convenient but changeable contact details.
Customer IDs, Email, and Composite Keys
Use an existing Shopify-customer-to-CardCode cross-reference first. Use an email fallback only where the customer-matching policy permits it. An email address is not SAP's Business Partner key. When two accounts share a purchasing inbox, retain the existing customer relationship or send the conflicting match for review.
If a composite key is needed, document its components and normalization rules. Define what happens when several records match or a required value is absent. Shopify permissions and protected-customer-data access can affect returned fields, so an unavailable email should not automatically be classified as a customer-data error.
Shared Customer Records for Consumer Orders
A shared consumer Business Partner puts selected retail orders on one SAP account. Finance should approve which sales qualify because the choice affects customer-level balances and history. An unmatched B2B buyer, for example, should remain an exception instead of entering that retail account.
Preserve the order's billing and shipping details even when the posting account is shared. Delivery and customer support still need the details of that individual sale. Route orders outside the finance-approved consumer policy to the person responsible for customer matching.
A returning consumer can place two orders with different delivery addresses. Both can use the same posting account while retaining their own address snapshots. Updating the buyer's master address later should leave the earlier order's delivery details intact.
Company and Contact Relationships for B2B Orders
B2B identity can include a company, purchasing contact, and company location. Those are separate relationships, and a company name typed into an address does not establish a native Shopify Company record. Different branches may also have different addresses or tax settings.
Map the buying business to its SAP Business Partner while preserving the purchasing contact and branch. Native Shopify B2B features vary by plan and are no longer universally limited to Plus. A plugin-based B2B design and a native Company workflow have different connector mapping requirements.
Tax Mapping

Shopify SAP tax mapping connects the order's tax components to SAP tax configuration. It covers merchandise and shipping tax, exemptions, currency, and rounding on the same accounting basis.
Shopify Tax Amounts and SAP Tax Configuration
A Shopify tax title is not automatically a valid SAP tax code. SAP exposes tax-code and VAT-group concepts whose use depends on configuration and localization. Finance should approve how the applicable Shopify tax components map to the destination document.
Keep merchandise tax separate from shipping tax where the order contains both. Record the currency basis and whether prices include tax. A rate can help explain a calculation, but the same rate alone does not establish that two taxes have the same accounting treatment.
Tax-Exempt Orders and Regional Differences
A zero tax amount does not by itself prove exemption. The mapping needs the relevant order and customer context, together with the approved regional treatment. Missing tax data should not be converted into an exemption simply to make the sales document post.
Test destination regions and exempt orders against finance's expected tax treatment. For a branch purchase, retain the company-location information needed to apply that treatment. Record which tax component and SAP tax code should appear on each test document, including shipping tax where applicable.
When tax differs, retain the order reference, affected component, mapped SAP tax code, and mapping version for the finance owner. Compare the source tax amount and taxable base with the destination calculation. Resolve a missing discount or wrong code before considering any rounding difference.
Rounding and Line-Level Versus Document-Level Tax
Compare totals using the same currency and transaction stage. Shopify tax fields can represent amounts after discounts and before returns, while an updated order may have different current totals. Comparing the original sale to a partially refunded balance creates a false mismatch.
Shopify discountedTotalSet excludes order-level discounts and excludes code discounts by default. discountedUnitPriceSet excludes order-level and code discounts. Select the field that supplies the intended price or total, then allocate remaining discounts and rounding. Check the field definition and deduct each adjustment once.
If finance selects rounding to the nearest cent with half-cent amounts rounded up, two $0.05 lines taxed at 10% each produce $0.005 in tax per line. Rounding each line gives $0.01 plus $0.01, or $0.02. Calculating tax on the combined $0.10 instead gives $0.01 ($0.10 × 10%).
Finance should approve the comparison basis, allocation of any rounding remainder, and acceptable tolerance. Reconcile the rounding difference separately from missing discounts, wrong tax codes, and currency errors. Keep those defects visible until the underlying mapping is corrected.
Payment Mapping

Mapping Shopify payments to SAP Business One requires separate records for payment activity and accounting treatment. The sales total, captured amount, processor balance, and bank deposit can legitimately differ.
Gateway and Transaction References
Retain the gateway, available transaction reference, transaction kind, status, amount, and currency. Authorization reserves or approves a payment action. Post received cash only for the successful payment activity covered by the accounting rule, and retain failed captures as exceptions for follow-up.
Gateway-specific reference fields can be absent, so define the supported reference hierarchy instead of assuming one field works everywhere. Link each SAP payment posting to the relevant sale and successful payment event. This makes a later refund or dispute easier to investigate without treating every event as a new receipt.
For split payments, link each successful event and its amount to the same sale. Compare those amounts with the receipt postings, keeping failed and pending attempts separate. If a notification repeats an existing capture, locate that capture's posting instead of creating another Incoming Payment.
Gross Order Value, Processor Fees, and Net Payouts
Shopify Payments balance transactions distinguish gross amounts, fees, and net amounts, and can relate transactions to payouts. A payout can combine several sales and adjustments. The deposit reaching a bank therefore need not equal one order's value.
For example, a customer pays $120 for an order and the processor deducts a $3 fee. The net amount is $117 ($120 − $3) before other adjustments.
Reconcile the order with its SAP sales document, successful captured activity with its receipt posting, and the payout plus adjustments with the bank deposit. Finance should define the clearing and fee accounts and currency treatment for those comparisons, including when one payout covers several orders.
Refunds, Cancellations, and Chargebacks
A refund can cover part of an order, shipping, or tax, with separate restocking details. Check the associated transaction status to establish whether money returned. Link the SAP credit document to the accounting reversal, and track the gateway refund separately through completion.
Cancellation and chargeback handling need separate rules. A chargeback is a dispute with its own status and financial effects, not an ordinary customer refund. Preserve the original references and define which team owns the accounting adjustment, gateway action, and inventory decision for each event.
Test the Order Sync Before Production

Test representative orders with written expected results for the SAP document, payment activity, and exceptions. Include both a complete checkout and interruptions between related steps.
Normal, Discounted, Partially Refunded, and Tax-Exempt Orders
Start with a straightforward order, then vary guest checkout, known-customer matching, variant selection, discounts, shipping tax, and exemption. Include a partial refund so the test compares both the original sale and its revised quantities and totals.
- Expected Documents: Record the customer, items, warehouse, dates, and document types that should appear in SAP.
- Expected Exceptions: Define the result for missing identifiers, invalid tax mappings, and conflicting customer matches.
- Expected Reversals: Record which credit, refund, and stock actions belong to each cancellation or return scenario.
For a partial refund, identify the affected item and quantity, tax adjustment, payment state, and restocking instruction. Refunding one bag from a two-bag order should remain linked to that line. Review both the credit amount and quantity so a correct total cannot hide the wrong item being returned to stock.
Duplicate Prevention and Retry Behavior
Test repeated delivery and a lost acknowledgement after SAP creates the document. The latter leaves a sale in SAP while the integration awaits confirmation. The operator should find the existing document before retrying and resume only the work that remains unfinished.
Use the store/order cross-reference to establish business-record uniqueness, alongside event-delivery checks. Also test delayed or out-of-order notifications. A successful retry should finish the intended transaction without restoring an older state over a later change.
Include an interruption between related steps. If the sales document exists but payment posting fails, resume the unfinished payment work against that document. Record how the operator identifies the completed sales step and which reference connects it to the pending payment posting.
Totals and Payment Reconciliation
Compare merchandise, discounts, shipping, tax, and the final order total on the same basis. Then reconcile successful payment activity with the SAP payment posting. Finance reconciles processor payouts separately, retaining any unexplained difference against its sale, payment, or settlement reference.
Keep the test order IDs, SAP keys, expected values, observed differences, and resolution. Finance can then approve an explained rounding difference without masking an unmapped discount or missing refund. Failed cases should return to the responsible mapping or accounting owner before launch.
For an edited order, record when Shopify changed and when the SAP update completed. Compare both records after that update. If the quantities agree but tax differs, inspect the tax and discount basis. If SAP still shows the earlier quantity, investigate the pending update before changing the arithmetic.
How APPSeCONNECT Connects the Shopify Order Flow to SAP Business One
APPSeCONNECT connects Shopify orders to SAP Business One Sales Orders against a Business Partner. Our SAP Business One and Shopify integration transfers items, addresses, tax, shipping, and discounts so operations can work from the connected order rather than re-enter checkout details.
Field Mapping for Accounting Requirements
APPSeCONNECT ProcessFlow maps Shopify order values to destination attributes using functions, variables, and custom attributes. Those mappings carry the shipping and discount values used in the SAP sales document.
Validate representative mapped orders and expected SAP documents with finance. Check the tax-code mapping, posting dates, currency, discounts, shipping, and payment-account rules against accounting requirements. Record the approved map version and expected results before activation.
Our order flow supports shipping and discount charges at line or document level. Finance can compare those mapped amounts with the Shopify order when reconciling the SAP sale. Finance retains ownership of tax treatment, posting policy, and reconciliation expectations.
Sales Documents and Payment Handling
APPSeCONNECT supports a payment-posting flow using an A/R Reserve Invoice and Incoming Payment with the transaction ID. The transaction ID links the payment posting to the Shopify sale. Processor-fee import, payout settlement, and card-refund execution require separate workflows.
Confirm with the implementation team which SAP documents and payment postings the configured flow will create, and how unfinished steps will be recovered. Record that scope alongside the approved field map.
APPSeCONNECT Sync Info provides record status, timestamps, attempts, and successful destination references. Our manual and configurable automatic retries support recovery after a corrected exception. Destination checks remain part of safe replay when the original write result is uncertain.
An Auditable Order from Checkout to Settlement
APPSeCONNECT connects Shopify orders to SAP Business One Sales Orders and records the transaction ID in the supported payment-posting flow. Operations and finance can trace the sale to its SAP document and payment reference. Finance separately reconciles processor fees, payout adjustments, and bank deposits, keeping settlement differences visible alongside the order's customer and tax treatment.
Talk to an APPSeCONNECT expert about the Shopify order flow.
Frequently Asked Questions
Time-Saving Integration with Excellent Support
"I like that APPSeCONNECT saves us a lot of time by automating the import of sales orders from Shopify into SAP Business One. It helps in updating business partner contact information, which is great because before we had to hand-type the orders, but now it's all imported smoothly."
Request for a personalized demo


