A Shopify order should reach the team buying, stocking and shipping the goods without someone entering it twice. Start by agreeing which records move, which system controls them and how failures get noticed.
Check the connector before planning the launch
Frappe's Shopify connector is a separately installed ecommerce_integrations app. Reviewed on 14 October 2026, its version-15 branch declares Frappe and ERPNext 15 compatibility; version-16 declares version 16. That declaration does not prove your store's workflow. The inspected version-16 code still requests Shopify API 2024-01, so check the installed release, current authentication and supported API behavior before committing. Shopify calls its REST Admin API legacy and requires GraphQL for new public apps; this does not mean every existing custom integration has stopped working.
- Frappe's external integration app
- Shopify API version requested by the inspected branch
- Shopify's current API guidance
Choose the records and direction
Frappe documents incoming orders and configurable stock, payment and fulfilment behavior. Confirm each flow in the selected release. Use this table to agree the work, not as a promise that every connector covers every row.
| Record | Direction to agree | Decision before setup |
|---|---|---|
| Orders | Shopify to ERPNext Sales Order | Which order states qualify, and which company receives them? |
| Products and customers | Match existing records; create missing ones only by agreement | Use store product and variant IDs, item codes and customer rules. |
| Available stock | ERPNext to Shopify when ERPNext owns stock | Map warehouses to locations and agree reservations and sellable quantities. |
| Payments and fulfilments | Selected events into ERPNext documents | Agree invoice timing, partial delivery and payment-account mapping. |
| Cancellations and refunds | An explicit correction workflow | Decide who creates returns, credits and payment adjustments. |
Give each record one owner
If ERPNext controls stock, a manual Shopify stock edit can be overwritten by the next update. Decide separately who controls descriptions, prices and customer details. Keep the Shopify order ID linked to its ERPNext documents; names and display order numbers alone are poor matching rules. Review variants, units, bundles and multiple locations against the actual app. For goods sold in fractional quantities, agree a conversion because Shopify inventory uses whole units.
Check the money and the exceptions
Map discounts, shipping and taxes with your finance owner. For Indian sales, confirm GST treatment, invoice details and the applicable compliance setup. For example, a partly shipped order that is later cancelled needs a decision about the delivered goods and existing invoice. The inspected app's cancellation handler does not automatically reverse linked invoices and delivery notes. A refund at the payment gateway is also separate from matching the refund in your books. Overseas orders need agreed currency and rounding rules.
Acceptance checks before daily orders move
- Create a discounted, taxed order with shipping; match its items and total in ERPNext.
- Deliver part of an order, take payment and process an agreed cancellation or refund.
- Send the same order notification again; confirm no second order, invoice or payment is created.
- Interrupt the connection, restore it and reconcile missing orders by their Shopify IDs.
- Change stock in the agreed warehouse and confirm the correct Shopify location updates.
Agree who keeps the connection working
Shopify notifications can arrive again, arrive out of order or be missed. Assign an owner to review failed records, check missing orders and approve retries. Specify the expected delay, peak order volume, monitoring and checks after app or API updates. Initial record loading and historical orders need their own agreed scope. If you are also changing accounting systems, plan that migration separately from store sync. Fullsend reviews the available app or custom API work for your setup; connector charges, integration work, hosting and ongoing support are listed separately from standard ERPNext implementation.
- See module prices and build an implementation package
- Scope initial data movement and ongoing support
- If you are also moving your QuickBooks accounts
- Compare the WooCommerce integration approach
Related decisions
Official references: Frappe ecommerce_integrations repository · Declared Frappe and ERPNext 15 compatibility · Declared Frappe and ERPNext 16 compatibility · Shopify integration documentation · Inspected Shopify API version and event mapping · Inspected Shopify order and cancellation handling · Shopify REST and GraphQL requirements · Shopify API version lifecycle · Shopify webhooks and reconciliation