D2 Technology · Commerce Control

A decision layer for Orders, Settlement, Ads, COGS and exceptions.

Commerce Control turns fragmented TikTok Shop and Shopee source data into a traceable view of source coverage, SKU mapping, reconciliation, P&L, payout and data-quality exceptions.

  • Smart Upload
  • Orders ↔ Settlement
  • SKU Master
  • Exception-first reporting

Direct answer

What is Commerce Control Dashboard?

It is the technology layer that lets operators see business outcomes, cash settlement and data quality without treating them as the same thing. Sources are preserved, mapped into a canonical model and used for profitability only when evidence is sufficient; missing evidence stays visible as an exception.

Operating problem

What this service is designed to fix

D2 starts from the operating failure mode before choosing tactics, tools or output volume.

  • GMV, payout, Ads and COGS live in disconnected sources.
  • Inconsistent SKU names prevent product-level reporting.
  • Sales-period P&L is mixed with settlement/cash timing.
  • Dashboards hide missing cost or unmapped orders behind complete-looking totals.

Scope

Core execution scope

Final scope depends on the brand, platform access, data coverage and ownership agreed during onboarding.

  • Smart Upload and source coverage detection
  • Raw-source preservation and canonical normalization
  • SKU Master / canonical SKU mapping
  • Orders ↔ Settlement reconciliation
  • Ads, COGS and contribution reporting
  • Payout visibility and exception queue

Operating loop

How D2 turns the scope into a repeatable cadence

The workflow needs explicit inputs, owners, review points and a rule for what changes next.

  • Identify sources and validate coverage before calculating KPIs.
  • Normalize fields and map identifiers/SKUs into a canonical model.
  • Reconcile Orders to Settlement using stable keys and period rules.
  • Join Ads, COGS and variable costs when evidence is sufficient.
  • Turn exceptions and variances into an operator action queue.

Evidence

Data and proof used to support decisions

D2 separates source evidence from assumptions and keeps missing or unresolved inputs visible as exceptions.

  • Orders
  • Settlement
  • Ads
  • COGS
  • SKU Master
  • Illustrative data is labeled and never presented as a client performance claim

Measurement

Metrics are read in business context

No single metric proves success. D2 connects operating signals to revenue, cost, contribution and the next decision.

  • Gross/valid revenue and payout
  • Platform fee and Ads ratio
  • COGS / contribution margin
  • Mapping/reconciliation coverage
  • Exception count and unresolved value
  • Reporting latency / source freshness

Boundaries

What needs to be explicit before execution starts

Clear boundaries protect measurement quality and prevent one service from being treated as every e-commerce task.

  • No invented cost or mapping when evidence is missing.
  • Not a default replacement for accounting or tax systems.
  • API/real-time integration is used only when source reliability and decision value justify it.

Engagement

Scope follows source coverage and reporting requirements, not a fixed public price table.

D2 defines marketplaces, file/API sources, SKU mapping, cost model, reporting cadence, automation and support requirements before issuing a proposal.

Contact for proposal

FAQ

Frequently asked questions

What is Commerce Control Dashboard for?+

Commerce Control connects Orders, Settlement, Ads, COGS and the SKU Master into one operating view for revenue, payout, contribution and exceptions instead of relying on isolated platform dashboards.

Does it require a real-time API connection?+

No. Smart Upload and controlled file ingest can be better when APIs are unreliable, evidence needs auditing or daily freshness is sufficient for the decision cadence. APIs are used when business value and reliability justify them.

Does the dashboard estimate COGS automatically?+

No. COGS needs a brand-confirmed cost source. Unmapped SKUs, missing costs and unreconciled settlement records remain visible as exceptions rather than being filled with convenient assumptions.

Are Orders and Settlement combined into one number?+

No. Orders support sales-period P&L while Settlement supports payout and realized deductions. The system reconciles both layers while preserving their different business meaning and timestamps.

Does Commerce Control replace accounting software?+

Not by default. It is a commerce intelligence and decision layer for operations and profitability, not a statutory accounting or tax system.

How is pricing determined?+

The website does not publish a fixed price table. The proposal depends on marketplaces, source coverage, mapping complexity, reporting scope, automation requirements and the support/ownership required.

Read Commerce Profitability Insights