Selling on Tokopedia while running Dynamics 365 Business Central usually means someone in operations lives inside the Seller Center all day. Orders are keyed into Business Central by hand from a browser tab, stock is corrected after the fact when a customer orders something already sold on another channel, and the Tokopedia payout that lands in the bank is a single lump sum nobody can tie back to individual sales orders. Business Central has excellent sales, inventory and finance foundations — sales order processing, item availability, warehouse shipments, bank reconciliation — but it ships with no knowledge of Tokopedia's order lifecycle, its logistics statuses, or the commission, service and promotion fees Tokopedia deducts before it pays you. There is no standard field to hold a Tokopedia order ID, no place for a marketplace SKU that differs from your item number, and nothing that turns a settlement report into a balanced set of entries.

ECOSIRE builds a Business Central extension in AL that closes that gap. It is delivered as a per-tenant extension for a SaaS environment, or as a signed app for an on-premises or hosted deployment, and it targets the current supported release waves. The extension adds its own setup table and setup page for Tokopedia credentials and shop selection, staging tables for raw marketplace payloads, and mapping tables holding the item-to-listing relationship, the marketplace-status to document-status map, and the fee-type to G/L-account map. Table and page extensions put Tokopedia identifiers on Sales Header, Sales Line, Item and Customer so the marketplace origin of every document is visible on the card the user already works in — no separate screen to learn. All API traffic runs through dedicated codeunits using HttpClient with an isolated-storage token store, retry with exponential backoff, and full request/response logging so an integration failure is diagnosable without reproducing it.

The moving parts run on job queue entries, so they behave the way the rest of Business Central does. One recurring job pulls new and changed Tokopedia orders, resolves the buyer to a customer (or to a shared marketplace customer, depending on how you want AR to look), maps each marketplace SKU to an item or item variant, and creates a sales order with shipping address, shipping method and marketplace status stamped on it — idempotently, keyed on the marketplace order ID, so a re-run never duplicates a document. A second job publishes availability and price: an event subscriber on item ledger entry posting and on sales line insert flags affected items, and the publisher pushes calculated available quantity to the listing so overselling is caught at the source rather than at packing. Shipment confirmation runs the other way — when a sales shipment or warehouse shipment is posted, the extension pushes carrier and tracking number back to Tokopedia and advances the marketplace order state.

Settlement import reads the payout report, matches each line to its sales order, and creates a general journal or cash receipt journal batch where the sale, the commission, the service fee and the promotion contribution each hit the account you nominated, with the dimensions you nominated — leaving a payout you can actually reconcile against the bank statement. Every object ships with permission sets so the marketplace operator, the accountant and the administrator each get the access their role needs, telemetry is emitted to Application Insights for job failures and API error rates, and API pages (REST API v2.0 / OData v4) expose the mapping and log tables so Power Automate, Power BI or a Dataverse flow can read integration health without a separate database connection.

This is a build-to-order product, not an AppSource download. Nothing is installed until you request a quotation and we agree the scope, because the details that matter — which Tokopedia shops, whether you post per order or per payout, how variants map to your item structure, SaaS or on-premises, and which release wave you are on — change the build. Typical delivery is one working week from confirmed scope. We build against your Business Central version, deploy to a sandbox first, run user acceptance testing with your own catalogue and a real settlement report, and only then publish to production with a rollback plan in hand. You receive the AL source, the repository, technical documentation and a user guide, plus a training session and a post-go-live support window during which we fix defects in what we delivered.