来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 Review process for app developers
This page explains which TikTok Shop app review steps apply to public apps, custom apps, and seller-developed custom apps, how the review stages are sequenced, and how to interpret the 25-authorization rule. Use Partner Center as the source of truth for the latest review status, required actions, and market-specific SLA. The time ranges below are planning estimates for launch scheduling, not guaranteed approval times. Review time can change based on market, app category, submission quality, API scope risk, data access, and resubmissions.
§2 Review stages at a glance
The review flow depends on app type, category, target market, and seller authorization scale.
| Review stage | Public app | Custom app | Seller developer custom app | Trigger or notes | Planning estimate |
|---|---|---|---|---|---|
| Registration review | Required | Required before broader launch when Partner Center requests it | Developer onboarding required; marketplace app review is usually not required for own-shop use | Confirms developer qualification and launch eligibility | Usually several business days after complete submission |
| App design / ARD review | Required when Partner Center requests ARD or design materials | Required if the app is a Connector app, reaches 25 or more seller authorizations, or Partner Center requests review | Usually not required for own-shop use | Reviewer checks whether the App Requirement Document (ARD) and design materials cover required TikTok Shop use cases | Usually 3-5 business days after complete materials are submitted |
| App development and app review | Required | Required for Connector apps, custom apps with 25 or more seller authorizations, or apps otherwise flagged by Partner Center | Usually not required for own-shop use | Reviewer tests the app, checks API scope usage, verifies seller-facing flows, and reviews product evidence | Usually 5-10 business days after a complete testable build is submitted |
| Language listing review | Required for every public app and for each target market or listing language | Not required unless the custom app is being upgraded to public or Partner Center requests listing materials | Not required | Confirms that App and Service Store listing content is accurate and market-language compliant | Usually 3-5 business days per submitted market or language |
| Compliance, legal, data security, and privacy review | Required when applicable and must be passed before listing | Required when applicable based on market, category, data access, or Partner Center request | Required when Partner Center requests it | Data Security and Privacy Review (DSPR) assessment is commonly planned at about 2 weeks; full compliance/legal review may take 3 or more weeks. US data-security review may use a market-specific 10-12 working day estimate when that process applies | Start as early as possible; this is often the longest path |
| Beta testing review | Required for Connector apps targeting US or UK sellers when Partner Center triggers beta testing | Required for Connector custom apps targeting US or UK sellers when Partner Center triggers beta testing | Usually not required | During beta or pre-approval review, seller authorizations may be temporarily limited | Usually 2-4 weeks, depending on beta scope, defects, and required seller coverage |
| Launch / publish | Allowed after all required reviews pass | Allowed after all required custom-app checks pass | Allowed for own-shop custom use after required setup is complete | Public apps can be listed on the App and Service Store. Custom apps remain private and are shared by authorization link. | Immediate after approval in Partner Center, unless a market-specific hold applies |
§3 Text version of the review flow
The original flowchart shows the same review path visually. Use the text version below when the image is unavailable. Public app:
Create app
-> pass registration review
-> submit language listing for each target market
-> submit ARD, design materials, testing details, and screenshots
-> pass app design / ARD review
-> pass app development and app review
-> pass compliance, legal, data security, and privacy review when applicable
-> complete beta testing if the app is a Connector app targeting US or UK sellers
-> publish and list on the App and Service Store
Custom app:
Create app
-> complete required custom-app prerequisites in Partner Center
-> if Connector, 25+ seller authorizations, or Partner Center requests review:
submit ARD, design materials, testing details, and screenshots
pass app review
complete beta testing if required for the category and market
-> publish privately and share the authorization link
Seller developer custom app for the developer's own shop:
Register as a seller developer
-> create a custom app for the seller's own shop
-> configure scopes, authorization, signing, and webhooks
-> test the integration
-> use the app for that shop
Seller-developed custom apps that access only the developer's own shop data usually do not need app review, language listing review, or beta testing. Partner Center may still require onboarding, compliance, or security checks depending on market and data access.
§5 Language listing review
Language listing review is required for all public apps and must be completed for each target market or listing language where the app will be listed. The statement "only Connector apps targeting US or UK trigger this stage" should not be used for language listing review. That condition refers to beta testing review, not language listing review. Use this rule:
| App or scenario | Language listing review requirement |
|---|---|
| Public app | Required for each target market or listing language. |
| Public app adding a new market | Required for the new market before the app is listed there. |
| Custom app | Not required because custom apps are not listed publicly. |
| Custom app upgrading to public | Required for all selected target markets before the upgrade can complete. |
| Seller developer custom app for own shop | Not required. |
For field-level listing requirements, market-language requirements, and listing submission steps, see Publish and list a public app.
§6 App Requirement Document (ARD)
An App Requirement Document (ARD) is a review worksheet used to confirm app scope, required APIs, data handling, testing evidence, and launch readiness for a specific app category. The ARD template and submission path can vary by category and market. Use this order:
- In Partner Center, open App & Service.
- Select the app.
- Open the App Review section.
- Select Submission materials for review.
- Download or follow the latest ARD template shown for your app category, if one is provided.
- If the ARD template or submission path is not visible, contact your partner manager or submit a support ticket through How to contact support.
Submit the latest ARD version requested by Partner Center. Do not reuse an old ARD template from another category, market, or prior review without confirming it is still accepted.
§7 Connector category
A Connector app is an app category for integrations that connect TikTok Shop with an external seller operation system or commerce platform. Connector apps often synchronize product, order, inventory, fulfillment, logistics, or other operational data, so they can require additional review even when distributed as custom apps. Common Connector examples include:
| Connector example | Typical integration scope |
|---|---|
| Ecommerce platform connector | Connects TikTok Shop with platforms such as Shopify, WooCommerce, Magento, BigCommerce, or similar commerce systems. |
| ERP, OMS, or WMS integration | Synchronizes orders, inventory, product data, warehouse operations, or fulfillment status. |
| Logistics, 3PL, or fulfillment connector | Supports shipping, tracking, carrier mapping, fulfillment status, or third-party logistics operations. |
| Product feed or listing tool | Synchronizes product catalogs, pricing, inventory, or listing attributes. |
| Multi-channel commerce connector | Connects TikTok Shop with multiple marketplace or seller operation systems. |
This list is illustrative, not exhaustive. The app category shown in Partner Center is authoritative. If your app connects TikTok Shop to an external system and handles seller operational data, treat it as likely to need Connector-level review unless Partner Center confirms otherwise.
§8 App design review
During app design review, TikTok Shop checks whether the ARD and design materials show that the app can support the required TikTok Shop use cases for its category. Prepare:
- ARD for the correct category and market.
- Product design or workflow document.
- API scope list and why each scope is needed.
- Key seller journeys, such as authorization, product sync, order sync, fulfillment, returns, or reporting.
- Data handling notes, including where seller data is stored and how data is deleted when authorization ends.
If the reviewer requests changes, update the ARD or design materials and resubmit. The review clock usually restarts after resubmission.
§9 App development and app review
During app development and app review, TikTok Shop reviews and tests the actual app implementation. Prepare:
- Product URL or access instructions.
- Test account credentials that reviewers can use.
- Testing steps for the main seller workflows.
- Product screenshots and optional videos.
- API scope information.
- Known limitations, unsupported markets, and environment notes.
For public apps, app review is required before listing. For custom apps, app review is required when the app is a Connector app, reaches 25 or more seller authorizations, or Partner Center requests review for the selected category or market. If the app is rejected, open the review details in Partner Center, read the rejection reason, fix the issue, update the submission materials, and resubmit.
§10 Beta testing review
Beta testing review evaluates whether the app works reliably with real or controlled seller usage before broader launch. Beta testing is required when Partner Center triggers it, commonly for Connector apps targeting US or UK sellers. During beta testing:
- Public apps are not visible in the App and Service Store.
- Seller authorizations may be limited during the beta or pre-review period.
- Reviewers may evaluate app stability, seller experience, API correctness, and whether unresolved bugs could affect sellers.
- If defects are found, fix them and continue beta testing until the app satisfies the review requirement.
After required beta testing and all other reviews pass, Partner Center lifts the beta or pre-review limitations according to the approved launch path.
§11 Review status and resubmission
Use Partner Center to track review status for each required stage.
| Status | Meaning | Developer action |
|---|---|---|
| Draft | Materials are saved but not submitted. | Complete the required fields and submit when ready. |
| In review | TikTok Shop is reviewing the submission. | Monitor status and avoid changing submitted materials unless Partner Center allows it. |
| Approved | The stage passed review. | Continue to the next required stage or publish if all required stages are complete. |
| Rejected | The submission did not pass review. | Open the rejection details, fix the issue, update materials, and resubmit. |
If a review remains in progress longer than the planning estimate, submit a support ticket with the app key, service ID, market, app category, review stage, submission date, and current status. Use How to contact support.