ERPNext Faire Wholesale Connector

Key Features

Scheduled Faire order pull via a `scheduler_events` job that maps each order to an ERPNext Sales Order with retailer Customer, SKU/barcode-resolved items, wholesale price, and taxes

Idempotent order sync keyed on the Faire order id (stored on the Sales Order) so re-runs never create duplicate documents

Dedicated Frappe module with `Faire Settings` (single DocType) for API token, warehouse mapping, and per-feature sync toggles

`Faire Sync Log` DocType recording request/response, status, and record counts for every run — auditable and re-runnable from the desk

Catalog and pricing push via a whitelisted method: Items, variants, wholesale/RRP price lists, and images published from ERPNext to Faire

Two-way, bin-level inventory sync computing available quantity per Warehouse and reconciling Faire-side adjustments back into ERPNext

`hooks.py` doc events on Delivery Note / Stock Entry submit that trigger tracking writeback and stock recalculation without manual steps

Shipment tracking writeback — carrier and tracking number pushed to the Faire order on fulfillment to meet Faire's shipping SLA

Brand-portal returns ingestion that raises a Return / Credit Note in ERPNext against the original Sales Order

Background execution with `frappe.enqueue` and retry/backoff so Faire API rate limits and timeouts don't block the desk or lose data

`Faire Integration` role profile plus permission rules restricting credential visibility and sync re-runs

Item mapping DocType linking Faire product/variant ids to ERPNext Items for reliable resolution across catalog changes

Oversell protection with collision handling when the same SKU sells concurrently on Faire and other channels

Optional client script on Sales Order surfacing Faire channel, order status, and a manual re-sync action for support and finance teams

Compatible with Frappe/ERPNext v15 and v16, deployable on self-hosted benches or Frappe Cloud

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks from confirmed scope, and you receive the source code and git repository so the integration is yours to own and extend.

What you get

Installable Frappe app source code for your ERPNext version (v15 or v16), built to your confirmed scope

Installation and configuration on your bench, including `Faire Settings`, warehouse/price-list mapping, and scheduler setup

Technical documentation covering DocTypes, hooks, whitelisted methods, scheduler events, and the Faire API touchpoints

User guide plus a live training session for your operations and finance team

UAT on a staging bench with a documented rollback plan before production go-live

Post-go-live support window for bug fixes and sync tuning

Git repository handover so you own and can extend the integration

Faire credential and permission setup guidance (role profile, API token handling, sandbox vs. live)

Who this is for

Faire brand operations lead

Runs day-to-day wholesale fulfillment for a brand on Faire and is tired of re-keying retailer orders into ERPNext. Needs orders to land as Sales Orders automatically and tracking pushed back before the Faire SLA lapses.

Maker / founder scaling wholesale

A small-batch maker whose Faire volume has outgrown manual processes. Wants ERPNext to stay the single source of truth for catalog, pricing, and stock without hiring an ops person to babysit two dashboards.

ERPNext administrator / systems owner

Owns the Frappe bench and cares about a clean app, proper DocTypes, permission scoping, auditable sync logs, and code they can read and extend — not a black-box connector.

Finance / inventory manager

Needs accurate two-way inventory and correct wholesale pricing on every order so stock valuation and revenue reconcile, and returns from the Faire brand portal produce proper Credit Notes in ERPNext.

How ERPNext Faire Wholesale Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Faire order import	Auto-pulled to Sales Orders on a scheduler, idempotent by order id	Possible but you design and maintain the mapping yourself	Rarely supports Faire specifically; generic import at best
Two-way inventory	Bin-level per warehouse with oversell collision handling	Achievable with significant in-house effort	Often one-way or channel-generic, not Faire-aware
Tracking writeback	Carrier + tracking pushed to Faire on fulfillment via doc events	Must be built and wired to Delivery Note events	Inconsistent; may need manual export
Returns handling	Brand-portal returns raise Credit Notes in ERPNext	Extra scope, often deprioritized	Usually out of scope
Architecture	Proper Frappe app: DocTypes, hooks, whitelisted methods, role profile	Depends on your team's discipline and standards	Black box; limited visibility or extensibility
Ownership	Source code + git repo handed over to you	You own it, but you also built and must maintain it	Licensed; source typically closed
Version support	Built and tested for your ERPNext v15 or v16	Whatever your team targets	Depends on vendor's release cadence
Support	Post-go-live window, docs, and training included	Self-supported unless you retain help	Vendor tickets, variable responsiveness

Frequently Asked Questions about ERPNext Faire Wholesale Connector

Is this an existing app I can download and install from the Frappe Cloud Marketplace?

No. This is a build-to-order integration. ECOSIRE scopes, builds, installs, and supports it for your specific Faire account and ERPNext setup. There is no instant download — you get the source code and git repository once your version is built and delivered.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on the complexity of your variant structure, pricing model, warehouse layout, and returns workflow, which we lock down in the initial scoping call before any build work starts.

Which ERPNext versions do you support?

Frappe/ERPNext v15 and v16, on self-hosted benches or Frappe Cloud. We confirm your exact version and hosting during scoping and build against it so the app installs cleanly on your instance.

How does the inventory sync avoid overselling across channels?

Inventory is synced two-way at the bin level per Warehouse, driven by scheduler events and Delivery Note / Stock Entry doc events. The connector recomputes available quantity and includes collision handling so concurrent sales on Faire and other channels don't oversell a shared SKU. Sync frequency is configurable in `Faire Settings`.

What happens with returns from the Faire brand portal?

Return requests raised in the Faire brand portal are ingested by the connector and used to raise a Return / Credit Note in ERPNext against the original Sales Order, so your inventory and finance records stay consistent with what happened on Faire.

What do we get for support and updates after go-live?

Every build includes a post-go-live support window for bug fixes and sync tuning, plus full technical documentation and the git repository. Because you own the source, your team or ours can extend it later. Ongoing maintenance or Faire API-change updates beyond the initial window can be arranged as a support agreement.

Will this modify ERPNext core or is it a separate app?

It is a separate, self-contained Frappe app with its own module, DocTypes, hooks, and whitelisted methods. It does not patch ERPNext core, which keeps your instance upgrade-safe and makes the integration easy to audit, version, and remove if ever needed.