NetSuite ↔ Shopify · Not built yet · Waitlist open
Oracle NetSuite ↔ Shopify:
not built yet. Tell us to build it.
NetSuite is the most common ERP behind Shopify Plus stores, and it is the connector merchants ask us about most after Odoo. It is not built. This page exists to count how many of you actually need it — and to tell you exactly what already works while you wait.
NetSuite waitlist
Tell us you need NetSuite — 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 NetSuite ships · Unsubscribe anytime
Straight answer
Where NetSuite sync stands today
Hasil Sync does not connect Oracle NetSuite 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 NetSuite
- NetSuite exposes SuiteTalk REST (record + SuiteQL) and the older SOAP web services, both authenticated with token-based auth (TBA) or OAuth 2.0 — a supported, documented surface, no scraping required.
- There is no native outbound webhook UI the way Odoo 17 ships one. Real-time NetSuite → Shopify pushes normally mean a SuiteScript user-event script, which is customer-side ERP code — something we would rather design around than force on you.
- NetSuite concurrency is governed and account-tier dependent. Any honest connector has to queue, backoff, and reconcile rather than fire per-event calls, which is the same queue-and-reconcile architecture Hasil Sync already runs for Odoo.
- NetSuite item, pricing, and multi-location inventory models are richer than Shopify's. Mapping price levels and locations correctly is the actual work — not the HTTP calls.
NetSuite merchants are typically Shopify Plus or enterprise operators with multi-entity accounting, multi-warehouse inventory, and an existing implementation partner. That is a heavier integration and a longer buying cycle than Odoo — which is exactly why we will not start it on a hunch.
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 NetSuite, 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 NetSuite with Shopify today?
No. Odoo is the only ERP connector in production today. NetSuite ↔ Shopify sync is not built, not in beta, and not available on request. Joining the waitlist counts your vote and gets you the day-one invite if NetSuite is chosen as the next connector.
When will NetSuite ↔ Shopify sync be available?
There is no promised date, and we will not invent one. Our published rule is no second ERP connector until 25 paying Odoo customers, and no connector launches before it passes a 1,000 req/hr stress test plus a simulated ERP downtime run. Waitlist demand decides which ERP is second.
Can I use Hasil at all if I run NetSuite?
Yes — Hasil Pricing works with no ERP at all. It reads Shopify products and variants, applies per-customer and per-group wholesale price lists with quantity break tiers, and lets your buyers order through a private portal that creates Shopify draft orders. NetSuite keeps doing accounting exactly as it does now; nothing about your ERP has to change.
How would a NetSuite connector work technically?
Through SuiteTalk REST with token-based auth or OAuth 2.0, plus SuiteQL for efficient reads, wrapped in the same queue-and-reconcile engine we run for Odoo: an event queue, exponential backoff against NetSuite's governance limits, per-object sync health, and payload purge after 30 days. Shopify's side would stay Admin API webhooks over official OAuth — no App Store install, no theme edits.
Would it require SuiteScript customisation in my account?
That is the open design question, and the honest answer is that a near-real-time NetSuite to Shopify direction usually needs a user-event SuiteScript, because NetSuite has no native outbound webhook UI. Our preference is a scheduled, reconciling read path that needs zero custom code in your NetSuite account, with SuiteScript as an optional accelerator for merchants who want lower latency.
Put NetSuite at the top of the queue
One email. It counts as a vote, and it's the only way you'll hear the day NetSuite ↔ Shopify goes live.