Commerce & Finance integration
Move Shopify orders into SAP without losing control of stock and fulfillment.
Nexus can validate Shopify order lines, map products and locations, submit the required SAP order process and return the permitted fulfillment updates. Refund and cancellation paths are designed alongside the sale, so exceptions do not become unexplained differences between the storefront and ERP.
The problem
Why Shopify + SAP needs a governed process
Shopify describes the customer purchase; SAP may control available stock, warehouse execution and accounting. Product variants, bundles, discounts and shipping charges can mean different things in each system. A cancelled storefront order may already be in warehouse processing by the time the update reaches ERP.
Responsibility
How the systems divide responsibility
Storefront transaction record
Shopify
Customer checkout, storefront orders, payment context and online customer communication.
ERP and fulfillment record
SAP
ERP products, warehouse and stock rules, sales documents, invoicing and operational fulfillment.
Capabilities
What Nexus orchestrates
Pre-built action groups used in this pattern. Anything else runs through an API, protocol or database step, or Rules + Code, in the same workflow.
Shopify
39 ACTIONS
- Orders
- Customers
- Products
- Inventory
- Shipping
SAP
97 ACTIONS
- Sales Orders14
- Invoice10
- Finance20
- Products10
- Core SAP7
Architecture
One governed run across both systems
How work starts
Webhook, schedule or API poll
An order reaches the agreed payment or release state, a cancellation is requested, or an ERP stock or fulfillment change is ready to publish.
When a pre-built action does not cover it
Workflow patterns
What teams run across Shopify + SAP
01
Paid-order release
Validate the order state, customer and line mappings before creating the SAP sales document.
02
Stock publication
Translate the agreed SAP availability measure into storefront inventory for the mapped location and variant.
03
Shipment status return
Link SAP fulfillment results to the Shopify order using the supported fulfillment operation and permissions.
04
Cancellation and refund review
Check the ERP processing stage before requesting a cancellation or preparing the finance adjustment associated with a refund.
Direction and ownership
Which way each change moves
Accepted Shopify orders move into the agreed SAP company and fulfillment process. SAP returns selected stock availability and fulfillment outcomes for publication in Shopify. The authoritative stock source and permitted inventory adjustments are defined by location; neither system overwrites the other's entire inventory blindly.
Shopify SAP
Order lines, mapped variants, discounts, shipping charges and approved cancellation or refund context.
SAP Shopify
Agreed stock availability, ERP references and shipment or fulfillment status.
Control
Approvals and exception handling
Human approval
Unmapped bundles, unusual price differences and cancellations after warehouse release wait for the designated commerce, fulfillment or finance owner. The approved action proceeds for the reviewed order state; rejection records the alternative handling required.
Exceptions
- Unknown variants or warehouse mappings hold the affected order rather than substituting an item.
- Stock or fulfillment changes that conflict with the agreed authority are routed for reconciliation.
- Repeated order updates use source and ERP references; uncertain creation outcomes are checked before retry.
Security, audit and deployment
Every run leaves a reviewable record
- Shopify order version, payment context and line values used.
- Variant, location and pricing transformations applied.
- Any approval for a fulfillment or refund exception.
- SAP document responses and the updates returned to Shopify.
Credentials for Shopify and SAP are held in the vault and used only by the steps that need them. Role-based permissions decide who can edit, approve and run the workflow. Nexus runs on premises, in private cloud or air-gapped, so the execution record stays inside your deployment boundary. Governance and audit
Talk to a solutions engineer
See this run against your Shopify and SAP
Bring the process you run today. We map which system owns what, where approval belongs and the steps each side needs, against your own Shopify and SAP, not a generic environment.
- The Shopify + SAP workflow built and run end to end.
- Where a person is asked to approve, and what they see.
- The execution record an auditor would read afterwards.
- What it takes to run this inside your own deployment boundary.
Participating connectors
The connectors behind this pattern
Related
Continue from here
- Payment and subscription events into CRM and ERP
Commerce and payment events landing in CRM and ERP.
- Enterprise automation
Governed processes across the systems you already operate.
- Enterprise integration
Connectors, interfaces and code in one platform.
- Integration explorer
Add more systems to this combination.
FAQ
Shopify + SAP questions
- Does SAP stock mean the same thing as Shopify available inventory?
- Not always. The design defines reservations, safety stock and location rules before publishing an availability value.
- Can a Shopify refund reverse an SAP invoice automatically?
- Only through the approved finance process. A payment refund and an ERP accounting adjustment are distinct actions.
- Can the process support our Shopify plan and SAP edition?
- Required APIs, permissions and SAP interfaces are checked against your installations before the workflow scope is agreed.
Integration review
Discuss this integration
Bring your Shopify and SAP process. We will map ownership, approval and the steps each system needs.