Shopee sellers usually run two disconnected systems. Orders arrive in Seller Centre and get re-keyed into Dynamics 365 Business Central hours or days later, so the inventory Business Central reports is never the inventory Shopee is selling from. Overselling follows, then cancellations, then a hit to your shop's fulfilment rating. At month end, the payout that lands in the bank never equals the sum of the sales orders, because Shopee has already deducted commission, service fees, transaction fees, seller-funded voucher subsidies, shipping adjustments and coin cashback — and none of that is in your ledger.

Business Central handles the ERP side of this well, but it has no notion of a marketplace. Out of the box there is no Shopee order status model, no listing entity to map SKUs against Shopee's category and attribute tree, no shipment push-back, and nothing that turns a settlement payout into a balanced journal. Standard integration options force you into flat-file imports or a generic middleware layer that owns your data and hides the mapping logic. Neither gives you an auditable link from a Shopee order number to a posted sales invoice and a bank reconciliation line.

We build a dedicated AL extension for your tenant. It authenticates against the Shopee Open Platform API using the shop-level partner key and refresh-token flow, and stores credentials in Isolated Storage rather than plain setup fields. New Shopee tables hold shop registrations, SKU-to-item mappings, listing state and the raw settlement lines; table and page extensions add marketplace fields to Item, Sales Header and Sales Line; and codeunits do the work, invoked from Job Queue Entries so polling cadence is configurable per shop rather than hard-coded. Order import maps Shopee order status (UNPAID, READY_TO_SHIP, SHIPPED, COMPLETED, CANCELLED, IN_CANCEL, TO_RETURN) onto your document flow, so a paid order becomes a sales order and a completed order becomes a posted invoice, with the Shopee order SN carried on the document for traceability. Stock and price synchronization runs off event subscribers on item ledger and price changes, so a warehouse posting in Business Central updates the Shopee listing without waiting for the next batch. Shipment confirmation and tracking numbers are pushed back when the warehouse ships, which is what keeps your shop inside Shopee's despatch SLA. Settlement files are parsed line by line into a reconciliation worksheet: gross sale, each fee type to its own G/L account or dimension, and a balancing line to the bank account, so the payout ties out exactly.

Everything is exposed through the standard platform. Custom API pages (REST API v2.0 / OData v4) publish marketplace order, listing and settlement data for Power BI, Power Automate or Dataverse virtual tables, so operations reporting does not require a report developer. Permission sets separate the marketplace operator role from the finance role that posts settlement journals. The extension is built for current Business Central release waves and delivered either as a per-tenant extension for SaaS or as a signed app for on-premises and hybrid deployments — we target the exact version and localization you are on, including your country's VAT/GST posting setup.

This is build-to-order, not an AppSource download. You book a short scoping call, we confirm which Shopee regional sites and shops are in play, your SKU structure, your fulfilment model (Shopee Logistics versus your own courier), how you want fees posted, and which Business Central version and localization you run. From confirmed scope, typical delivery is one working week: we develop against your requirements, deploy to your sandbox for UAT, run a real order and a real settlement file end to end with your team, then publish to production with a documented rollback. You receive the AL source, a git repository handover, install and configuration documentation, a user guide, a training session and a post-go-live support window — the code is yours, and nothing is locked behind a subscription you cannot leave.