Connecting Shopify to SAP S/4 HANA sounds simple – until you’re deep in file enrichment logic, payment flow edge cases, and three-way project coordination. Here’s what actually happened.
What we built: a live data bridge between Shopify and SAP S/4 HANA
Rausch GmbH needed a fully automated connection between their Shopify Plus store and SAP S/4 HANA. No manual exports, no spreadsheet handoffs.
We built a custom SAP connector handling four core jobs: orders, payment terms, tracking numbers, and inventory sync. Working alongside Eddyson – an external SAP integration partner – we owned the Shopify side while Eddyson bridged the gap to SAP.
The flow works like this:
- Shopify sends order data via webhook to our connector
- We enrich the files with missing information and deposit them on an FTP server for Eddyson to pick up
- In the other direction, SAP sends tracking and inventory updates to Eddyson, which forwards them to us – we enrich and push them into Shopify
Clean loop, when it works.
File enrichment and payment flows: where the real complexity lives
Shopify’s order webhook payload doesn’t include everything SAP S/4 HANA needs – and that gap is where most of the work happened.
Barcodes, for example, aren’t part of the order data. The connector loops through each line item, fires an additional API call using the variant ID, and fetches the barcode separately. Same logic for gift cards: we detect the payment gateway name, hit the transactions endpoint, and pull the gift card data before packaging the file.
None of this is complex in isolation. But when you’re mapping fields across two systems with fundamentally different data models, it adds up fast.
Buy on account required its own solution entirely. SAP handles these orders with a delivery block – the order exists but doesn’t ship until payment is confirmed. That meant orders/create and orders/paid couldn’t follow the same flow. We built two distinct flows, each triggering different downstream logic. Getting the SAP behavior properly documented took longer than expected.
Three-party project coordination: the hidden cost of misalignment
Any project involving a client, an agency, and a third-party integration partner has natural friction points. Mapping decisions took time to finalize, and some delays came from waiting on alignment between parties rather than from the technical work itself.
We navigated it – but it taught us something important about how these projects should be set up from the start.
What we’d do differently on a Shopify ERP integration
We went into this project without a detailed requirements list or milestone-based roadmap. That gap cost us time.
Upfront documentation is non-negotiable. When you’re coordinating between Shopify, a custom connector, and a third-party SAP middleware partner, ambiguity is expensive. A requirement that seems obvious to one party is news to another.
A few things we now treat as mandatory on any Shopify ERP integration:
- A detailed requirements list before kickoff – especially for payment flows, tax logic, and edge cases like gift cards or custom payment methods
- A shared Slack channel with all parties onboarded from day one – context scattered across emails and calls slows everything down
- Data mapping completed early and in detail – the gap between what Shopify sends and what SAP expects is where projects lose weeks
Key takeaways for your Shopify SAP integration
If you’re planning a Shopify SAP or broader Shopify ERP integration with a third-party middleware partner, here’s the short version of what this project taught us:
- Define requirements before kickoff – not a rough scope, an actual list. Payment flows, tax logic, edge cases.
- Map your data early – the Shopify-to-SAP field gap is real and takes time to resolve properly.
- Build on a stack you’ll maintain – technical debt from legacy codebases surfaces as migration costs, not if but when.
- One shared communication channel from day one – when three parties need to align quickly, async fragmentation kills momentum.
The connector works. The lessons were worth it.
We also delivered the full Shopify services scope for Rausch GmbH – building their Shopify Plus store, migrating from Shopware 5, and implementing a custom product configurator for their Pick&Mix solutions. The ERP connector sits inside a larger, working ecosystem.
