Tokopedia Marketplace Connector

Key Features

Order import job queue entry that pulls new and changed Tokopedia orders and creates sales orders idempotently, keyed on the marketplace order ID so a re-run never duplicates a document

Configurable marketplace status map (Tokopedia order state to Business Central document state) held in a setup table, so status semantics change without a code deployment

SKU mapping table linking Tokopedia listing SKUs to Item No. and Variant Code, with unit-of-measure translation and a fallback rule that parks unmapped orders for review instead of failing silently

Availability publisher driven by event subscribers on item ledger entry posting and sales line insert, so a stock movement anywhere in Business Central flags the listing for the next push

Price synchronisation reading from a nominated sales price list, applying a marketplace-specific markup or price group, and pushing only changed values to keep API call volume down

Product listing export mapping item categories and item attributes to Tokopedia category and attribute values, including image URLs and description fields

Shipment confirmation push fired from posted sales shipment and warehouse shipment, sending carrier and tracking number back to the marketplace and advancing the order state

Settlement import that parses the Tokopedia payout report and builds a general journal batch splitting revenue, commission, service fees, promotion contributions and adjustments to mapped G/L accounts

Fee-type to G/L-account mapping table so finance controls the chart of accounts posture without developer involvement, with dimension defaulting per marketplace

Isolated-storage credential store with OAuth token refresh in a dedicated codeunit — no secrets held in table fields and none rendered on the setup page

Integration log table capturing full request and response, with exponential-backoff retry, a dead-letter view and an operator retry action that needs no developer

API pages (REST API v2.0 / OData v4) exposing mapping, order-link and integration-log tables for Power BI dashboards, Power Automate alerts and Dataverse virtual tables

Permission sets for marketplace operator, accountant and administrator roles, plus Application Insights telemetry for job queue failures and API error rates

Multi-shop support with per-shop setup records, so several Tokopedia storefronts feed one Business Central company with distinct customer, location and dimension defaults

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

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 2 to 4 weeks 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.

What you get

Complete AL extension source code, built and tested against your specific Business Central version and deployment type (SaaS per-tenant extension or on-premises signed app)

Installation and configuration on your sandbox and production environments, including setup table population, job queue entry scheduling and permission set assignment

Technical documentation: object inventory with IDs, integration architecture, API endpoints consumed, event subscribers used, and the extension upgrade path

End-user guide covering order review, mapping maintenance, settlement import and error handling, plus a live training session for your operations and finance users

User acceptance testing on a staging environment using your own catalogue, real Tokopedia orders and a real settlement report, with a documented rollback plan before the production publish

Post-go-live support window for defect fixes within the delivered scope, with a named engineer and an agreed response path

Git repository handover with full commit history, branch strategy and build pipeline configuration, so you or another partner can maintain the extension

Mapping workbook and RapidStart configuration package for SKU, status and fee-account mappings, so the configuration is reproducible across environments

Who this is for

Tokopedia seller operations manager

Runs daily order flow across Tokopedia and other channels, currently re-keying marketplace orders into Business Central and reconciling stock by hand at day end. Needs orders to land as sales orders automatically, marketplace status visible on the order card, and availability pushed back fast enough that overselling stops.

Finance manager or controller

Owns the general ledger and has to explain why the Tokopedia payout in the bank does not match invoiced revenue. Needs commission, service fees and promotion contributions posted to nominated G/L accounts with dimensions, so the payout reconciles line by line and per-channel margin becomes reportable.

Business Central partner or internal IT lead

Responsible for the environment, extension governance and upgrade readiness. Needs a properly structured AL extension with owned object IDs, permission sets, telemetry and documented event subscribers — not ad-hoc customisations that break at the next release wave.

E-commerce or channel manager

Decides what is listed, at what price, on which marketplace. Needs listings exported from Business Central item data with correct category and attribute mapping, and price changes reaching the marketplace without a manual Seller Center session.

How Tokopedia Marketplace Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Fit to your order and settlement process	Built to your scoped rules — your status map, your fee accounts, your variant structure	Fits exactly, if the spec is right and the developer knows both Business Central and Tokopedia	Fits the vendor's assumed process; you adapt your operations to the app	No Tokopedia concept exists; the process is a browser tab and manual data entry
Source code and ownership	Full AL source plus the git repository handed over at delivery	You own it, and you own every future fix for it	Closed binary from AppSource; you file a support ticket and wait	Base application only; no marketplace objects to own
Time to a working system	2 to 4 weeks from confirmed scope, including sandbox UAT	Typically months once hiring, spec, build and test are counted honestly	Installs in minutes, then weeks of configuration and workarounds	Available today, but the work stays manual forever
Settlement and fee reconciliation	Payout lines matched to orders and posted to mapped G/L accounts with dimensions	Achievable, but it is the part in-house builds most often run out of budget before finishing	Often a summary journal or CSV export; per-order matching is a paid add-on	A lump-sum bank receipt with no marketplace breakdown
Upgrade safety across release waves	Supported extension patterns only; release wave compatibility testing offered under support	Depends entirely on the developer's discipline with events and object ownership	The vendor decides when to certify a wave; you wait for their schedule	Always current — because nothing marketplace-specific exists in it
Error handling and diagnosability	Full request/response logging, backoff retry, dead-letter view and an operator retry action	Usually the last feature built and the first one cut	A vendor log you can read but not extend or query from your own reports	No integration, so no integration errors — and no automation either
Power Platform and reporting access	API pages (REST API v2.0 / OData v4) over mapping and log tables for Power BI, Power Automate, Dataverse	Possible, though frequently skipped because it is not the headline requirement	Whatever endpoints the vendor chose to expose, if any	Standard Business Central APIs only; nothing marketplace-related to query
Commercial model	Fixed price against a written scope, plus an optional ongoing support agreement	Day rates, with schedule risk carried by you	Per-user or per-order subscription that grows as your volume grows	Included in your Business Central licence; the cost shows up as operations headcount

Frequently Asked Questions about Tokopedia Marketplace Connector

How long does delivery take?

This is a build-to-order extension, so nothing is pre-packaged for instant download. Typical delivery is 2 to 4 weeks from confirmed scope. The clock starts once we have agreed shop count, mapping rules, the settlement posting model, your Business Central version and deployment type, and you have provided sandbox access and Tokopedia API credentials. Wider scope — multiple companies, several marketplaces, unusual variant structures — extends the timeline, and we tell you that before you commit, not after.

What support and updates do I get after go-live?

Every build includes a post-go-live support window during which we fix defects in what we delivered at no extra cost. Beyond that we offer an ongoing support and maintenance agreement covering Business Central release wave compatibility testing, Tokopedia API changes, 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 the extension if you prefer.

Does this work on Business Central SaaS, on-premises, or both?

Both. For a SaaS environment we deliver a per-tenant extension published through the admin centre using only supported AL patterns — no base table modifications, no code customisation of base objects, so your environment stays upgrade-safe. For on-premises or hosted deployments we deliver a signed app and can additionally use .NET interop or file-system access where your scenario needs it. We build against your specific version and confirm compatibility with the current supported release waves during scoping.

How does the settlement reconciliation actually post?

The import reads the Tokopedia payout report and matches each line back to the sales order it came from using the marketplace order ID stored on the document. It then creates a general journal or cash receipt journal batch where gross sale value, commission, service fees, promotion contributions and adjustments each post to the G/L account you mapped in setup, with your nominated dimensions. You review and post the batch — the extension does not post to the ledger unattended unless you explicitly ask for that behaviour. The result is a payout you can reconcile line by line against the bank statement.

What happens when a Tokopedia SKU does not match anything in Business Central?

The order is neither lost nor force-created against the wrong item. It is held in a staging table with a clear mapping-error status and surfaced on an exception page where an operator can create the mapping and re-drive the import with one action. The same pattern applies to failed API calls: they are logged with full request and response, retried with exponential backoff, and left in a dead-letter view with a retry action rather than disappearing into a job queue error message.

Can I connect this to Power BI or Power Automate?

Yes. The extension exposes its mapping, order-link and integration-log tables through API pages built on REST API v2.0 / OData v4, so Power BI can report on channel margin and integration health, Power Automate can raise an alert when the import job fails or an order parks on a mapping error, and Dataverse can surface the data as virtual tables. We wire up an agreed set of endpoints as part of the build and document them in the technical handover.

Is the listed price final?

The listed figure is an indicative starting point for a standard single-shop build. Final pricing comes out of the scoping call, because the variables that move it are real: how many Tokopedia shops, whether you need multi-company or multi-currency, how complex your variant and attribute structure is, whether settlement posts per order or per payout, and how much historic data or reconciliation is in scope. We then quote a fixed price against a written scope, so there are no surprises mid-build.