Selling on Shopee, Lazada, TikTok Shop, Tokopedia and their regional siblings means running five different order lifecycles at once. Each marketplace has its own order states, its own cancellation window, its own escrow-and-payout cycle, and its own fee schedule — commission, service fee, affiliate fee, free-shipping subsidy, coin cashback — all deducted before the money lands. Dynamics 365 Business Central has an excellent sales order, inventory and finance core, but it has no concept of a marketplace channel. Out of the box you get one availability figure, one sales order flow, no per-channel stock reservation, and no way to tie a single bank statement line to the 180 orders and 640 fee lines that produced it. Most sellers bridge that gap with spreadsheets and a bookkeeper, and discover the size of the gap only when the trial balance stops tying out.

The Southeast Asia Marketplace Pack is an AL extension we build for your Business Central tenant. It adds a Marketplace Channel setup table plus channel-scoped connection records, and a normalized Marketplace Order staging layer that every channel connector writes into before it becomes a Business Central Sales Order. Ingestion runs on job queue entries — one recurring codeunit per channel, with a watermark cursor, exponential back-off on HTTP 429, and idempotent upsert keyed on channel code plus external order id, so a replayed webhook or an overlapping poll never creates a duplicate order. Item mapping lives in table extensions on Item and Item Variant (channel SKU, channel item id, listing status) so your existing item numbers stay canonical. Table extensions on Sales Header and Sales Invoice Header carry the channel code, external order number and payout batch, and those fields flow through posting into the customer ledger and value entries — which is what makes channel profitability a real Business Central analysis rather than a report bolted on the side.

Stock is where multi-marketplace sellers actually lose money, so the pack treats it as a first-class problem. A Channel Stock Buffer table holds per-location, per-channel reserve quantity and a publish rule (fixed buffer, percentage, or priority waterfall across channels). A codeunit recalculates publishable quantity from item availability by location, net of the buffer and existing reservations, and pushes stock updates to each channel on its own cadence — because Shopee and Lazada throttle differently and a single global push simply gets you rate-limited. Event subscribers on OnAfterPostSalesDoc and the warehouse shipment events trigger a targeted re-push rather than a full catalogue sync, so an oversell window is measured in seconds instead of "until the nightly batch".

Tax and money handling are localized rather than generic. Invoice generation respects the Indonesian, Malaysian, Thai, Philippine, Vietnamese or Singaporean localization you actually run — VAT/GST/SST posting groups, tax-inclusive marketplace pricing unwound to net plus tax, and the reference fields your local e-invoice regime requires. Marketplace-collected tax posts to a separate account so you can prove what the platform withheld. Payout reconciliation imports each settlement statement into a Marketplace Payout header with fee lines mapped to G/L accounts through a configurable fee-type table, matches the order lines back to the posted sales invoices, and produces a payment journal that clears receivables and books every commission, subsidy and adjustment. Unmatched lines land on an exception page instead of quietly rounding into a suspense account. Returns come back through the same spine: a channel return creates a Sales Return Order or Credit Memo, restores the buffer, and reverses the associated fees where the marketplace refunded them. Everything is exposed through API pages (REST API v2.0 / OData v4) with dedicated permission sets, so Power BI, Power Automate and Dataverse-based flows read the same data your accountants close on.

This is build-to-order, not a download. You request a quotation, we run a scoping call, and we confirm which marketplaces, which country localizations, which Business Central release wave, and whether you are on SaaS (per-tenant extension or AppSource-track app) or on-premises. From confirmed scope, typical delivery is two to four weeks: we build against your version, deploy to a sandbox for UAT with your real order and settlement files, then install into production with a rollback plan. You receive the AL source code, a git repository handover, technical and user documentation, a training session, and a post-go-live support window. Nothing is pre-built and nothing is instant — the point is that the extension fits your channel mix and your chart of accounts on day one.