Home
P1Browser logo

TikTok Shop Cross-Border vs. Local Shops: What's Different — Document Review, Secondary Review Triggers, and Legal Entity Verification Compared

The licenses that passed review for a cross-border shop under the same business license get stuck in secondary review for a local shop? This article breaks down the three-layer cross-verification differences in registration entity, payment entity, and logistics entity, with notes on the SPS linked score-drop mechanism and multi-shop environment isolation configuration essentials.

TikTok Shop Cross-Border vs. Local Shops: What's Different — Document Review, Secondary Review Triggers, and Legal Entity Verification Compared

Within 6 hours of submitting the 3rd Malaysian local shop for secondary review, the SPS scores for all three shop clusters under the same business license in Thailand, Vietnam, and Malaysia dropped in sync; Black Friday mega-sale registration eligibility collectively expired, and the associated TikTok Ads accounts entered a restricted state. Yet this same license-and-credential combination had passed first-round review at the cross-border shop stage, only to be repeatedly rejected for local shops. The core issue is not which field was left unfilled in the documents — it is that the review logic for cross-border and local shops follows two entirely different chains, from registration entity and legal entity verification to payment attribution.

In other words, you cannot simply replicate cross-border shop review-pass experience into local shops. Below is a breakdown of the specific differences.

Four currencies and local logistics parcels displayed side by side, illustrating the differences between cross-border and local shops in payment currencies and logistics fulfillment chains
Cross-border shops settle in USD/CNY via cross-border direct mail, while local shops must switch to local-currency payment and local 3PL fulfillment — the two fulfillment chains cannot be mixed or cross-linked

Registration Documents and Legal Entity Verification: What Exactly Differs Between Cross-Border and Local Shops

The two shop types share the same business license, but the platform invokes different entity-verification rules during review. Cross-border shops require a mainland China business license plus the legal representative's national ID card; local shops (taking Thailand, Vietnam, and Malaysia as examples) require a local entity registration or a power of attorney plus the legal representative's passport, with a minimum remaining validity of ≥12 months. More critically, the payment entity: cross-border shops use CNY or USD settlement accounts, while local shops must link to local-currency payment channels (Thai baht, Vietnamese dong, Malaysian ringgit) — the financial entities behind the two cannot be intermixed. For a detailed comparison, seeComparison of Registration Documents and Operating Costs: Cross-Border Shops vs. Southeast Asia Local Shops.

Review CriteriaCross-Border StoreSoutheast Asian Local Store (Thailand/Vietnam/Malaysia)
Registered EntityChinese Business License (Mainland)Local company or authorized agent + business license
Legal Representative IDID Card / Passport (validity ≥ 6 months)Passport (validity ≥ 12 months); name must match the registered entity word for word
Receiving EntityMainland China Settlement Account (USD / CNY)Local currency account (THB / VND / MYR); must not be cross-linked with a Chinese account
Logistics contract signatoryCross-border logistics service provider (4PX, YunTu, etc.)Local courier or local 3PL; the contracting entity must match the registered entity
AHR baseline evaluation dimensionsCross-border fulfillment SLA, return rate, customer complaintsLocal fulfillment SLA (typically within 48h), local return handling, influencer outreach response
Likelihood of triggering a secondary reviewLow (high degree of document standardization)Higher (three-way cross-verification of the legal representative's passport, entity type, and logistics contract)

In the table above, the most frequent rejection points are concentrated in two cells: passport validity under 12 months, and a mismatch between the logistics contract signatory and the registered entity. The backend rejection notice usually only reads \"legal representative document information does not match the registered entity,\" and even after a character-by-character name check the application is still turned back—the actual blocker is a mismatch in validity period or entity type (limited company vs. sole proprietorship).

Desktop layout on a single workstation where multiple store browser Profiles are color-coded and isolated, each mapped to one of five sub-account roles
Name groups by Country + Store Type + Sequence Number. The five-role sub-account matrix maps to five types of browser Profiles to prevent environment-layer disconnection.

The three-layer causal chain behind a second-review trigger: it is not incomplete documentation, it is entity disconnection.

A second-review rejection is rarely caused by a single missing field; instead, a disconnection has occurred among the three entity layers. Listed in order of troubleshooting priority:

  1. Registered Entity Layer—The business license name, Unified Social Credit Code, and legal representative's name must match the platform's registration information character for character. If a local store is registered through a local agent, the authorized person's name in the letter of authorization must exactly match the name on the submitted passport; even a one-letter discrepancy triggers an "inconsistency between legal representative ID information and the registered entity."
  2. Receiving Entity Layer—The settlement account's registered name must match the registered entity (or the authorized party in the letter of authorization). Cross-border stores linked to RMB accounts and local stores linked to THB accounts: if multiple stores under the same business license are mixed with different-currency receiving accounts, the platform will flag a funding entity anomaly and directly trigger a second-review check.
  3. Logistics Entity Layer—Party A (shipper) in the fulfillment logistics contract must be the store's registered entity or its authorized agent. If the contract entity is listed as the parent company while the store is registered under a subsidiary, even with the business license linked, it will be ruled as a broken logistics chain.

If any of the three layers is disconnected, the second review will reject the application. Before resubmitting, you must followthe step-by-step troubleshooting path from legal representative verification to account health scoreand verify each layer in sequence—do not simply correct the name spelling.

When multiple stores operate under the same business license, the platform identifies them as the same controlling entity. Local stores have a significantly higher probability of triggering secondary review compared to cross-border stores. Once a store fails to pass, SPS scores for other stores under the same entity will drop synchronously within a 24–72 hour window, and stores with an AHR below 150 points will lose eligibility for major promotional campaigns. TikTok's officialAdvertiser Account Policyexplicitly requires advertisers to comply with platform processes and local laws; account restrictions triggered by entity discontinuity fall into this category. Therefore, secondary review checks for local stores must be stricter than those for cross-border stores—cross-border store documentation is highly standardized and the three-tier consistency requirement is easier to meet, whereas local stores require word-by-word verification of passport expiry dates, entity types, and logistics contract signatories.

Frequently Asked Questions

After a cross-border store passes review, can the same set of documents be directly reused to open a local store?

No. The certificate combination that passed review for a cross-border store (Chinese business license + ID card + RMB payment + cross-border logistics contract) must be entirely replaced with a local entity + passport + local currency payment + local 3PL contract for a local store. Direct reuse will trigger an entity type mismatch and will most likely result in secondary review rejection.

After a secondary review rejection, is there a required waiting period before resubmission?

The platform has not published a fixed cooling period, but resubmitting the same materials unchanged will typically result in another rejection. It is recommended to correct each item along the three-tier causal chain and then resubmit after at least 48 hours. Before resubmission, complete three checks: passport expiry verification, word-by-word entity name verification, and logistics contract signatory confirmation.

Views 0