SAP ↔ Shopify · Not built yet · Waitlist open
SAP ↔ Shopify:
not built yet. Tell us to build it.
SAP S/4HANA and SAP Business One run the back office of large Shopify Plus operations. Hasil does not sync either one yet. Here is the real status, the technical shape a SAP connector would take, and what already works for your B2B buyers today.
SAP waitlist
Tell us you need SAP — we build the ERP people ask for.
We ship one ERP at a time. Odoo is live today. The next connector is decided by counted requests on pages exactly like this one — not by guesswork. Leave your email and you're a vote plus a day-one invite.
No spam · One email when SAP ships · Unsubscribe anytime
Straight answer
Where SAP sync stands today
Hasil Sync does not connect SAP to Shopify today. There is no beta, no private build, no "contact sales" workaround. The one ERP connector that exists and is in production is Odoo — XML-RPC read/write, two-way webhooks, stress-tested at 1,000 requests per hour, payloads purged after 30 days.
We say that plainly because the alternative — implying coverage we don't have — costs you a wasted evaluation and costs us the only thing a small team actually owns: being believed.
What we already know about SAP
- S/4HANA exposes OData v2 and v4 services through the SAP Gateway, plus event-driven messaging via SAP Event Mesh and the SAP Integration Suite — a documented enterprise surface, but one that varies a lot between on-premise, private cloud, and public cloud deployments.
- SAP Business One is a different product with a different API: the Service Layer (OData) and the older DI API. A Business One connector and an S/4HANA connector share almost no code.
- Access is usually mediated by your Basis team, a middleware layer, or an existing SAP Integration Suite tenant. Realistically the connector plugs into that landscape rather than calling the ERP directly — an integration project, not a two-click install.
- SAP pricing conditions and material master data are far more expressive than Shopify price lists. Deciding which condition types map to which Shopify prices is the hard part, and it is customer-specific by nature.
SAP merchants are enterprises with governance, security review, and an existing systems integrator. That is a procurement cycle measured in quarters, and it is the least likely of the four to be built before we have a paying enterprise customer asking with a signature attached.
Available now
The B2B half doesn't wait for your ERP
Hasil is two products. Hasil Sync is the ERP connector — Odoo only, for now. Hasil Pricing is a B2B wholesale portal that runs on Shopify data alone. It has no ERP dependency at all, so it works the same whether you run SAP, Odoo, spreadsheets, or nothing.
Customer-specific price lists
Per-customer and per-group pricing with quantity break tiers, resolved server-side at request time.
Private wholesale portal
Your buyers log in at your own portal URL, see their own prices, and submit orders as Shopify draft orders.
No funds, no theme edits
Official Shopify OAuth via Admin API. Orders become draft orders you invoice from Shopify. We never touch money.
Our rule
How the next ERP gets chosen
One published rule, no exceptions: no second ERP connector until 25 paying Odoo customers, and no launch of any connector before it survives a 1,000 req/hr stress test plus a simulated ERP downtime run. A half-working ERP sync is worse than none — it corrupts inventory quietly.
- Requests on this page are counted per ERP and reviewed monthly.
- The ERP with the most verified merchant requests is built first.
- Everyone on that waitlist gets the first invite and locked launch pricing.
Running Odoo instead? The connector is live — see the Odoo ↔ Shopify integration.
FAQ
Questions
Does Hasil sync SAP with Shopify today?
No. Odoo is the only ERP connector in production. Neither SAP S/4HANA nor SAP Business One is supported, in beta, or available on request. The waitlist counts your request and gets you the first invite if SAP is chosen next.
S/4HANA or Business One — are these the same connector?
No. They are separate SAP products with separate APIs. S/4HANA works through OData services on the SAP Gateway and event messaging via Event Mesh or the Integration Suite. Business One works through the Service Layer or the DI API. Tell us which one you run when you join the waitlist — the two are counted separately.
Can I use Hasil at all if I run SAP?
Yes. Hasil Pricing has no ERP dependency. It reads your Shopify catalogue over official Shopify OAuth, applies per-customer and per-group wholesale price lists with quantity break tiers, and gives your buyers a private portal that submits Shopify draft orders. SAP stays exactly as it is — no theme edits, no App Store install, and Hasil never touches funds.
What would a SAP connector actually look like?
The same queue-and-reconcile engine we run for Odoo, sitting behind whatever integration layer your landscape already uses: OData reads for master data, event-driven pushes where Event Mesh or the Integration Suite is available, exponential backoff, per-object sync health, and payload purge after 30 days. Shopify's side stays Admin API webhooks over official OAuth.
Would you build SAP for a single enterprise customer?
Ask us directly at sales@hasil.io. A funded, scoped enterprise engagement is a different conversation from the public roadmap. The public rule stands: no second ERP connector before 25 paying Odoo customers, and no launch before a 1,000 req/hr stress test plus a simulated ERP downtime run.
Put SAP at the top of the queue
One email. It counts as a vote, and it's the only way you'll hear the day SAP ↔ Shopify goes live.