Shopee Marketplace Connector

Key Features

Shopee Open Platform API v2 authentication with partner key signing and automatic refresh-token renewal, credentials held in Isolated Storage rather than plain setup fields

Multi-shop and multi-region registration: several Shopee shops (and regional sites) mapped to one or many Business Central companies, locations and dimension sets

Order import with a configurable status map covering UNPAID, READY_TO_SHIP, PROCESSED, SHIPPED, COMPLETED, CANCELLED, IN_CANCEL and TO_RETURN, driving sales order creation, release and posting

Shopee order SN, package number and buyer username carried on Sales Header and Sales Invoice Header via table extensions, so every posted document traces back to the marketplace record

Near-real-time stock synchronization driven by event subscribers on item ledger entry posting, with per-shop buffer stock and reserved-quantity rules to prevent overselling

Price and promotion push with per-shop price list selection, currency handling and optional guard rails that reject a push outside a configured percentage band

Product listing export with Shopee category, attribute and variation (model/tier) mapping, including a mapping worksheet that flags unmapped mandatory attributes before publish

Shipment confirmation and tracking push-back on warehouse shipment posting, supporting Shopee Logistics pickup/drop-off and self-arranged courier tracking numbers

Settlement and fee reconciliation: escrow and payout detail parsed into a worksheet, each fee type (commission, service, transaction, seller voucher, shipping adjustment) posted to its own G/L account or dimension, balanced to the bank account

Returns and cancellation handling that creates sales credit memos or return orders and reverses reserved stock, keeping the marketplace and ledger positions aligned

All long-running work scheduled through Job Queue Entries with per-task cadence, retry counts and a marketplace activity log page that records request, response and failure reason per call

Rate-limit-aware batching with exponential backoff and a resumable cursor, so a throttled or interrupted sync continues from the last acknowledged page rather than restarting

Custom API pages (REST API v2.0 / OData v4) exposing orders, listings and settlement lines for Power BI, Power Automate and Dataverse virtual tables

Dedicated permission sets separating marketplace operations from finance posting rights, plus telemetry signals emitted to Application Insights for monitoring sync health

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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

What you get

Installable AL extension source, built and targeted at your exact Business Central version, localization and deployment model (SaaS per-tenant extension or on-premises signed app)

Installation and configuration performed on your sandbox and production environments, including Shopee app registration guidance, shop authorization and Job Queue setup

Technical documentation: object ID ranges, table/page extension inventory, event subscribers, API page endpoints, permission sets and the fee-to-G/L posting map

User guide plus a live training session for your operations and finance teams covering order flow, listing publish, shipment push-back and settlement reconciliation

UAT on a staging environment with a real Shopee order and a real settlement file processed end to end, signed off before production publish

Documented rollback plan and a tested uninstall/downgrade path, so a production publish can be reversed without data loss

Post-go-live support window with defect fixes on the delivered scope and assistance with the first live settlement cycle

Full git repository handover with commit history, branch strategy and build pipeline notes — the source code is yours to keep and extend

Who this is for

Shopee seller operations manager

Runs daily despatch across one or several Shopee shops and is judged on late-shipment and cancellation rates. Needs orders in Business Central within minutes, tracking numbers pushed back automatically on shipment posting, and a single activity log to check when a sync did not run — not a spreadsheet export at the end of the day.

Finance controller / accountant

Owns the month-end close and has to explain why the Shopee payout does not match recorded sales. Needs each fee type posted to its own G/L account or dimension, a settlement worksheet that balances to the bank line, and an audit trail from Shopee order SN to posted invoice.

IT manager or Business Central partner consultant

Responsible for the tenant and wary of middleware that owns the data. Wants an AL extension deployed inside Business Central with its own permission sets, Job Queue entries, telemetry and source code in a git repository they control, upgradeable across release waves.

Inventory and supply planner

Sells the same SKUs across Shopee, retail and other channels from shared stock. Needs marketplace availability driven by real item ledger quantities with per-shop buffer rules, so a Shopee sale never commits stock already promised to another channel.

How Shopee Marketplace Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Shopee order and status handling	Full Shopee status map driving sales order creation, release and posting, with the order SN on every document	Achievable, but your team designs and tests the whole status model from scratch	Usually a fixed status map you configure rather than change	No marketplace concept at all — orders are re-keyed or imported from a file
Stock synchronization	Event-subscriber-driven from item ledger postings, with per-shop buffer and reservation rules	Depends entirely on the developer's design; batch-only is the common shortcut	Typically scheduled batch at a vendor-set interval	None — Business Central has no channel to publish availability to
Settlement and fee reconciliation	Payout parsed into a worksheet, each fee type to your nominated G/L account or dimension, balanced to bank	Often descoped as too fiddly, leaving finance with a manual difference entry	Frequently a single lump fee line, or omitted from the product entirely	Manual journal built from the Seller Centre report each month
Listing export and attribute mapping	Category, attribute and variation mapping with unmapped mandatory attributes flagged before publish	Buildable, but attribute-tree handling is where DIY projects usually overrun	Varies widely; variation and regional attribute coverage is a common gap	Listings are created and maintained by hand in Seller Centre
Ownership of the code	You get the AL source and the git repository — extend or maintain it with anyone	You own it, and you also own every future fix and release-wave test	Vendor-owned binary; you depend on their roadmap for changes	Not applicable
Ongoing cost model	One-time build, then an optional support and maintenance agreement	Developer time up front, then unbudgeted maintenance whenever an API changes	Recurring per-user or per-transaction subscription for as long as you use it	No licence cost, paid instead in staff hours re-keying and reconciling
Fit to your process	Built to your fulfilment model, localization and fee posting map, agreed at scoping	Fully bespoke, at the cost of designing every decision yourself	You adapt your process to the app's assumptions	Process is whatever your spreadsheets currently enforce
Time to live	Typically 2-4 weeks from confirmed scope, including sandbox UAT and rollback plan	Commonly several months once discovery, build, test and rework are counted	Install in days, then weeks of workaround-building for the gaps	Available immediately, because nothing is automated

Frequently Asked Questions about Shopee Marketplace Connector

How long does delivery take, and is this something I can download today?

No — this is build-to-order, not an existing Microsoft AppSource download. We build the extension for your tenant after you request a quotation. Typical delivery is two to four weeks from confirmed scope, covering development, sandbox deployment, UAT with a real order and a real settlement file, and production publish. Scope complexity moves that: a single shop with a clean SKU structure lands at the shorter end; multiple regional sites, variation-heavy listings or a bespoke fee posting map sits at the longer end. We give you a dated plan after the scoping call, before any commitment.

Which Business Central versions and deployment models do you support?

We build against current Business Central release waves and target the exact version and localization you run. For Business Central online we deliver a per-tenant extension published to your environment; for on-premises and hybrid we deliver a signed app package with deployment instructions. If you are mid-upgrade, tell us at scoping and we will target the version you will be on at go-live and note any objects affected by the upgrade.

What happens with support and updates after go-live?

Every engagement includes a post-go-live support window for defect fixes on the delivered scope, plus help through your first live settlement cycle. Beyond that we offer an ongoing support and maintenance agreement covering Shopee Open Platform API changes, Business Central release-wave compatibility testing and enhancement work. Because you receive the full AL source and the git repository, you are never locked in — your own team or another partner can maintain it if you prefer.

How does settlement reconciliation actually work?

We pull escrow and payout detail from the Shopee API into a settlement worksheet in Business Central. Each line is split into its components — gross sale value, commission fee, service fee, transaction fee, seller-funded voucher, shipping adjustment, coin cashback — and mapped to the G/L accounts or dimensions you nominate during scoping. The worksheet balances to the bank account line, so the posted journal matches the amount that actually hit your bank and month-end no longer needs a manual difference entry.

Will this stop me overselling shared stock?

That is the design intent. Availability pushed to Shopee is derived from real item ledger quantities in Business Central, with per-shop buffer stock and reservation rules you configure, and it is triggered by event subscribers on posting rather than only by a scheduled batch. It is honest to say no connector removes the physical latency of a marketplace API accepting an update, so we set the buffer with you based on your order velocity — the buffer is a deliberate setting, not a workaround.

Do I need middleware, an iPaaS subscription, or a separate database?

No. The connector is an AL extension running inside Business Central and calling the Shopee Open Platform API directly. There is no third-party integration platform in the path, no external database holding your orders, and no per-transaction fee to anyone but Shopee. Your only external dependency is the Shopee developer app registration, which we help you set up.

Can we report on marketplace data in Power BI or use it in Power Automate?

Yes. Marketplace orders, listings and settlement lines are exposed through custom API pages using REST API v2.0 / OData v4, which Power BI, Power Automate and Dataverse virtual tables consume natively. You do not need a report developer to build a Shopee margin or fee-analysis dashboard, and you can trigger Power Automate flows on marketplace events without touching the AL code.