Tuya Trade-in Conditions and Process
Document Version: 20250724
Table of Contents
1. Trade-in Operation Instructions
This document describes the operation instructions for production certificate trade-in.
2. Restriction Conditions
- Cannot trade-in without successful authorization.
- Cannot trade-in with App activation.
- FFS, HomeKit, Carrier projects cannot be traded in.
- Authorization code list, Production certificate - authorization only, cannot be traded in.
3. Operation Process
The operation process involves the following steps:
Trade-in Token Acquisition (via IoT) → Production Certificate Confirmation (via PMS) → Trade-in Token Registration (via PMS) → Production Testing (using Cloud Module Production Test Tool).
4. Operation Instructions
4.1. I. Trade-in Token Acquisition
For trade-in token acquisition, please refer to the link: Production Certificate (Token) Trade-in Extraction.
4.2. II. Production Certificate Confirmation
After extracting the production certificate for trade-in, first confirm it in the Production Certificate Confirmation column of the PMS system. The process is illustrated below:
Screenshot of Tuya Smart Industrial SaaS Platform > Production Management > Work Order Management > Production Certificate Confirmation. A dialog box appears prompting for "Production Certificate" input. Upon successful confirmation, it displays "Production Certificate Confirmation Successful". Fields shown include "Work Order", "Production Certificate", "Token", "Quantity", and buttons for "Cancel" and "Confirm".
4.3. III. Trade-in Token Registration
Next, in the PMS system's Production Certificate Trade-in section, add a batch name as shown in the figure below:
Screenshot of Tuya Smart Industrial SaaS Platform > Production Management > Work Order Management > Production Certificate Trade-in. It shows fields to "Add Batch Name" (请输入自定义批次名称), "Token", "Quantity", and "Trade-in Reason". A table lists existing batches with options to "View Details" or "Delete".
4.4. IV. Production Testing
1. Open the Cloud Module Flashing Authorization Platform tool. Enter the production certificate for trade-in. Refer to the Cloud Module Tool User Manual for specific operations. Follow the sequence indicated in the figure:
- (1) If you need to associate the original SN on the module: Check "Detect SN" at item 5. In the SN field at item 7, scan the SN code from the module label and click "Run" to start the operation.
- (2) If you do not need to associate SN: Uncheck the box at item 5. Leave the SN field at item 7 blank and click "Run" to start the operation.
Screenshot of "Cloud Module Flashing Authorization Platform 3.3.0.23". The interface includes sections for "Parameter Settings", "Operation Mode", "Test Report", "Log Function", and "Help". Key fields visible are "Production Certificate", "Product Model" (e.g., CB3S), "Test Process" (e.g., Trade-in - Flashing Authorization), "Authorization Method" (e.g., wifi), "SN" field (item 7), "Detect SN" checkbox (item 5), "Run Mode" (Click to Run), and a "Run" button.
2. After successful trade-in flashing authorization, the status is shown below:
Screenshot showing a successful status in the "Cloud Module Flashing Authorization Platform". The "Test Details" section indicates success.
5. Frequently Asked Questions
For common problems with trade-in operation failure, please refer to the trade-in FAQ.
Note on Operation Stability: Trade-in operations require complex logic and a stable test bench for a successful one-time completion. Mid-process failures can lead to operation failure, requiring repurchase of production certificates. If test environment stability is a concern, or for full order rework, consider using the after-sales rework mode.
6. Tool Logic
The tool logic for the trade-in process is as follows: The process begins by entering production testing and obtaining the MAC address. It queries for trade-in records based on the token ID. If the data originates from a Cloud Module, it queries for the latest authorization log using the SN. Checks are performed for SN, MAC, and UUID matching, and for device authorization information. If no record is found, the process proceeds to "Trade-in Record Entry", where it checks for duplicate data. "Trade-in Record Validation" follows, verifying successful entry and the 7-day validity of the MAC address. If validation fails, the previous authorization is invalidated, and the total count is decremented. The process then moves to "Erase", checking if the token is a trade-in token. Next is "Burn", where it queries for the latest UUID and batch number using the MAC (first MAC, then SN) and compares it with the trade-in entry record. "Authorization" verifies if the trade-in status is "Validation Successful" or "Update Successful". If not, it follows the normal token authorization flow. If successful, an authorization UUID is created, and the batch number's trade-in status is set to "Update Successful". The process concludes.
