The lock has to enter your ecosystem
Tuya and TTLock are the two ecosystems we build on. Which one you choose decides the app, the gateway and how much control your customer gets.
Buyer guide · Smart home integrators
Integrators order more often than any other buyer type we serve, and the thing that ends a relationship is a lock that does not behave the way the ecosystem promised.
Swipe the table sideways to see the full specification →
| Buyer type | Smart home integrators |
|---|---|
| Typical first order | 30 sets door locks / 1 carton (20 pcs) padlocks |
| Samples | 3-7 days |
| Trial order | 10-15 days |
| Bulk order | 20-35 days |
| Customisation | Marking, packaging and non-standard bodies at quote stage |
| What to send first | Door photo or drawing, quantity, destination market |
Two things worth knowing before the first order, whichever product you end up buying.
Tuya and TTLock are the two ecosystems we build on. Which one you choose decides the app, the gateway and how much control your customer gets.
Tuya Bluetooth and TTLock open the lock from the phone. The older Tuya Wi-Fi generation only takes a request. Everything else about the order depends on that answer.
The five that come up most often in this buyer group, answered with the conditions attached.
Buyer questions
Tuya has the wider consumer brand recognition and a large device ecosystem. TTLock has finer access-control features such as timed e-keys and access history. Both open actively from the phone.
Cloud-to-cloud work is a project rather than a product option, and it depends on the platform. Tell us what you need and we will say whether it is a configuration or a development task.
White-label apps exist in both ecosystems under commercial terms we do not control, so we will not promise an app we cannot deliver. What we can do is confirm what the platform allows.
On Tuya Bluetooth and TTLock, yes. On the older Tuya Wi-Fi generation, no - that version is request-based only, and we state which one is on the quotation.
The gateway pairs to the lock in the app, and range depends on the building. We confirm the pairing method per model rather than quoting a distance.
Each of these has cost somebody a shipment. All four are avoidable at quote stage.
The most expensive mistake in this category. If the app is the reason the customer chose the product, the version has to be confirmed in writing.
Gateways are ecosystem specific. A Tuya gateway does not manage a TTLock lock.
Test the sample in your own environment before you demonstrate it. Bench behaviour and installed behaviour differ.
Record the firmware and app version on the sample. An update that changes behaviour should not be discovered at a customer site.
Four stages, and what we need from you at each one.
Tuya or TTLock, and which of your platforms it has to sit inside.
This is a line on the quotation, not an assumption from the model name.
Where an integration is involved, we put the technical questions to the platform rather than guessing.
Test the sample in your own environment, then order the batch against the specification you validated.
Chosen for this buyer group rather than sorted by date.
The version check that matters most.
Read the guide →Choosing the ecosystem your market uses.
Read the guide →What drains it and what to tell the customer.
Read the guide →When a rating is genuinely needed.
Read the guide →An integration that needed fixing.
Read the guide →What to send for an integration order.
Read the guide →