You connect Shopify to ERPNext so orders, customers, stock and invoices flow into one system instead of living in two. In 2026 there are two solid paths: the official Ecommerce Integrations app, or a custom webhook flow through n8n. This guide walks both, and flags the January 2026 Shopify auth change that trips people up.
Short answer
ERPNext syncs with Shopify through the official Ecommerce Integrations app, which pulls Shopify orders into ERPNext as Sales Orders, creates missing customers and items, and pushes ERPNext stock levels back to Shopify. You raise Sales Invoices from those orders inside ERPNext. For custom rules, an n8n webhook flow is the flexible alternative.
I run ERPNext implementations at Mith Tech in Bengaluru, and Shopify is one of the most common stores I'm asked to connect. Most Indian D2C brands start on Shopify for the storefront, then outgrow its back office once GST invoicing, warehouse stock and purchase planning enter the picture. Honest take: the connector handles the happy path well, but the January 2026 Shopify authentication change means a lot of older setup guides you'll find online are now wrong.
Which ERPNext Shopify connector should you use in 2026?
Use the Ecommerce Integrations app from Frappe as your default. The older standalone erpnext_shopify connector is deprecated, its functionality having moved into the newer, actively maintained app that ships releases through 2026 and supports current ERPNext versions. Reach for a custom n8n flow only when your mapping rules outgrow the connector.
Here's how the realistic options compare on fit, not price.
| Option | Best for | Sync direction | Custom logic |
|---|---|---|---|
| Ecommerce Integrations app | Standard Shopify → ERPNext order + stock sync | Orders in, stock out | Limited, config-driven |
| n8n webhook flow | Non-standard mapping, multi-store, conditional rules | Whatever you build | Full control |
| Third-party paid connectors | Teams wanting a managed, supported product | Vendor-defined | Vendor-defined |
The app covers most single-store setups out of the box. n8n earns its place when you have rules like "only sync paid COD orders after confirmation" or "split one Shopify order across two ERPNext warehouses" — logic a config screen can't express. If you're weighing your whole stack, my open-source Shopify alternative piece covers when to keep Shopify versus move the storefront too.
Skimmable summary: default to the Ecommerce Integrations app; use n8n when your mapping rules get complex.
What actually syncs between Shopify and ERPNext?
Orders flow from Shopify into ERPNext as Sales Orders, with the connector creating any missing customer and item records automatically from the Shopify payload. Stock moves the other way: ERPNext pushes inventory levels for changed items back to Shopify so your storefront reflects real warehouse counts. Invoices are generated inside ERPNext.
Orders → Sales Orders
Each Shopify order becomes an ERPNext Sales Order. Missing customers and items are created on the fly from the order data.
Stock → Shopify
ERPNext is the source of truth for inventory. Changed item quantities are pushed to Shopify to keep the storefront accurate.
Invoices in ERPNext
You raise the Sales Invoice from the synced Sales Order inside ERPNext — where your GST setup, HSN codes and tax templates live.
Customers & items
Buyer details and products referenced in an order are matched or created, so you don't maintain two separate masters by hand.
One point worth setting expectations on: the default connector's job is to bring orders in and keep stock accurate. It does not push finished tax invoices back to the Shopify order timeline. That's usually fine for Indian sellers, because your compliant GST invoice belongs in ERPNext anyway, not in Shopify.
Skimmable summary: orders and customers come in, stock goes out, and invoices are created and filed inside ERPNext.
How do you set up the Shopify connector step by step?
Setup has two halves: create a custom app inside Shopify to get API access, then configure Shopify Settings inside ERPNext. Since Shopify deprecated legacy private apps on 1 January 2026, you now create the app under Settings → Apps and sales channels → Develop apps, and you copy the Admin API access token the moment it appears — Shopify will not show it again.
Install the Ecommerce Integrations app
On Frappe Cloud, install it from the Marketplace. On a self-hosted bench, use bench get-app and bench install-app ecommerce_integrations, then run bench migrate. Confirm it appears in your installed apps list.
Create a custom app in Shopify
In your Shopify admin, go to Settings → Apps and sales channels → Develop apps → Create an app. Give it a name like "ERPNext Sync". This replaces the old "manage private apps" flow removed in January 2026.
Grant Admin API scopes
Under Configuration, enable read and write scopes for orders, products, inventory and customers. At minimum you need read_orders, write_orders, and the product and inventory scopes so both directions of the sync can work.
Install the app and copy the access token
Install the custom app on your store. Shopify then reveals the Admin API access token once. Copy it immediately and store it safely — you cannot retrieve it later and will otherwise have to reinstall.
Configure Shopify Settings in ERPNext
Open Shopify Settings in ERPNext. Enter your store URL and the access token. Map your company, price list, warehouse, and — importantly for India — your tax templates so GST is applied correctly on the resulting Sales Orders.
Test with one real order
Place a small test order in Shopify. Confirm a Sales Order appears in ERPNext with the right customer, items, warehouse and taxes. Then change a stock quantity in ERPNext and confirm it reflects in Shopify.
The January 2026 credential change
Shopify's new Develop-apps flow and its developer dashboard can hand you a Client ID and Secret (OAuth-style) rather than the classic Access Token some ERPNext screens expect. If your connector version predates OAuth 2.0 support, you may hit an authentication mismatch. Community work to add OAuth 2.0 to Ecommerce Integrations is in progress. The safe move in the interim is to generate the Admin API access token via the store's Develop-apps flow, and to run a recent connector version. If in doubt, verify the exact steps against Shopify's current official docs before going live.
Skimmable summary: build a custom Shopify app, grant order/product/inventory scopes, copy the one-time access token, then map company, warehouse and taxes in ERPNext.
When should you use n8n instead of the connector?
Choose n8n when your business rules are too specific for a settings screen — conditional syncing, custom field mapping, multi-store consolidation, or enriching an order before it lands in ERPNext. n8n listens to a Shopify webhook such as orders/create, transforms the payload, then calls the ERPNext REST API to create exactly the document you want, on your terms.
A typical n8n flow looks like this:
Webhook trigger
Add a Shopify webhook for orders/create (and orders/paid if you only act on paid orders) pointing at an n8n Webhook node. Shopify expects a 200 response within its short timeout, so keep the entry node fast.
Transform and map
Use n8n nodes to reshape the order — map SKUs to ERPNext item codes, pick the right warehouse, apply your tax template, and add any custom fields your workflow needs.
Create the ERPNext document
Call the ERPNext REST API with an API key and secret to create the Sales Order (or a draft Sales Invoice, if that's your flow). Handle errors and log failures so nothing is lost silently.
n8n is itself open source and self-hostable, which fits the same no-lock-in philosophy as ERPNext. For the full pattern — authentication, the REST endpoints, and idempotency — see my dedicated ERPNext and n8n integration walkthrough. If you're building something more B2B and headless, the MedusaJS vs Shopify Plus for B2B comparison is a useful companion read.
Skimmable summary: use n8n when you need conditional logic, custom mapping or multi-store rules the connector can't express.
How does GST invoicing work once orders sync?
GST invoicing stays inside ERPNext, because that's where your tax templates, HSN codes, place-of-supply logic and e-invoicing sit. The connector brings the Shopify order in as a Sales Order; you then create the Sales Invoice from it in ERPNext, apply the correct GST template, and generate a compliant tax invoice — and e-invoice or e-way bill where thresholds apply.
This separation is a feature, not a limitation. Shopify's storefront collects the order; ERPNext produces the legally compliant document your accountant and the GST portal expect. Keeping invoicing in ERPNext also means one audit trail across your Shopify sales, offline sales, and B2B channels — not a patchwork per platform. ERPNext ships strong Indian localisation for exactly this, which is a big reason I recommend it to Bengaluru D2C brands over stitching together several point tools.
Skimmable summary: orders sync in, but you raise the GST-compliant Sales Invoice inside ERPNext where localisation lives.
Frequently asked questions
Is the old ERPNext Shopify app still usable?
The original erpnext_shopify connector is deprecated and no longer the recommended path. Its functionality moved into Frappe's Ecommerce Integrations app, which is actively maintained with releases continuing through 2026. For any new setup, install Ecommerce Integrations rather than the legacy app.
Does the connector create GST invoices in Shopify?
No. The default connector pulls Shopify orders into ERPNext as Sales Orders and keeps stock in sync; it does not push finished tax invoices back to Shopify. You raise the GST-compliant Sales Invoice inside ERPNext, where your tax templates, HSN codes and e-invoicing are configured.
What broke with Shopify integrations in January 2026?
Shopify deprecated legacy custom and private apps created in the admin console on 1 January 2026. New apps are created via the Develop-apps flow and, in some cases, an external developer dashboard that issues OAuth-style Client ID and Secret credentials. Older ERPNext connector versions expecting a classic access token can hit an auth mismatch until OAuth 2.0 support lands.
Can I sync inventory in real time?
Inventory syncs from ERPNext to Shopify when item quantities change, keeping your storefront counts accurate against your warehouse. For truly instant reactions to store events, a webhook-driven n8n flow gives you the tightest control over timing and which changes trigger a sync.
Does ERPNext charge per user like Shopify apps do?
No. ERPNext is free and open source under the GPLv3 licence — there are no per-user seat fees for the software itself. Your costs are hosting and implementation. Shopify and its paid connectors follow subscription models; pricing there varies by edition, so check each vendor's official page.
Can I connect more than one Shopify store?
Yes. The Ecommerce Integrations app supports multi-channel and multi-company setups, and an n8n flow can consolidate several stores into one ERPNext instance with per-store mapping. This is common for brands running separate storefronts for different regions or brands under one back office.
About the author
I'm Manoj, an ERPNext implementation consultant at Mith Tech in Bengaluru. I help Indian SMBs and D2C brands connect their storefronts, warehouses and finance into one open-source ERP — without per-seat licence traps or vendor lock-in. I work hands-on with ERPNext, Frappe, and automation tools like n8n to fit the software to how a business actually operates.
Want your Shopify store wired into ERPNext cleanly?
Explore what a fully connected setup looks like with ERPNext, or read how the wider Frappe and ERPNext platform fits Indian SMBs.