- Home
- Apps
- Multichannel & PIM Tools
- Faire Wholesale Marketplace Connector
Illustrative previewAn AL extension that connects Faire Wholesale to Dynamics 365 Business Central so brand orders,
catalog listings, inventory, shipments and settlement payouts live in one system. Built to order by
ECOSIRE for your Business Central version and your posting setup.
What is Faire Wholesale Marketplace Connector?
An AL extension that connects Faire Wholesale to Dynamics 365 Business Central so brand orders, catalog listings, inventory, shipments and settlement payouts live in one system. Built to order by ECOSIRE for your Business Central version and your posting setup. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
About this Product
If you sell on Faire, your wholesale demand arrives in a portal that knows nothing about your Business Central item ledger. Someone exports a CSV of Faire orders and keys them in as sales orders; someone else remembers to decrement availability on Faire after a large direct-to-retail order ships; a third person tries to explain why the Faire payout that hit the bank is smaller than the sum of the invoices, because Faire has already netted commission, shipping and any damage or return allowances. Business Central out of the box has no Faire awareness at all: there is no marketplace order staging, no listing entity, no fee-aware settlement reconciliation, and nothing that maps Faire's brand-side order lifecycle onto Sales Header, Sales Line and the warehouse documents you actually post against.
We build a dedicated AL extension that closes that gap. Faire orders are pulled into a marketplace order staging table by a codeunit running under a Job Queue Entry, keyed on the Faire order id so a re-run can never create a duplicate sales order. A mapping layer resolves Faire product and option identifiers to Business Central Item No. plus variant, resolves the Faire retailer to a customer (auto-created from a template or matched to an existing account), and applies a status map that turns Faire's order states into your document flow — new orders become released or open sales orders per your rule, backordered items respect your reservation policy, and cancellations raise an exception for a human rather than silently deleting posted work. Item availability and price changes flow the other way from event subscribers on item ledger and price-related publishers, batched and throttled so a large posting run does not hammer the Faire API. Listings are exported with your category and attribute mapping so Faire's taxonomy is driven from a maintained setup table, not from a spreadsheet.
Fulfilment closes the loop: when you post a warehouse shipment or a sales shipment, the extension pushes the carrier, tracking number and shipped lines back to Faire, and stores the marketplace response against the document for audit. Settlements are the piece most connectors ignore. We import the Faire payout statement, reconcile each order-level amount against the corresponding posted invoice, and generate the fee, commission and adjustment lines as a general journal batch against G/L accounts you nominate in a setup page — so the bank receipt reconciles cleanly and your gross-versus-net revenue is visible in Business Central rather than in the Faire dashboard. Everything is exposed through your own table extensions, page extensions and list pages, secured by a dedicated permission set, and instrumented with a marketplace log so a failed API call is diagnosable without opening a developer session.
Technically this ships as an AL extension for your Business Central release wave, packaged as a per-tenant extension for SaaS or deployed into your on-premises container as you prefer. Faire is reached over its REST API from an HttpClient wrapper with retry, backoff and a stored API key held in Isolated Storage. Business Central-side integration points are proper event subscribers and interface codeunits rather than base-application modifications, so upgrades stay clean. Where you want the data outside Business Central — a Power BI marketplace margin report, a Power Automate alert on failed order import — we expose the staging and log tables through API pages (REST API v2.0 / OData v4) and, where you use Dataverse, through the standard virtual-table route.
This is build-to-order, not an AppSource download. We start with a scoping call, confirm your Faire account structure, item and variant conventions, customer templates, dimension usage and settlement posting accounts, then write the extension against your Business Central version. Typical delivery is one working week from confirmed scope. You get the AL source, a UAT pass on a sandbox with your own Faire credentials before anything touches production, a documented rollback, and a support window after go-live.
What you get
- Installable AL extension source and compiled .app built for your Business Central version and release wave (SaaS per-tenant or on-premises)
- Installation and configuration on your sandbox and production environments, including setup page walkthrough, Job Queue Entry scheduling and permission set assignment
- Technical documentation: object ranges, table/page extension list, event subscribers, API surface, field mapping reference and settlement posting logic
- End-user guide plus a live training session for your sales, warehouse and finance users covering daily operation and the exception queue
- UAT on a staging environment using your own Faire sandbox or read-limited credentials, with a signed-off test script and a documented rollback plan
- Post-go-live support window with defect fixes on the delivered scope at no extra charge
- Git repository handover with full commit history, branch/tag for the delivered release and build instructions
- Data migration and reconciliation of open Faire orders and existing listings at cutover
Who this is for
Wholesale operations manager at a consumer brand
Runs Faire alongside direct wholesale accounts and is tired of re-keying orders and chasing stock discrepancies. Needs Faire orders to land as real Business Central sales orders with the right customer, dimensions and posting groups so the warehouse picks from one queue.
Finance controller or management accountant
Owns the bank reconciliation and cannot explain the gap between invoiced revenue and the Faire payout. Needs commission, shipping and adjustment fees posted to nominated G/L accounts per settlement so gross-to-net is auditable inside Business Central.
E-commerce or channel manager
Maintains the Faire catalog and pricing. Needs listings, images, options and category attributes exported from Business Central item data so the ERP is the single source of truth rather than a spreadsheet that drifts.
IT lead or Business Central partner consultant
Responsible for a clean, upgradeable tenant. Needs an extension built on event subscribers and API pages with its own object range, permission set and telemetry, plus source code and documentation handed over.
How Faire Wholesale Marketplace Connector Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Dynamics 365 Business Central Native |
|---|---|---|---|---|
| Fit to your Faire account and item model | Built against your actual variants, templates and dimensions after a scoping call | Fits perfectly if your in-house AL developer has Faire API time available | Generic mapping that assumes a conventional SKU structure | No Faire concept exists in Business Central at all |
| Settlement and fee reconciliation | Statement import with per-order matching and journal lines to your nominated G/L accounts | Usually deferred as phase two and often never built | Commonly limited to order and stock sync; payouts stay manual | Manual journals from the Faire dashboard each payout cycle |
| Delivery time and cost profile | one working week from confirmed scope, fixed quote | Months of internal developer time competing with other backlog | Install in a day, then weeks of workarounds for what it does not do | Immediate, but the work stays with your staff forever |
| Source code ownership | Full AL source handed over in your git repository | You own it, and you own the maintenance and the bus factor | Closed source; changes depend on the vendor roadmap | Not applicable |
| Upgradeability across release waves | Event subscribers and interface codeunits only, retested each wave under support | Depends entirely on the discipline of whoever wrote it | Vendor-managed, but you wait for their release schedule | Nothing to break, nothing to gain |
| Handling unmapped SKUs and edge cases | Exception queue with actionable messages; nothing posts on a guess | Typically discovered in production when the first mismatch appears | Often a generic error log requiring vendor support to interpret | Caught by whoever is doing the manual entry, if they notice |
| Reporting and automation surface | API pages over staging, mapping and log tables for Power BI, Power Automate and Dataverse | Whatever was scoped; usually added later under pressure | Vendor-defined endpoints, sometimes none | Standard Business Central reporting only, with no marketplace data in it |
| Who you call when something breaks | The engineers who wrote it, within the agreed support window | Your own team, in the middle of another project | A ticket queue with no knowledge of your configuration | No integration, so no integration support |
Frequently Asked Questions about Faire Wholesale Marketplace Connector
Is this an existing app I can download from Microsoft AppSource today?
No. This is a build-to-order extension. ECOSIRE writes it against your Business Central version, your Faire account structure and your posting setup, then installs and supports it. There is no instant download and no trial link — the process starts with a scoping call.
How long does delivery take?
Typical delivery is one working week from confirmed scope. The clock starts once we have agreed the field mapping, status rules, settlement posting accounts and sandbox access — not at the initial enquiry. Larger scopes (multiple Faire brand accounts, unusual variant models, heavy warehouse customisation) are quoted with their own timeline before you commit.
What happens with support and Business Central updates?
You get a post-go-live support window for defects in the delivered scope. Beyond that we offer an ongoing support and maintenance agreement covering Business Central release-wave compatibility — we test against the preview environment before each major wave and ship an updated .app. Because you receive the source in your own git repository, you are never locked to us.
Does it work on Business Central on-premises as well as SaaS?
Yes. The extension is written as standard AL with no base-application modification, so it deploys as a per-tenant extension on SaaS or into your on-premises deployment. Outbound HTTPS access to the Faire API is the only environment requirement; on-premises tenants must have HTTP client calls allowed for the extension.
How are Faire fees and payouts reconciled?
The connector imports the Faire settlement statement, matches each order-level amount to the corresponding posted sales invoice, and creates general journal lines for commission, shipping and adjustment amounts against G/L accounts you nominate on the setup page. The resulting entry nets to the bank receipt, so the payout reconciles without manual journals.
What if our items and Faire options do not line up one-to-one?
That is the normal case and it is handled by an explicit mapping table rather than a naming convention. Faire product and option identifiers map to Business Central Item No. plus Variant Code, including unit-of-measure conversion. Anything unmapped is quarantined in an exception queue with a clear message instead of failing a posting routine silently.
Can we get the data into Power BI or Power Automate?
Yes. The staging, mapping and log tables are exposed through API pages using REST API v2.0 / OData v4, so Power BI can report marketplace margin and Power Automate can trigger on a failed import. Where you use Dataverse, the same tables are available through the standard virtual-table integration.
Related Modules

Egypt E-Invoicing & E-Receipt Connector for Business Central
A per-tenant Business Central AL extension that submits ETA-compliant e-invoices and e-receipts, handles digital signatures and UUIDs, maps GS1/EGS item codes, and tracks real-time clearance — built, installed, and supported by ECOSIRE on your tenant.

eMAG Marketplace Connector for Business Central
A custom-built, per-tenant AL extension that links the eMAG Marketplace (Romania, Bulgaria, Hungary) to Dynamics 365 Business Central — automating order import, offer and price/stock sync, eMAG Fulfilment (FBE) reconciliation, and invoice, VAT and AWB write-back. Built, installed and supported by ECOSIRE on your environment.

Freight Forwarding & Container Management
A custom-built Dynamics 365 Business Central extension that runs your forwarding orders, house/master bills, container and voyage planning, customs paperwork, and carrier settlement inside your own BC tenant. Built, deployed as a per-tenant extension, and supported by ECOSIRE.

Fruugo Connector for Business Central
Sell globally via Fruugo with automated Business Central order, product and inventory sync — built, installed and supported by ECOSIRE as a per-tenant extension on your tenant.
Faire Wholesale Marketplace Connector
An AL extension that connects Faire Wholesale to Dynamics 365 Business Central so brand orders, catalog listings, inventory, shipments and settlement payouts live in one system. Built to order by ECOSIRE for your Business Central version and your posting setup.
- Faire order import into a staging table keyed on the Faire order id, with idempotent re-run so a repeated job never creates duplicate sales orders
- Configurable marketplace status map from Faire order states to Business Central document states (quote, open, released, cancelled) with an exception queue for states a human must decide
- Item and variant resolution from Faire product/option identifiers via a maintained mapping table, with unmapped-SKU quarantine instead of a silent posting failure
- Retailer-to-customer resolution: match on Faire retailer id or email, or auto-create from a configurable customer template with default posting groups and dimensions