Spreadsheet consolidation is fragile
The team is manually combining recurring exports, changing formulas or rebuilding the same management report every cycle.
Commerce Automation & Reporting
Build one commerce control layer before adding more dashboards.
D2 Group maps, normalizes and reconciles TikTok Shop, Shopee, Ads, platform fees, settlement and cost data before calculating recognized revenue, contribution and the metrics teams use for operating decisions. The objective is not another dashboard. It is a traceable source-of-truth layer with visible exceptions.
Direct answer
What does commerce automation and reporting actually control?
It creates a controlled layer between raw marketplace data and business decisions. D2 identifies which source owns each number, standardizes recurring data, reconciles orders and settlement populations, applies documented fee and cost formulas, surfaces exceptions, then produces reporting that keeps GMV, recognized revenue, payout and contribution as separate questions.
When this service fits
Start when reporting itself has become an operating constraint.
Marketplace numbers disagree
Orders, Ads, fees, settlement and payout views do not reconcile, so teams cannot explain why GMV, cash received and contribution differ.
Management needs contribution visibility
Topline sales are visible, but platform fees, Ads, COGS, packaging, creator costs or other agreed inputs are not consistently connected to the same revenue population.
The dashboard lacks source control
A reporting interface already exists, but the team cannot trace definitions, exceptions, missing inputs or which source owns each number.
Reporting control layer
Clean charts are not enough when the underlying numbers disagree.
D2 treats reporting as a data-control problem first. Source definitions, formulas and exceptions must stay visible before the system optimizes presentation or automation.
Source mapping
Define which marketplace, Ads, settlement and cost source owns each field before any reporting layer combines the data.
Normalization
Standardize dates, order IDs, status logic, SKU keys, currencies and recurring file structures into one controlled model.
Reconciliation
Compare order, settlement, Ads and cost populations so duplicates, timing gaps, missing records and status mismatches remain visible.
Formula layer
Apply documented definitions for recognized revenue, platform fees, Ads ratio, COGS, contribution and other agreed metrics.
Exception visibility
Flag missing inputs, malformed files, unmatched orders and inconsistent totals instead of silently producing an authoritative-looking dashboard.
Workflow automation
Automate intake, validation, transformation, alerts and delivery only where automation improves reliability without hiding failure paths.
Decision output
A reporting cycle should end in a confidence decision, not another export.
Trust
The source population, formula and period reconcile well enough for the metric to support a business decision.
Investigate
An exception, timing gap or unexplained variance needs source-level review before the metric is treated as reliable.
Correct
A mapping, formula, data-quality or workflow issue is identified and the reporting logic should be fixed before the next cycle.
Act
Validated reporting is translated into an operating decision such as Scale, Hold, Fix or Retest on the relevant commerce layer.
Connected commerce
Reporting should connect to the operating layer that can act on the result.
Operating cadence
Map, normalize, reconcile, calculate, review and act.
Map sources
Identify each source file, API, reporting period, key field and commercial definition before combining anything.
Normalize
Standardize dates, order identifiers, statuses, SKU keys, currencies and cost fields into a common reporting model.
Reconcile
Compare order, settlement, Ads and cost populations; surface missing records, duplicates, timing gaps and status mismatches.
Calculate
Apply documented formulas for recognized revenue, fees, Ads ratio, COGS, contribution and the agreed decision metrics.
Review & act
Turn validated metrics and exceptions into a Trust, Investigate, Correct or business-action decision, then improve the logic as source reality changes.
Measurement model
GMV, settlement and contribution are different questions.
D2 keeps commercial layers separate so the team can ask the right question of each number. A clean reporting model should explain which population and formula produced the metric before it is used to make a growth decision.
Revenue integrity
GMV, recognized revenue and order populations mapped to explicit status and period definitions.
Cost visibility
Platform fees, Ads, COGS, packaging and other agreed variable costs kept in one comparable model.
Settlement clarity
Marketplace payout data separated from sales performance so cash timing is not confused with contribution.
Contribution
A documented operating view of what remains after the variable costs included in the agreed formula.
Ownership boundary
D2 can own the reporting system without becoming the source of business truth.
Client retains
Marketplace and advertising accounts
Raw business data and exports
Product cost and inventory truth
Final accounting / finance policy
Commercial approvals and access control
D2 owns in scope
Source mapping and reporting model
Normalization and reconciliation logic
Documented operating formulas
Exception visibility and recurring checks
Automation and reporting delivery within scope
Contribution reporting is an operating-management model unless the client separately validates the definitions for statutory accounting or tax use. D2 does not replace the client's finance policy, accounting records or legal responsibility.
Automation model
Automate repeatable steps without automating uncertainty.
D2 can use n8n, APIs, webhooks or controlled file workflows to reduce repetitive consolidation. Automation is added after source and formula logic are explicit, with validation, duplicate prevention and exception paths kept visible so a failed or incomplete source does not silently produce a trusted-looking report.
Selected reporting work
Proof should show where the numbers came from and what decision changed.
Reporting case
Mì Cay Dozin
D2 reconciled Orders, Ads, platform fees, COGS and SKU mix to explain why topline revenue did not equal healthy contribution economics.
Open case studyReporting case
Wins Food
Multi-SKU revenue, fees, Ads, product cost and packaging were brought into one repeatable reporting logic for shorter-cycle decisions.
Open case studyReporting case
Financial Reporting & Reconciliation Automation
A system case focused on repeatable financial data processing, reconciliation logic and exception visibility rather than manual spreadsheet consolidation.
Open case studyCommerce reporting knowledge
Understand the definitions before trusting the output.
TikTok Shop Report Files
Understand why order detail, pending settlement and settled data answer different reporting questions and should not be merged blindly.
Read insightTikTok Shop Fees & Settlement
Separate sales activity from settlement logic and understand how fees and payout timing affect marketplace reporting.
Read insightTikTok Shop GMV vs Profit
See why topline GMV can grow while contribution stays weak when Ads, fees, COGS and SKU mix move differently.
Read insightGMV Max ROAS vs Profit
Put paid-growth efficiency back into margin context instead of treating platform ROAS as a complete profitability measure.
Read insightCOGS Explained
Define product cost consistently so marketplace profitability does not change every time a different spreadsheet is opened.
Read insightCommerce Profitability
Connect revenue, fees, Ads, cost and contribution into the commercial questions operators need to answer next.
Read insightCommon questions
Commerce automation & reporting, answered directly.
What does commerce automation and reporting actually manage?
D2 maps marketplace and advertising sources, normalizes fields, reconciles orders and settlement, applies explicit fee and cost logic, flags missing or conflicting data, and produces reporting for revenue, Ads, platform fees, COGS, contribution and operating decisions. The reporting layer is built on verified source logic rather than dashboard presentation alone.
When should a business rebuild its ecommerce reporting process?
A rebuild is useful when recurring reports depend on manual spreadsheet consolidation, different teams produce different answers for the same period, settlement cannot be explained from orders, or a dashboard has no traceable source and formula definitions. D2 starts by mapping those inconsistencies before adding more automation or visualization.
How is reconciliation different from a dashboard?
A dashboard visualizes the numbers it receives. Reconciliation checks whether those numbers represent the same period, order population, status logic and commercial definition before they are combined. D2 treats source mapping, validation and reconciliation as upstream requirements so a clean chart does not hide inconsistent revenue, settlement or cost logic.
Can D2 combine TikTok Shop, Shopee, Ads and COGS data?
Yes, when the required source files, exports or API access are available. D2 can normalize marketplace orders, settlement, platform fees, advertising spend, product cost and packaging or other agreed cost inputs into one reporting model. The exact fields and level of automation depend on what each source exposes.
Why can GMV be different from settlement and profit?
GMV is a topline sales measure, while settlement reflects what the marketplace pays after timing, statuses, fees and adjustments. Contribution then introduces cost layers such as Ads, COGS, packaging, creator commission or other agreed expenses. D2 keeps GMV, recognized revenue, settlement and contribution as separate concepts so teams do not treat one number as all four.
How does D2 calculate marketplace contribution?
D2 defines versioned formulas around verified inputs. A typical contribution view starts with recognized revenue, then deducts the agreed platform fees, advertising spend, product cost and other variable costs in scope. The exact formula is documented so the team can see which costs are included, which are excluded and which inputs are still missing.
Can D2 work from spreadsheet exports instead of APIs?
Yes. Manual exports can be a valid source-of-truth starting point when platform APIs are unavailable, incomplete or not yet approved. D2 can standardize recurring files first, then automate selected ingestion or transformation steps later without changing the underlying reporting definitions.
Can D2 automate recurring commerce reports with n8n?
Yes, where automation is operationally appropriate. n8n can orchestrate file intake, API calls, validation, transformation, scheduled processing, exception alerts and report delivery. D2 keeps validation and failure paths explicit because automated reporting is only useful when missing, duplicate or malformed inputs are visible.
Who owns the source data and financial definitions?
The client retains ownership of marketplace accounts, raw business data, product cost truth and final accounting or finance policy. D2 owns the agreed source mapping, reconciliation logic, workflow, reporting implementation and operating checks within scope. Any management contribution view is an operating model unless the client separately validates it for statutory accounting use.
How does D2 price automation and reporting work?
D2 scopes the fee around the number of sources, reconciliation rules, reporting depth, automation complexity and ongoing operating responsibility. Marketplace revenue is not automatically used as the fee basis. Any recurring support, custom integration or performance-related commercial term is defined explicitly in the proposal before work begins.
Reporting system review