Selling on Best Buy Marketplace usually starts as a spreadsheet habit. Someone exports the day's orders from the seller portal, pastes them into a workbook, keys them into Business Central as sales orders, and then works backwards to figure out why available inventory no longer matches the quantity the marketplace is advertising. Every hour of that lag is either an oversell you have to cancel — which hits your seller performance metrics — or stock you are holding back from the channel out of caution. When the settlement report arrives, commission, fulfilment and refund lines have to be reconciled by hand against a bank deposit that never equals the sum of the invoices. Dynamics 365 Business Central out of the box has no notion of a marketplace offer, no place to store a marketplace order id, and no way to reconcile a net payout against gross revenue and deducted fees.

We build a dedicated AL extension for your tenant that treats Best Buy Marketplace as a first-class sales channel inside Business Central. The extension ships as a per-tenant extension for Business Central online (or a signed app for an on-premises deployment), installed through Extension Management with its own permission sets rather than dropped into a modified base application. It adds channel setup tables holding the marketplace API credentials, a channel-to-Customer and channel-to-Location mapping, an item-to-offer mapping table keyed on your Item No./Variant Code against the marketplace SKU, and table extensions on Sales Header, Sales Line and Item so the marketplace order id, offer id, shipment id and channel status live on the document itself and travel through to the posted invoice.

Technically, all traffic to the marketplace API runs through codeunits using HttpClient with retry, throttling and full request/response logging into a channel log table, so a failed call is diagnosable rather than a mystery. Polling and pushes run as Job Queue Entries on schedules you choose — for example order import every fifteen minutes, stock and price sync on a shorter cadence, listing export nightly. Order import maps marketplace order states onto a status your team understands, creates the sales order (or invoice, depending on the flow we agree), and is idempotent: a re-poll of the same marketplace order id will never create a second document. Stock synchronisation is event-driven where it should be — EventSubscriber codeunits hooked to posting and item-ledger events queue a quantity update so a warehouse shipment posted in Business Central is reflected on the offer without waiting for the next full sweep. Shipment confirmation and tracking numbers push back from the posted warehouse shipment or Sales Shipment Header, closing the loop on the marketplace side. Settlement files and fee lines are imported and matched to their orders, then posted as general journal or purchase entries against the accounts and dimensions your controller specifies, so the payout in the bank reconciles to gross revenue minus commission and fees. We also expose the connector's own data through API pages (REST API v2.0 / OData v4) so Power BI, Power Automate and Dataverse can read channel status without screen-scraping.

Because the extension is built to your configuration, we do not hand you a generic binary and wish you luck. Delivery starts with a scoping call where we walk your Best Buy Marketplace account, your Business Central version and localisation, your item and variant structure, your warehouse and fulfilment flow, and your finance team's expectations for how marketplace revenue and fees should land in the chart of accounts. That produces a written scope. Typical delivery is one working week from confirmed scope, depending on how many of the five capability areas you need on day one and how clean the item-to-offer mapping is. We build against the Business Central release wave you are actually running, deploy to a sandbox for UAT with your real catalogue, then install to production with a rollback plan.

After go-live you get the AL source in a git repository you own, technical documentation, a user guide, a training session for the people who will run it daily, and a post-go-live support window during which we fix defects and tune the job queue cadence against real order volume. Business Central ships two major release waves a year; we keep the extension compiling and passing against the release wave you are on, and quote separately for functional changes when Best Buy changes its API or you add a new fulfilment model.