Home, furniture, and decor suppliers selling on Wayfair typically run two disconnected systems: the Wayfair Partner Home / supplier portal on one side and ERPNext on the other. Orders get re-keyed by hand, inventory quantities drift between the two, ASNs and routing get built in spreadsheets, and settlement statements never quite match the sales invoices in ERPNext. Wayfair's CastleGate (wholesale/FBW) and dropship programs each have their own order shapes, SLA clocks, and label/routing requirements, and ERPNext core has no native concept of any of them — there is no Wayfair order source, no ASN document, and no place to store a partner PO number or a Wayfair-assigned carrier. This is where the native platform runs out of road: you can hold products and stock in ERPNext, but nothing bridges them to a Wayfair supplier feed.

ECOSIRE builds a proper Frappe app (its own module, DocTypes, and hooks.py) that lives inside your ERPNext site rather than a fragile external script. We model the integration as first-class documents: a Wayfair Settings single DocType for credentials and endpoints, a Wayfair Order staging DocType that maps cleanly onto ERPNext Sales Order / Delivery Note, a Wayfair Product Mapping DocType linking your ERPNext Item codes and warehouses to Wayfair SKUs and fulfillment nodes, and an ASN DocType for shipment notices. Wayfair's supplier APIs are integrated through a whitelisted service layer (@frappe.whitelist() methods) with token handling, retry, and idempotency so a replayed webhook or a re-run pull never double-books an order.

Technically, the connector runs on Frappe's own primitives. scheduler_events (cron and hourly) poll for new CastleGate and dropship POs, refresh order status, and push inventory feeds on the cadence you choose; doc_events in hooks.py fire on Delivery Note submit to generate the ASN and request shipping labels/routing, then write the tracking and carrier back to Wayfair. Server scripts and mapping tables translate Wayfair SKUs, ship nodes, and carrier codes to ERPNext Item, Warehouse, and shipping records, while a client script surfaces Wayfair status, PO number, and label links directly on the Sales Order form. A dedicated role profile and permission rules keep the Wayfair credentials and sync controls scoped to the operators who need them. Settlement files are parsed and reconciled against ERPNext invoices so remittances, chargebacks, and co-op deductions land as matched entries instead of manual guesswork. Every sync writes to an audit log DocType you can inspect and re-drive.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm which Wayfair programs you run (CastleGate, dropship, or both), your fulfillment nodes, carrier/routing rules, ERPNext version (v15 or v16), and your item and warehouse conventions. We build against your actual data on a staging bench, run UAT with real Wayfair POs and a settlement file, and only then install to production behind a documented rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source, install and configuration, technical and user documentation, a training session, and a post-go-live support window — and the git repository is handed to you so you are never locked in.