Why Distributors Should Confirm the Platform Early
A platform decision affects more than the app name shown in a sales presentation. It influences how the sample is added to an account, how installers complete onboarding, which actions work near the lock, which actions require network connectivity, and what users expect from remote management. If these points are left until after the sample arrives, a technically functional lock may still be difficult to position or support.
The platform also affects documentation and after-sales preparation. A distributor needs to know who creates the first account, who becomes the administrator, how another user receives access, how a lock is reset or transferred, and what happens when a phone, gateway or lock is replaced. These questions should be included in sample evaluation rather than treated as a later software detail.
Platform names alone do not confirm a function list. Tuya and TTLock each support multiple products, connection arrangements and development paths. The exact behavior available to a buyer depends on the lock hardware, enabled functions, app or account arrangement, gateway and approved configuration.
What Tuya and TTLock Represent
Both names refer to third-party technology environments used with connected devices, but neither name describes one fixed smart-lock specification.
Tuya
Tuya provides an IoT developer platform with public-app, OEM-app and SDK development paths. Its official Bluetooth-lock documentation describes short-range phone-to-lock operation and a gateway path to cloud connectivity. Available lock functions depend on the device protocol, selected data points, app service and project configuration.
TTLock
TTLock provides smart-lock app, management and open-platform capabilities. Its official documentation describes Bluetooth operations near a lock, account and access-permission management, and gateway-supported remote actions. The lock's supported features, gateway setup and account permissions determine which actions are available.
SUPTER does not own or develop either platform. A platform can be discussed only after the platform version available for the selected lock model has been confirmed.
Key Areas to Compare
Use the following matrix as a verification guide, not as a promise that every listed capability is available on every lock.
| Decision area | Tuya-based configuration | TTLock-based configuration | What the distributor should confirm |
|---|---|---|---|
| Product-model availability | Availability must be verified for the exact lock and ordered configuration. | Availability must be verified for the exact lock and ordered configuration. | Do not infer platform support from the model name, appearance or another lock. |
| App and account structure | Tuya documents public-app, OEM-app and SDK paths; the selected service and account arrangement affect onboarding. | TTLock documents an app account, lock administrator and delegated access roles; the exact management arrangement depends on the solution used. | Identify the app, account owner, administrator and user-transfer process before sampling. |
| Bluetooth and local operation | Official Bluetooth-lock documentation supports short-range phone-to-lock communication for configured Bluetooth locks. | Official documentation uses Bluetooth for operations performed near a compatible lock. | Test pairing, local operation, reset and account binding on the actual sample. |
| Remote access and gateway | A configured Bluetooth gateway can connect a compatible Bluetooth lock to cloud services; remote functions remain configuration-dependent. | A gateway connects a compatible lock to the network and enables documented remote management actions. | Confirm whether remote access is required, which gateway applies and which actions are enabled. |
| Temporary access | Tuya lock documentation includes temporary or dynamic password functions for certain implementations and enabled functions. | TTLock documentation includes eKeys and permanent, timed, recurring or one-time passcodes for supported locks. | Verify the credential types, validity rules and offline or gateway conditions on the sample. |
| Users and records | Member permissions and unlocking records are documented for certain Tuya lock solutions. | Administrator, authorized-user and operation-record functions are documented for supported TTLock locks. | Test who can add or remove users, which records appear and how records are retrieved. |
| Branding expectations | Tuya offers a separately configured and subscribed OEM App service with selected brand settings. | Do not assume a branded app is included merely because a lock uses TTLock technology. | Separate product and packaging branding from app branding, cost, account and publication requirements. |
| API or SDK integration | Tuya cloud API access requires a cloud project, the required subscribed services, credentials and account authorization. | TTLock Open Platform calls require an application client ID and access token; SDK or API scope must be reviewed separately. | Do not treat API access as automatically included with a lock order. |
| Region and data requirements | Tuya documents country-code-based data-center selection in its Commercial Lock App SDK account flow and account authorization for cloud projects. | The exact TTLock service and account arrangement must be confirmed before making any regional data claim. | Confirm the applicable app, SDK or cloud-project context and review market-specific privacy, account and compliance requirements. |
| Replacement and support | Replacement should be tested for device removal, re-pairing, account reassignment and gateway reconnection where applicable. | Replacement should be tested for lock deletion or transfer, re-initialization and gateway reconnection where applicable. | Document a repeatable process for installers and after-sales teams. |
A comparison is useful only when it refers to the same product model, access methods and operating scenario. A platform label by itself is not a complete product configuration.
Questions to Ask Before Choosing
Prepare a written answer to these questions before requesting a final sample recommendation:
- Which exact lock model and lock-body configuration are being considered?
- Which Tuya-based or TTLock-based configuration is approved and available for that model?
- Which actions must work locally, and which actions are expected to work remotely?
- Is a gateway required, and which gateway is approved for the sample?
- Who will create and retain the primary account and administrator role?
- How will users, installers or project staff receive and lose access?
- Is the product sold through retail, online, installer, distribution or project channels?
- Is branded packaging sufficient, or is a separately scoped app-branding service expected?
- Which manuals, onboarding steps and after-sales procedures must be prepared?
- How will a failed, returned or replaced lock be removed, reset and reassigned?
- Are there market-specific privacy, data, app-store or compliance requirements to review?
Sample Evaluation Checklist
Evaluate the actual model and approved configuration. Mark a function as not applicable when it is not included instead of assuming that the platform name guarantees it.
Record the app version, lock configuration, gateway model and account roles used during the evaluation. The record helps prevent a later order from being discussed against assumptions that differ from the approved sample.
How SUPTER Supports the Decision
SUPTER supports the commercial and project preparation around an approved smart-lock configuration. The scope is to help buyers connect the platform decision to the market, product and delivery plan.
SUPTER is not the owner or developer of Tuya or TTLock. Platform availability, app services, integration scope and remote functions must be confirmed for the selected product and configuration.
A Six-Step Final Decision Framework
Use one documented sequence so commercial, technical and service teams approve the same configuration.
- 01
Confirm the product model
Start with the lock, door conditions and access methods required for the market.
- 02
Confirm the available platform configuration
Verify whether the model has an approved Tuya-based or TTLock-based option and record its limits.
- 03
Define the channel and user workflow
Map account ownership, installer actions, user onboarding and remote-management expectations.
- 04
Test the sample
Evaluate the exact lock, app, gateway and account arrangement that is being proposed.
- 05
Confirm documentation, branding and support
Align manuals, packaging, app expectations, reset and replacement procedures.
- 06
Finalize the mass-order configuration
Record the approved hardware, platform, accessories, documents and supply plan before ordering.
The appropriate platform depends on the approved product model, configuration, market, channel and service workflow. Platform selection should be confirmed before sample evaluation and mass-order preparation.
Frequently Asked Questions
Is Tuya better than TTLock?
There is no universal answer. Compare the exact configuration available for the selected lock, then evaluate the account, connectivity, access-management, branding and support workflow required by the target channel.
Can every smart lock use either platform?
No. Platform support depends on the lock hardware, firmware, approved module or solution and ordered configuration. It must be confirmed model by model.
Is a gateway always required?
Not for every local operation. Bluetooth functions can work near compatible locks, while particular remote actions may require a configured gateway or another network arrangement. Test the exact sample.
Can the app branding be customized?
Do not assume it is included. Tuya documents separately configured OEM App services; any branding scope, service plan, account ownership, cost and publication process must be confirmed. TTLock-related app branding must also be scoped separately rather than inferred from the lock.
What should be tested on a sample?
Test local access, app onboarding, account roles, credentials, remote and gateway functions where included, records, language, installation, reset, transfer, replacement and documentation.
When should the platform be confirmed?
Confirm the available platform direction before sample preparation, then approve it only after the exact sample and service workflow have been evaluated.
Official Documentation Reviewed
This guide uses qualified platform-level information from official Tuya and TTLock documentation. Functions remain dependent on the exact lock, platform configuration, account arrangement and gateway.