Designing a Multi-Store Profit Feed That Doesn't Lie

Starway Global — Thu, 12 Nov 2026 11:37:58 +0000

TikTok Shop operators often run several stores, several ad accounts, and several people who all need the same answer: are we actually making money?

A dashboard that only adds revenue from each store can look healthy while profit is leaking through returns, delayed fees, creator commissions, and campaign spend. The problem is usually not the chart. It is the grain and timing of the underlying profit feed.

Start with one daily ledger grain

Use one row per store, market, currency, and business date. Keep gross merchandise value, seller-funded discounts, platform fees, affiliate commissions, refunds, and ad spend as separate columns. Do not flatten them into a single revenue number too early; once the details disappear, reconciliation becomes guesswork.

Store the source timestamp and the ingestion timestamp together. This makes late-arriving orders and corrected settlements visible instead of silently rewriting yesterday's total.

Normalize time before comparing stores

Orders, ads, and settlements may use different time zones. Convert all event timestamps to a documented reporting time zone, then derive the business date from that normalized time. Pair every displayed metric with the time zone used to calculate it.

Treat returns and fees as delayed events

A refund can arrive days after the order. A commission can be estimated first and finalized later. A robust feed should support:

event date — when the sale happened;
posting date — when the adjustment became known;
revision version — which settlement record is current.

Keep both event-date and posting-date views. Finance needs the corrected ledger; operations often needs to see when a problem was discovered.

Allocate shared costs explicitly

Ad spend and creator cost should have a documented allocation rule. An ad account linked to two stores can be split by tracked revenue, order count, or a fixed operating rule. The exact rule matters less than making it stable, visible, and versioned.

Do not let a visual grouping imply a precision that the source data does not have. Label estimated contribution separately from settled profit.

Make metric semantics part of the API

A useful feed should return field definitions alongside values. For example:

{
  "store_id": "store_01",
  "business_date": "2026-11-12",
  "currency": "USD",
  "settled_revenue": 8240.55,
  "refunds": 312.10,
  "platform_fees": 641.22,
  "creator_cost": 530.00,
  "ad_spend": 1120.40,
  "contribution_profit": 5636.83,
  "is_estimated": false
}

The schema is intentionally boring. Boring fields are easier to audit, compare, and monitor.

Put anomalies into the data model

Late settlements, duplicate imports, currency mismatches, and negative adjusted orders should become explicit quality flags. A feed that quietly drops these rows creates a more dangerous problem than a dashboard with a visible warning.

A practical validation layer can check:

Every order maps to one known store.
Currency conversion uses the documented rate date.
The settled total remains within a defined tolerance of the event-date estimate.
Ad spend exists for every active campaign account.
Refund and fee revisions never overwrite the raw source record.

Use the feed for decisions, not decoration

Once the ledger is normalized, operators can answer useful questions consistently: which store has the best contribution margin, which campaign is creating revenue without profit, where returns are eroding a product, and which creator mix is improving repeatable economics.

Multi-store reporting is less about connecting more charts and more about agreeing on one auditable definition of profit. The original operations guide behind this model is available in the multi-store management playbook, and the free profit calculator can help validate unit economics before the data is connected.

A Practical Break-Even ROAS Model for TikTok Shop Sellers

Starway Global — Thu, 12 Nov 2026 09:45:49 +0000

Most TikTok Shop dashboards show revenue, ad spend and ROAS. Those numbers are useful, but they do not tell you whether an order made money.

The missing layer is contribution margin. Once you calculate it, break-even ROAS becomes a simple business rule instead of a guess.

Start with contribution profit per order

Use the real cost stack, not only the product cost:

contribution profit =
  selling price
  - product cost
  - platform fee
  - affiliate commission
  - shipping and fulfilment
  - payment fee
  - refund allowance
  - advertising spend

For example:

selling price             $40
product cost              $12
platform fee               $3
affiliate commission        $6
fulfilment                 $5
expected refunds           $2
advertising               $10
------------------------------
contribution profit         $2

The order generated $40 of revenue and $2 of profit. That is a 5% contribution margin after advertising. A revenue-first report would make the order look much healthier than it actually is.

Turn margin into break-even ROAS

Contribution margin before ads is:

margin before ads = contribution before ads / revenue

Break-even ROAS is the inverse:

break-even ROAS = 1 / margin before ads

If a product contributes 35% before advertising:

break-even ROAS = 1 / 0.35 = 2.86

ROAS 2.4 is below break-even. ROAS 3.2 leaves some room for ads, refunds and testing.

Here is the same rule as JavaScript:

function breakEvenRoas(contributionMarginBeforeAds) {
  if (contributionMarginBeforeAds <= 0) return Infinity;
  return 1 / contributionMarginBeforeAds;
}

console.log(breakEvenRoas(0.35)); // 2.857...

The three costs sellers miss most

1. Affiliate commission

Creator commission is often 10–30% of the sale. If you calculate margin without it, your break-even threshold is too low.

2. Refunds and return loss

A refund is not only a reversed sale. It can include return shipping, damaged inventory and payment costs. Build an expected refund allowance into the model.

3. Discounts and campaign prices

If the advertised price is $40 but the campaign converts at $32, use $32. Otherwise you are calculating the margin of a price the customer did not pay.

Build a product-level decision table

A useful operations view should show:

selling price;
variable cost per order;
contribution margin before ads;
break-even ROAS;
target ROAS;
refund rate;
advertising spend;
contribution profit.

That turns campaign management into a repeatable comparison. A high-revenue product with a thin margin should not receive the same scale target as a lower-revenue product with more contribution profit.

A practical stop rule

Instead of asking, “Did this campaign beat ROAS 3?” ask:

What is the product’s break-even ROAS?
Is the reported ROAS calculated over the same attribution window?
Are refunds and affiliate commissions included?
Does the campaign produce contribution profit after advertising?
Is the result repeatable at the next budget level?

This prevents a common failure mode: scaling a campaign that reports a healthy ROAS while the underlying product is already below its true threshold.

Calculator

You can run the formula without an account in the free break-even ROAS calculator:

https://www.fz567.cn/tools/breakeven-roas-calculator

For the written walkthrough, see:

https://www.fz567.cn/blog/roas-breakeven-tutorial

The key idea is simple: ROAS is a performance metric, but contribution profit is the decision metric.

DEV Community: Starway Global