Etsy makers hit a wall the moment their shop outgrows spreadsheets. Orders land in the Etsy dashboard, stock lives in your head or a Google Sheet, and ERPNext has no idea any of it happened. You end up re-keying every sale into a Sales Order, guessing at real inventory across multiple listings and variations, and reconciling Etsy's transaction and processing fees against your books by hand at month-end. ERPNext is a genuinely capable manufacturing and inventory system for a growing craft brand, but out of the box it has no concept of an Etsy shop, its listing model, or its fee structure. That gap is exactly what this connector closes.

ECOSIRE builds a proper Frappe app for your ERPNext site — not a brittle CSV import. It ships as an installable app with its own module, custom DocTypes (for example an Etsy Shop connection record, Etsy Sync Log, and mapping tables between Etsy listings and ERPNext Items), and configuration stored in ERPNext rather than hard-coded. Integration with Etsy runs over the official Etsy Open API v3 using OAuth 2.0, with tokens stored and refreshed server-side. Inbound receipts are pulled on a schedule via Frappe scheduler_events and turned into ERPNext Sales Orders (and optionally Delivery Notes and Sales Invoices) with buyer, shipping address, line items, and per-order fees mapped correctly. Outbound changes — a stock movement or a price update in ERPNext — are pushed back to the matching Etsy listing through hooks.py document events on Item and Stock Ledger updates, so the two systems stay in step both ways.

Under the hood the app is built the way a Frappe engineer would expect: whitelisted methods expose the sync endpoints, server scripts and controller logic handle the mapping and idempotency (so a re-run never double-creates an order), and client scripts add the buttons and status indicators your team actually uses. Etsy transaction fees, payment processing fees, and shipping labels are mapped to the right ERPNext accounts, and VAT/tax handling is configured against your tax templates so the numbers reconcile instead of needing a manual adjustment. Access is governed by ERPNext permissions and role profiles, and every sync run is recorded in a log DocType so you can see exactly what came in, what failed, and why. Multi-shop sellers get one connection record per shop with isolated credentials and mappings. The app targets current Frappe/ERPNext v15 and is built forward-compatible with v16.

Because this is build-to-order, nothing is a black box you download and hope fits. We start with a short scoping call to confirm your shops, listing/variation model, fee and tax treatment, and which documents you want created. We build against that scope, deliver on a staging site for you to run real orders through during UAT, then install on production with a rollback plan. Typical delivery is one working week from confirmed scope depending on complexity and shop count. You get the full source in a git repository, documentation, a training session for your team, and a post-go-live support window — this is a real engineering engagement, not an instant-download listing.