If you sell wholesale on Faire and run your operations in ERPNext, the gap between the two is where margin quietly leaks. Retailer orders land in the Faire dashboard, someone re-keys them into a Sales Order, stock levels drift because two systems each think they own the truth, and tracking numbers get pasted back into Faire by hand under a fulfillment SLA. ERPNext core has no native concept of a Faire channel — there is no Faire connected app, no marketplace DocType, and no scheduler job reaching the Faire API — so out of the box every order is a manual round trip. Generic import tools and spreadsheet uploads don't understand Faire's wholesale pricing, brand-portal returns, or the reservation semantics that keep you from overselling a hero SKU across channels.

The ERPNext Faire Wholesale Connector is a proper Frappe application — its own module with dedicated DocTypes (a Faire Settings single for API credentials and sync toggles, a Faire Sync Log for auditable runs, and item/order mapping DocTypes) rather than a pile of loose scripts. It authenticates to the Faire API and, on a scheduler event, pulls new and updated orders, mapping each to an ERPNext Sales Order with the correct Customer (the retailer), items resolved by SKU or barcode, Faire wholesale price, taxes, and a channel reference stored on the document for traceability. Product and price publishing runs the other direction: a whitelisted method pushes selected Items, variants, wholesale/RRP pricing, and imagery from ERPNext to your Faire catalog, so ERPNext stays the source of truth for what you sell and for how much.

Technically the app leans on the parts of Frappe that make integrations robust. hooks.py doc events fire on Delivery Note and Stock Entry submit to trigger inventory recalculation and tracking writeback; server scripts and background jobs (frappe.enqueue) keep API calls off the request thread and safe to retry; scheduler events (typically every few minutes) drive the order pull and inventory reconciliation. Inventory sync is two-way and idempotent — bin-level available quantity is computed per warehouse and pushed to Faire, while Faire-side adjustments are reconciled back — with collision handling so a race between channels doesn't oversell. A dedicated Faire Integration role profile and permission rules scope who can see credentials and rerun syncs, and every external call is logged with request/response context for support. When a shipment is confirmed, the connector writes the carrier and tracking number back to the Faire order to satisfy fulfillment timelines, and brand-portal return requests are ingested so a Return/Credit Note can be raised in ERPNext against the original order.

Because this is build-to-order, nothing here is a one-click download. We start with a short scoping call to confirm your Faire account setup, warehouse and pricing model, variant structure, and returns workflow, then we build and configure the connector against your ERPNext instance (Frappe/ERPNext v15 or v16, self-hosted or Frappe Cloud). You get the app installed on a staging bench first for UAT, then a supervised go-live. Typical delivery is one working week from confirmed scope, and you receive the source code and git repository so the integration is yours to own and extend.