If your storefront runs on WooCommerce but your operations, accounting, and inventory live in ERPNext, someone on your team is almost certainly re-keying orders by hand, reconciling stock across two systems, and discovering oversells after the fact. ERPNext ships no native WooCommerce integration — the closest core primitive is a generic REST API and webhook surface, which leaves you to hand-build the field mapping, the idempotency, the variant matching, and the failure handling yourself. That is exactly the gap this connector closes.

ECOSIRE builds this as a proper Frappe app — its own module, DocTypes, and hooks.py — installed onto your ERPNext v15 or v16 site. Inbound, WooCommerce webhooks (order.created, order.updated, product.updated, customer.created) hit whitelisted endpoints exposed via @frappe.whitelist(), each verified against the store's webhook secret before a background job processes it through the Frappe queue so your web workers stay responsive. Orders land as ERPNext Sales Order or Sales Invoice documents with the WooCommerce order id stored on a custom field for idempotent upserts; customers are matched or created as Customer + Contact + Address records. Outbound, we register doc_events in hooks.py so that stock-ledger movements and Item Price changes push back to WooCommerce over its REST API, and a Delivery Note submission or manual status change writes the order status back to the store (processing, completed, cancelled) with the tracking number where you carry one.

Product and variant sync is handled deliberately: ERPNext Item templates with attributes map to WooCommerce variable products, and each Item Variant maps to a specific WooCommerce variation by SKU, so price lists and stock update at the variation level rather than clobbering the parent. A scheduled scheduler_events job runs a periodic reconciliation sweep to catch anything a missed webhook dropped, and every sync attempt is logged to a WooCommerce Sync Log DocType with the payload, direction, and error, so failures are visible and replayable instead of silent. Refunds map to ERPNext credit notes and coupon usage is carried onto the sales document, keeping finance's numbers honest.

Because this is build-to-order, nothing is a one-size download. We start with a short scoping call, agree the exact field mappings, tax handling, warehouse-to-store rules, and which direction is authoritative for each entity, then build against your real WooCommerce and a staging ERPNext site. You get the app source, install and configuration on your environment, UAT on staging with a rollback plan, and a post-go-live support window. Typical delivery is one working week from confirmed scope, depending on how many edge cases (multi-warehouse, multi-currency, B2B pricing) you need covered.