SAP Business One Shopify Data Mapping Guide: Items, Customers, Orders, Stock

AM
Anita M.
Distribution Center Manager
★★★★★★★★★★
4.5/5 · 9/21/2026

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."

Read more APPSeCONNECT Reviews
SAP Business One Shopify Data Mapping Guide: Items, Customers, Orders, Stock
Author photo: Subhajit GoswamiSubhajit Goswami11 min read

A field map connects SAP Business One items with Shopify variants, buyers with Business Partners, and orders with sales documents. It also determines which warehouse quantities the storefront can sell. SAP Business One Shopify data mapping records the identifiers, field ownership, transformations, and exception rules needed to preserve those relationships as records change.

Key Takeaways

Key Takeaway

Complete Field Rules: A mapping records source, destination, direction, owner, matching key, transformation, and exception behavior so the same rule applies to each eligible record.
Distinct Identities: Shopify product, variant, inventory, customer, and order IDs serve different roles. SAP item codes and Business Partner keys need explicit cross-system relationships.
Financial and Stock Meaning: Discounts, tax, payment events, and sellable quantity require a defined basis. SAP projected availability is not automatically immediate-sale Shopify stock.
Configured Workflows: APPSeCONNECT maps source attributes and connects selected products, prices, orders, stock, and shipment updates between Shopify and SAP Business One.

What Data Mapping Covers

SAP B1 Shopify field mapping turns a business decision into a repeatable transfer rule. Each mapped value should have a clear meaning, owner, and destination behavior.

Diagram of what SAP Business One Shopify data mapping covers: items, customers, orders, and stock
Business Data
Mapping
Important Rule
Item
SAP item to Shopify variant
Identity and unit match
Customer
Shopify buyer to SAP Business Partner
Retained identifier and exception policy
Order
Shopify order to SAP document
Stable reference and accounting basis
Stock
SAP warehouse to Shopify location
Eligible quantity and reservation policy

Source and Destination Fields

Record exact source and destination paths, data types, and business meanings. A Shopify variant SKU can support business matching, while SAP's item code identifies the SAP item. For each relationship, state which value locates an existing record and which values update its content.

Keep object identity separate from descriptive content. A product title can change without creating a new purchasable variant. A customer's email is a contact detail, while SAP CardCode identifies the Business Partner. The map should explain both the identifier relationship and the descriptive fields that may update.

Direction, Transformation, and Matching Keys

Define who owns the value and which way changes travel. An organization can choose SAP-owned base prices while keeping Shopify-owned merchandising descriptions. Bidirectional integration does not mean every field should accept changes from both sides.

A transformation changes a value’s representation, such as converting packs to individual units. A matching key locates the existing destination record. Keep the relationship between those records after creation, so a later description or email change updates the right record instead of creating another one.

Record which system’s change wins when both edit the same field. A late SAP price update, for example, can overwrite a commerce override unless the map defines how that exception ends. Assign unresolved conflicts to an owner and retain the values needed to decide them.

Required Values and Fallback Behavior

Mark required values and define what happens when they are missing or invalid. A rejected record with an assigned owner can be safer than an order posted to an arbitrary customer, item, tax code, or warehouse.

Use defaults only when the business approves their meaning and scope. A shared consumer account, for example, is an accounting policy for eligible orders, not a substitute for every failed customer match. Record the default's condition and the test that shows when it must not apply.

The seven parts of a field mapping rule: source, destination, direction, owner, matching key, transformation, and exception behavior

Quick Answer

SAP Business One Shopify data mapping defines how each record moves between the two systems. SAP items map to Shopify variants, Shopify buyers to Business Partners, Shopify orders to SAP sales documents, and SAP warehouse stock to Shopify locations. Each rule sets the matching key, field owner, sync direction, transformation, and exception handling.

Map SAP Business One Items to Shopify Products

Shopify SAP item mapping needs to distinguish the catalog's product structure from the item purchased on an order. The relevant match is often at variant level, with separate rules for shared product content.

Item Codes, SKUs, Variants, and Product Content

Record the SAP item code, Shopify product ID, variant ID, SKU, and relevant inventory relationship. Variants represent purchasable option combinations, such as size and color. Record stock per inventory item and location, retaining the identifiers needed to update the intended location’s quantity.

Separate SAP items can appear as variants under one Shopify product. For example, small and large blue shirts can share a product title and description while each variant maps to its own SAP item. Keep the item matches at variant level and the shared copy at product level.

Shopify recommends unique SKUs but does not prevent every duplicate. Use controlled SKUs or retained IDs to locate the intended variant, and reject conflicting matches. Record product status and channel publication separately so catalog updates can distinguish an active product from one published to the intended storefront.

Units, Prices, and Product Options

Map sales units, pack size, currency, and price source together. For a pack of six recorded as individual units in SAP, an order for two packs represents 12 units. The quantity conversion and price basis need to preserve both the warehouse movement and the order’s financial total.

Give each product option a stable variant-to-item relationship. When a new size is added, create or match its variant according to the catalog rule. When only its price changes, update that variant’s price and preserve the commerce-owned description and unrelated product settings.

Keep the unit, pack definition, price source, and field owner beside each variant match in the worksheet. When a pack definition changes, review both the published price and imported order quantity before releasing the revised mapping.

How Shopify product variants map to SAP Business One items, with shared product content at the product level and item matches at the variant level

Map Customers and Business Partners

Mapping Shopify customers to SAP Business Partners connects commerce identity with the account used for SAP transactions. It must distinguish the buyer, contact details, business relationship, and order addresses.

Customer Identifiers, Email, Companies, and Contacts

Use an existing Shopify-customer-to-CardCode cross-reference first. Email or a composite key can provide a fallback authorized by the customer-data owner. When two Business Partners share an inbox, retain their distinct account relationships and send the conflicting match for review.

For native B2B, a Shopify Company, its contacts, and company locations are separate relationships. A company name typed into an address is a descriptive value. Preserve the purchasing company relationship, contact, and branch so the order reaches the intended customer account and destination.

Native Shopify B2B features vary across several plans and are no longer universally Plus-only. Select the map for the B2B model in use. A plugin-based workflow needs its plugin fields, while a native Company workflow needs connector support for the company, contact, and location relationships it uses.

Billing and Shipping Addresses

Map billing and shipping addresses separately and preserve their order context. The address used for a sale can differ from a customer's current master-data address. A later account edit should not silently change the historical meaning of an earlier order.

Record required address fields, destination address identifiers, and the owner for incomplete data. For a B2B branch purchase, carry the branch's shipping address and relevant tax settings. Keep the head office's billing details separate when they differ from the delivery destination.

Guest Checkout and Duplicate Matching Rules

A Shopify order can lack a customer record, including at guest checkout. Finance should decide which guest sales use a shared consumer Business Partner and which follow customer creation. Retain each order’s buyer and address details for delivery and support, including when several sales share a posting account.

When email is missing, check permissions and protected-customer-data access before using the fallback allowed by the customer-matching policy. Test absent matches, multiple matches, a changed email, and a returning buyer so repeat purchases reach the intended Business Partner.

How a Shopify customer maps to an SAP Business One Business Partner, including email and composite-key fallback matching

Map Shopify Orders to SAP Business One

SAP Shopify order mapping preserves the sale's identity, purchased items, and financial meaning. Specify which events create a document and which update, cancel, or reverse related work.

How a Shopify order maps to an SAP Business One sales document, including order reference, status, and financial fields

Order References, Dates, Currency, and Status

Keep the Shopify store and stable order ID with the SAP object and document key. The customer-facing order number, SAP document number, and internal key identify different things. Store the cross-reference in the selected field or integration record, then use it to locate later updates and retries.

Record the source event time, SAP posting-date rule, currency, and status that qualifies the order for processing. Define the sequence of sales orders, invoices, approval drafts, and Incoming Payments with finance and operations. A paid Shopify status contributes to that decision but does not specify all of those documents.

After creation, an update should locate the existing transaction. Repeated or delayed notifications must not create another sale or overwrite a later state with an earlier one. Retained references support both normal updates and recovery after an uncertain destination response.

Line Items, Discounts, Shipping, and Tax

Map item, quantity, unit, price, discounts, warehouse, and applicable tax treatment at the appropriate level. Keep shipping charges, shipping discounts, and shipping tax separate. The mapping should state whether it uses original sale values or current values after edits and returns.

Select discount fields by their exact meaning. Shopify discountedTotalSet excludes order-level discounts and excludes code discounts by default. discountedUnitPriceSet excludes order-level and code discounts. Document which remaining discounts need allocation so the transformation neither omits them nor subtracts them twice.

Use finance-approved SAP tax configuration and rounding. Map tax components to the applicable SAP codes, and establish any exemption from the order and customer information under the relevant regional rules, not from a zero tax amount alone. Compare line and document totals in the same currency and transaction stage, then resolve missing discounts or incorrect codes before allocating a rounding remainder.

Payment References, Refunds, and Cancellations

Record payment kind, status, amount, currency, gateway, and available transaction references. Link successful captured activity to the defined SAP receipt posting. Keep authorizations separate from receipts and preserve the references finance needs to reconcile processor activity and subsequent bank payouts.

A partial refund can affect merchandise, shipping, tax, and restocking. Record the returned line and quantity and check the money-return transaction’s status. Link any SAP credit to its accounting reversal, while tracking the gateway refund separately through completion.

Define cancellation and dispute handling separately. A cancelled order, a returned item, and a chargeback do not request identical finance or inventory actions. Preserve the original order references and assign the responsible business owner for each exception.

Map Stock and Warehouse Availability

SAP B1 Shopify inventory mapping connects each item and location to a selling quantity. The calculation needs to identify stock ready for sale, reservations already deducted, and any buffer held back from the storefront.

Warehouse Locations and Available Quantity

Map the SAP warehouse code to the intended Shopify location and inventory relationship. A single variant can carry the same SKU across locations while quantities differ by location. Comparing one location with an all-warehouse SAP total can create a misleading mismatch.

Specify the stock state being read and the destination quantity being maintained. Shopify excludes committed, unavailable, and incoming inventory. Inventory-item and location identities are distinct from the product title or SKU.

Commitments, Safety Stock, and the Availability Formula

SAP projected availability adds ordered stock to in-stock quantity after subtracting commitments. Ordered goods may still be in transit. For immediate sale, calculate the quantity from stock the selected warehouse can supply now and the reservations that apply to it.

In a stock worksheet row, InStock is 40, Committed is 12, and Ordered is 20 for the supplying SAP warehouse. Projected availability is 48 (40 − 12 + 20). For immediate sale, map in-stock minus committed minus a three-unit buffer to Shopify available at the matched inventory item and location. The result is 25 (40 − 12 − 3), with incoming stock excluded.

How SAP Business One warehouse stock maps to Shopify available quantity, with committed stock and a safety buffer excluded

Document the units and reservation treatment. If SAP and Shopify both represent the same customer order, avoid deducting that commitment twice. Apply the same discipline to safety buffers so one buffer is not already embedded in the source and subtracted again during transformation.

Store-Specific and Multi-Warehouse Rules

Assign supplying warehouses to each storefront. For example, publish eligible stock from the retail warehouse and exclude a second warehouse reserved for wholesale orders. Keep that exclusion in the warehouse map so a later stock refresh does not add the wholesale pool to the storefront quantity.

For several stores, retain the store, warehouse, Shopify location, and item relationships together. Receive stock into one warehouse during testing and inspect each storefront’s result. Each mapped storefront and Shopify location should receive the quantity defined by its warehouse rule. Storefronts and locations excluded from that warehouse map should keep their own stock values.

Build and Test a Mapping Worksheet

Keep the mapping worksheet alongside implementation and troubleshooting work. It should let a business owner find a field's rule and let an operator trace a rejected value back to that rule and its version.

Owners, Direction, Required Values, and Exceptions

Include the business field, exact source and destination paths, data types, owner, direction, match key, required status, transformation, default or rejection, exception owner, and version. Add unit, currency, date, and rounding rules wherever they affect meaning.

  • Item Rule: Record the variant-to-item relationship, unit conversion, price owner, and response to a missing or duplicate match.
  • Order Rule: Record the stable reference, document path, eligible status, and financial basis.
  • Stock Rule: Record eligible warehouses, target locations, quantity formula, and reservation treatment.
  • Exception Rule: Name the responsible team and the evidence needed before correction or retry.

Keep a test and expected result beside each rule. A default that works for consumer orders should also have a test proving it does not apply to an ineligible B2B order.

Update the worksheet when a field, business rule, or connector configuration changes. Record the reason, owner, version, and affected tests. Retain earlier versions so an operator investigating an older order can recover the exact matches, transformations, and accounting treatment used when it was processed.

New, Updated, Missing, and Conflicting Records

Test creation and update separately. Include a returning customer, changed SKU, new variant, missing required field, conflicting match, and simultaneous field edits. The expected result should identify the destination record and value, or the owned exception.

Test repeated delivery and a successful write followed by lost acknowledgement. Check the destination before replaying an ambiguous result. Also include partial refunds, fulfillment quantities, stock commitments, and reconciliation differences so downstream behavior is covered alongside the initial transfer.

Inspect destination values as well as transfer status. For a two-pack order, check the matched item, pack conversion, financial components, and warehouse quantity. Compare them with the worksheet’s expected result, and send an incorrect default or conversion back to its mapping owner before release.

Mapping Worksheet Checklist, in Plain Language

How APPSeCONNECT Supports Shopify and SAP Business One Field Mapping

APPSeCONNECT ProcessFlow maps source attributes using functions, variables, and custom attributes. Our SAP Business One and Shopify integration places Shopify item, address, tax, shipping, and discount values in the SAP sales document so finance can compare those amounts with the online order.

Field Mapping Around Business Requirements

Review representatives transformed records and destination results with finance and operations owners for the configured APPSeCONNECT flow. Check items, customer matches, order documents, tax treatment, and sellable quantities against the worksheet. Resolve differences and record owner approval of the mapping version and observed results before activating or changing the flow.

Our order flow creates SAP Sales Orders against a Business Partner and transfers the order's addresses and charges. The customer match assigns the sale to its SAP account, while the order retains the billing and shipping details operations needs to fulfill it.

Connector Fields and Transformations

APPSeCONNECT publishes selected SAP items and price-list base prices to Shopify products. Our warehouse/location mappings support in-stock, in-stock minus committed, or in-stock minus committed plus ordered quantities. The plus-ordered option can include goods not yet received.

With the implementation team, confirm the actual source and destination field paths, data types, and available transformation for each selected mapping. Compare a representative transformed value with the expected destination result and record the selected paths and rule. If a rejected record needs replay, check the destination state before retrying it.

Keep the Field Map Current

APPSeCONNECT connects Shopify order details with SAP sales documents and publishes selected item, price, and warehouse quantities to Shopify. The worksheet records the matches and calculations behind those transfers. Updating its rules and version as requirements change keeps finance, operations, and the implementation team working from the same mapping.

Talk to an APPSeCONNECT expert about SAP Business One Shopify field mapping.

Frequently Asked Questions

APPSeCONNECT supports configured flows for selected products and base prices, orders and their details, warehouse-based stock, and shipment tracking. Payment handling includes an A/R Reserve Invoice and Incoming Payment flow with transaction ID. Additional B2B workflows have separate plugin-based scope.

SAP Business OneShopifyData MappingERP IntegrationAPPSeCONNECT
AM
Anita M.
Distribution Center Manager
★★★★★★★★★★
4.5/5 · 9/21/2026

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."

Read more APPSeCONNECT Reviews

Request for a personalized demo

Related Resources