Connect the store to purchasing, stock, delivery and accounts around the tasks your team actually performs. A useful integration makes failed or missing orders visible as well as moving the successful ones.
Start with the current integration options
ERPNext's version 15 migration guide records the removal of the old built-in WooCommerce integration. An old setup article is not proof that current ERPNext includes it. Frappe's ecommerce_integrations repository does not list WooCommerce among its supported integrations. Evaluate a maintained third-party connector for your exact versions, or scope custom work using WooCommerce's management REST API and Frappe's API. Name the app, maintainer, release and supported flows in the proposal before choosing a route.
- ERPNext's record of WooCommerce removal
- Integrations listed by Frappe's external app
- How the separately installed Shopify app differs
Agree the sync scope
The current WooCommerce REST API uses wc/v3 and exposes orders, products, variations and refunds. API availability does not mean an ERPNext connector already implements the following flows. Choose and verify the ones your business needs.
| Record | Possible direction | Business rule to settle |
|---|---|---|
| Orders | WooCommerce to ERPNext Sales Order | Which payment and order states should create work for the warehouse? |
| Products and variations | One system owns each agreed field | Match product and variation IDs to unique ERPNext item codes. |
| Sellable stock | ERPNext to the store when it controls inventory | Agree warehouse totals, reservations, stock buffers and backorders. |
| Invoices and payments | Only the approved accounting flow | Map discounts, fees, shipping, tax and payment references. |
| Returns and refunds | Explicit corrections in both systems | Agree stock receipt, credit and refund-matching responsibilities. |
Review your actual store, not just standard products
Record your WordPress, WooCommerce and ERPNext versions, hosting and relevant extensions. Bring examples of variable products, bundles, subscriptions, custom order states and payment gateways that you use. Their rules may need connector support or additional work. Decide who edits product names, prices and addresses; otherwise the next update may overwrite someone's correction. Keep external IDs with the matched ERPNext records and establish what happens when an item has no match.
Keep orders and money consistent
A paid order, delivered order and refunded order describe different events. Agree when ERPNext creates an invoice, how partial shipments work and how a refund affects existing documents. Match taxes, shipping, discounts, currency and rounding with your finance owner. For an Indian store, include the required GST invoice details and compliance workflow. If an order contains one available item and one backordered item, demonstrate the agreed reservation and delivery behavior before launch. A store status change alone must not be treated as proof that the books are correct.
- WooCommerce order states and financial fields
- Plan any continuing connection to QuickBooks separately
Acceptance checks for normal work and failures
- Place a taxed, discounted order containing a variation; match every line and total.
- Test pending payment, payment failure, cancellation, partial delivery and partial refund.
- Deliver a notification twice; confirm only one set of ERPNext documents exists.
- Simulate a missed notification and recover the missing order without duplicating earlier orders.
- Change the agreed stock source and confirm the store's available quantity and backorder rule.
- Check a realistic batch of orders, including pagination, and produce a list of unmatched records.
Make failures someone's responsibility
Use authenticated HTTPS access and verify webhook signatures, which confirm where a notification came from. WooCommerce records delivery logs and can disable webhooks after repeated failures. Assign an owner to check disabled notifications, failed records and missing orders, with an approved retry process. Frappe API access should use an integration user with only the necessary permissions. Agree monitoring, update checks, maintenance and initial record loading in the quote. An accounting migration is separate from continuing store sync. Fullsend scopes an assessed connector or custom integration; external app charges and ongoing integration care are separate items, not hidden inside a standard module price.
- WooCommerce webhook signatures, logs and failure behavior
- Frappe authentication and document API
- See the ERPNext module package prices
- Plan an accounting migration alongside the store connection
- Agree data loading and ongoing support responsibilities
Related decisions
Official references: ERPNext version 15 migration and removed integrations · Frappe ecommerce_integrations supported integrations · WooCommerce REST API overview · WooCommerce current REST API v3 resources · WooCommerce order states and fields · WooCommerce refund operations · WooCommerce webhook signatures, logs and failures · Frappe REST API authentication and permissions