First, a judgment: compliance implementation is not about memorizing policies, but about building a five-layer evidence chain
Policy documents in 2024 are not hard to find; what is hard is translating them into concrete actions. Many sellers have saved dozens of articles, yet when problems actually arise, they are concentrated in four areas: product names cannot be classified into codes during declaration, tax responsibility is unclear as to who bears it, platform secondary review requires supplementary materials, and after multiple people operate the account, permissions are misused or the account attracts risk-control attention.
These are not cases of having failed to memorize the policies, but rather of a broken evidence chain. It is recommended to break compliance down intoproduct access, business entity, declaration, taxation, and platform account environmentfive layers, with each layer leaving records that can be reviewed by customs, tax authorities, platforms, and colleagues. In terms of sequence, products come first and stores second; declarations come before taxation; platform permissions are placed last: products determine codes, certification, and tax burden; the entity determines who declares and who pays taxes; platform permissions are only the execution layer and cannot fill the gaps left in earlier layers.
Pre-selection screening: put 'can it be sold, and is it easy to declare' before bulk listing
Cross-border e-commerce product selection methodologies talk a lot about conversion rates and competition intensity, but rarely about compliance filtering. From a compliance perspective, a SKU must pass five filters; if it fails any one of them, the subsequent declaration and taxation work is wasted effort.
- Destination-country prohibited/restricted sales and certification.First check the platform's market access requirements for the category, then check the destination country's mandatory certification, labeling, and manual language requirements. For products where no clear conclusion can be found, treat them as “not directly listable” first; do not gamble on passing review with a “list it and see” approach.
- Intellectual property.At minimum, conduct a preliminary screening of four areas: trademarks, designs, patents, and copyright. Selling on others' listings, unauthorized brand terms, cartoon characters, and accessory compatibility descriptions are high-frequency risk areas; operations understands selling points, but not necessarily the scope of authorization.
- HS code classifiability.Determine whether the product can be stably classified under one code based on material, function, and use, and write a one-sentence classification rationale. If a product set spans multiple codes or must be split into multiple declarations, factor the tax burden and operating costs in advance.
- Logistics attributes.Battery-containing, liquid, powder, magnetic, oversized, and time-sensitive goods directly determine the available channels and declaration methods, and also determine where returns go and who handles them.
- Returns and tax complexity.For categories with high return rates, high order values, and local after-sales requirements, factor reverse logistics and taxes into gross margin first, then decide whether to launch.
After screening, there are only three outcomes: directly listable, list after supplementing materials, or abandon or switch products. The key is that the list cannot stop with operations—before listing, sync the product list with declaration and finance so that codes, certification, and tax burden can be aligned in one go, rather than going back to revise them during customs clearance or tax refund.
Declaration checklist: for each SKU, at least six things must be clearly explained.
When declaration problems occur, it is usually not because one does not know how to fill in the form, but because one only discovers when filling it in that there is no evidence behind the fields. It is recommended to create a record for each SKU for the following six items, each corresponding to a verifiable document rather than a verbal statement.
| Check item | Content that must be clearly explained | Recommended evidence to retain |
|---|---|---|
| Product name and use | The declared product name is consistent with the actual product, and the use description is specific to the scenario. | Product specification sheet, physical product photos, and archived Listing page |
| HS code and classification basis | The code corresponds to the material, function, and use, and the rationale for classifying it here can be written down. | Classification explanation, historical declaration records, and references for similar products |
| Country of origin | The actual production location matches the declaration, and batches can be distinguished when multiple factories supply | Purchase contracts, factory information, production records |
| Declared value and transaction terms | The composition of the transaction price is clear, and there is a basis for how freight, insurance, and discounts are handled | Orders, invoices, payment records |
| Licenses and certifications | Whether the certifications required by the destination country are within their validity period and cover this model | Certification certificates, test reports, validity period registers |
| Logistics and order tracking | Order numbers, waybill numbers, and customs clearance records can be matched to one another | Logistics shipping labels, customs clearance receipts, and records of handling abnormal shipments |
The choice of customs supervision mode (e.g., 9610, 9710, 9810, 1210) should be based on the company's actual situation, the form of the goods, and local customs requirements; the code others use does not mean it suits you. A policy number is not the answer—whether it matches your order, logistics, and payment collection structure is.
Tax checklist: first distinguish who bears the tax, who files the declaration, and who retains the supporting documents.
The most common tax misjudgment is treating the amount displayed in the platform backend as a tax conclusion. When verifying, break it down into five categories, and clearly state the responsible party and the location of supporting documents for each category.
- Customs duties and VAT at the import stage.Who bears customs clearance responsibility in the destination country, DDP or DAP, and how the tax base is structured—all must correspond to specific orders and logistics documents.
- Applicability of export tax rebates or tax exemption without invoices.Entity qualification, input vouchers, and whether the goods fall within the applicable scope—if these three conditions are not all met, do not calculate gross margin based on tax rebates; otherwise, pricing will be wrong from day one.
- Platform withholding and remittance.Which sites are subject to platform withholding, and at which layer the withholding occurs, must be based on the platform backend and local rules; do not assume all sites are the same.
- Corporate income tax and individual income tax or labor remuneration.Which entity receives the store revenue, how personnel costs are expensed, and whether overseas service fees have compliant supporting documents—all must be clearly explained.
- Payment collection and foreign exchange.Whether the receiving account, store entity, and reporting entity are consistent with one another; any inconsistencies must be clearly explained and documented.
The test is simple: if all you can say about a funds flow is “the money arrived,” without being able to explain who reports it, who bears responsibility, and where the supporting documents are, then this item has not been implemented.
Platform rules checklist: account entity, store permissions, login environment, and tool write operations must be consistently mapped
Platform reviews often do not rely on a single signal. Login environment, payment information, contact details, return address, and operational behavior may all be factored into the assessment; the specific reason for any action is subject to the account notification and the platform's official policies. What can be done is to lock down these elements so that every operation can be traced back to a person. The boundary that must first be clarified is this: login environment isolation can only reduce the probability of account crossover at the operational level; it does not constitute account entity compliance, nor can it replace KYC materials and reporting obligations. For this distinction, refer toIs it safe to use a fingerprint browser for multi-account operations: environment isolation boundaries and platform risk control.
| Platform | What the entity and KYC need to align on | Backend roles and permissions | Login environment and tool write operations |
|---|---|---|---|
| Amazon | Registered entity, receiving account, address information, and secondary review materials are from the same source | Seller Center roles should be split by job function to avoid sharing the main account. | Use a separate environment per store; verify the store ID before ERP writes. |
| TikTok Shop | The seller account entity must match the store qualifications and category access. | Separate permissions for creator collaboration, customer service, and order processing. | For cross-region operations, the time zone and egress must match the store's site. |
| Shopify | The store owner account must correspond to the independent site assets and payment channels. | Employee permissions should be minimized by function and revoked immediately upon departure. | Register the app authorization scope and the stores it writes to individually. |
| AliExpress / Shopee | The store entity, receiving account, and shipping origin information should be mutually verifiable. | Sub-accounts are split by operations, customer service, and finance | When multiple stores operate in parallel, environments and operators have a fixed correspondence |
For Amazon, the key verification points are role division in Seller Central and ownership of two-step verification materials; for detailed practices, refer toMulti-Account Operations in Amazon Seller Central: How Store Management Tools Avoid Association-Based Account Suspension. The meaning of “multiple stores” differs between TikTok Shop and Shopify: the former centers on seller accounts and platform stores, while the latter centers on store owner accounts and independent site assets; permission segmentation methods cannot be directly transferred. For the differences, seeTikTok Shop vs. Shopify: Seller Account Management Comparison.
As the number of stores increases and more people participate in operations, first establish a one-to-one correspondence between environments and tools, then consider changing tools; for specific checklist items, refer toHow to Choose a Fingerprint Browser for Cross-Border E-Commerce: An Evaluation Checklist from Account Isolation and Proxy Configuration to Team Collaboration.
7-day implementation sequence: close evidence gaps first, then discuss tool upgrades
- Day 1: Take stock of products on sale and stores; list which document is missing for each SKU and which legal entity and receiving account each store corresponds to.
- Days 2-3: Complete declaration and certification materials. First handle products whose codes cannot be classified and products missing certification; delist first any that can be delisted.
- Day 4: Check tax liabilities and supporting documents store by store; mark unclear items in red and submit them to Finance for confirmation rather than letting operations decide on their own.
- Days 5-6: Clean up platform permissions; reclaim accounts of departing and transferred employees on the same day; ensure login environments and operators have a fixed one-to-one correspondence; and record tool write scopes in a register.
- Day 7: Create an owner list and review cycle; specify who reviews which item and when, and which documents must be reviewed during handover.
When budget is limited, the priority is the legal entity, filings, and tax evidence; tools come last. Tools can reduce operational risk and the probability of cross-store issues, but cannot replace a compliant entity and tax obligations—saving this table to the team's shared drive is more useful than bookmarking another ten policy interpretations.
Frequently asked questions
When doing cross-border business in 2024, should I register the business entity first or select products first?
They can be done in parallel, but the decision sequence should be to first check whether the product can obtain compliant market access, and then determine which entity will handle it. Products determine codes, certification, and tax burden; the entity determines who declares and who pays tax. No matter how compliant the entity registration is, it is meaningless if the products cannot enter the destination country.
Without export tax rebate experience, which items should I start checking on the tax checklist?
First check whether the receiving entity and the declaring entity are consistent, then confirm whether input vouchers are complete. If these two items are not resolved, there is no basis for calculating the tax rebate; other details of platform withholding and remittance can be completed site by site.
When a platform requires supplementary KYC or secondary review materials, how should operations and finance divide responsibilities?
Operations is responsible for the accuracy of product information, store information, and page records, while finance is responsible for entity licenses, receiving accounts, and tax certificates. Before submission, one person should centrally verify that the materials come from the same source, to avoid multiple versions of addresses, phone numbers, and accounts across different documents.
When people and tools are shared across multiple platforms and stores, which records must be kept?
At least four categories must be kept: a mapping table of stores to entities, a list of backend roles and personnel, records of login environments and operators, and the write scope of tools such as ERP. During handovers and offboarding, checking these four categories item by item is far less effort than investigating after the fact.
