Selling on Carrefour Marketplace usually starts as a spreadsheet habit. Someone exports the Carrefour seller portal order list every morning, retypes it into Dynamics 365 Business Central as sales orders, guesses which item number matches which Carrefour SKU, and then re-uploads a stock file so the marketplace stops selling units that shipped yesterday. Business Central has no native concept of a marketplace offer, a marketplace order status, a marketplace commission line or a marketplace payout statement — its sales order, item and customer ledger tables assume you invoice the buyer. On Carrefour you do not: the marketplace collects, deducts commission and fees, and remits a net settlement. That mismatch is where the manual work, the oversells and the unreconciled bank lines come from.

We build a Carrefour Marketplace connector as a Business Central AL extension — delivered as a per-tenant extension for SaaS, or as an app you deploy on-premises — that owns the whole exchange. A Carrefour Setup page holds the seller credentials, shop ID, base URL and per-environment toggles, with secrets stored via Isolated Storage rather than plain setup fields. Dedicated tables hold the offer mapping (Business Central item and variant to Carrefour offer SKU), the order staging buffer and the settlement lines, so nothing is written straight into your posted documents without an audit trail. Codeunits handle authentication, paging, retries with exponential backoff and idempotency keys, and every inbound and outbound call is written to a Carrefour API Log table you can open from the role centre when something looks wrong.

Technically, the sync runs on Job Queue Entries rather than a user pressing a button. One entry pulls new and updated Carrefour orders on your chosen cadence, matches the marketplace SKU to an item through the mapping table, creates the sales order against a dedicated marketplace customer with the correct shipping address and marketplace order reference, and maps the Carrefour order state (waiting acceptance, shipping, shipped, cancelled, refunded) onto Business Central document status plus a status field you can filter and report on. A second entry pushes availability: an event subscriber on item ledger and reservation changes marks affected offers dirty, and the push job sends only the deltas, so a thousand-SKU catalogue does not become a thousand API calls per hour. Shipment confirmation runs the other way — posting a warehouse shipment or a sales shipment raises an event that queues the carrier, tracking number and shipped quantity back to Carrefour, which is what releases your payment clock. Settlement files and fee lines are imported into a reconciliation worksheet that proposes general journal or purchase invoice lines for commission, fulfilment and refund amounts, so the bank receipt for a payout period actually closes against documents instead of sitting in suspense. Everything is exposed through API Pages on REST API v2.0 / OData v4 where you need Power BI, Power Automate or a Dataverse virtual table over the same data, and shipped with purpose-built permission sets so a warehouse user can confirm shipments without seeing settlement figures.

This is build-to-order, not an AppSource download. Nothing installs today. We start with a scoping call where we look at your actual Carrefour seller account, the countries and shops you sell in, your item and variant structure, how you post marketplace revenue in your chart of accounts, and which Business Central version and deployment you run. That produces a fixed written scope: mapped fields, sync frequencies, status mapping table, posting rules and acceptance tests. Typical delivery is one working week from confirmed scope, longer only if you want fulfilment-by-marketplace flows, multi-country shops or multi-company consolidation in the first release.

We build against your Business Central version and current release wave, test on a sandbox copy of your database with your real catalogue, run UAT with your team against a written test script, and only then deploy to production with a rollback plan. You get the AL source, the git repository, the technical documentation, a user guide and a training session, plus a post-go-live support window during which we fix defects in what we built. Because you hold the source, you are never locked out of your own integration.