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 two to four weeks 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.