Staff access only.
| Order / Date | Customer | Account | Product | Status | Assign device |
|---|
| IMEI | ICCID | Device ID | Account(s) | Status | First seen |
|---|
Every customer account. Attach a device to one directly (no order needed) or remove one. Attaching writes the same registration as order fulfillment — the device appears in that account's app and starts reporting once it's powered on.
| Account | Status | Devices | Add device |
|---|
Purchase → live data: the full flow
The six stages a tracker goes through, from a customer buying it to the parent seeing live positions. Stages ③ and ④ are the ones staff act on, here in this console.
| Stage | What happens | Where |
|---|---|---|
| ① Buy | Customer picks a tracker in the app. Each product has a fixed deviceType
(SINOTRACK_ST904L or TELTONIKA_ATC700) — this decides the whole downstream setup. |
Customer app / store |
| ② Pay | Stripe charges the server-set price. An order is saved paid,
carrying the deviceType copied from the product. |
Stripe / store |
| ③ Assign | Staff ship the unit, then Assign its printed device id / IMEI to the paid order (Orders tab). This registers the device to the customer's account — required before any data is accepted. | Orders tab |
| ④ Provision | Once the unit is powered on, staff hit Provision on the order. We look up the SIM,
then send the over-the-air setup SMS for that deviceType (SinoTrack → h02 / port 5013;
Teltonika → port 5027). Watch progress in the Devices tab. |
Orders tab → Devices tab |
| ⑤ Ingest | The device connects to our ingest service and streams positions. Frames from an unregistered device (no step ③) are rejected. Accepted positions are stored + pushed live. | Ingest service |
| ⑥ App | Because step ③ tied the device to the buyer, live positions flow to their app. | Customer app |
Where the SIM comes from: when a unit first powers on, 1NCE reports its SIM to us and we record it (ICCID + IMEI). Provision links the order's assigned id to that SIM row to find the ICCID it needs to text. So a unit must have been powered on at least once, or Provision replies “no SIM found — power it on and retry”. SinoTrack units match the SIM by their device id; Teltonika units match by IMEI.
Device provisioning states
The lifecycle a SIM/tracker moves through, from first network attach to fully live. A unit is only genuinely tracking once it reaches DEVICE_SENDING_DATA.
| State | Meaning | Set by |
|---|---|---|
| CLAIMED | 1NCE reported a new SIM (first network attach) and we recorded it (ICCID + IMEI). No SMS sent — just on file, ready to Provision. | Receiver |
| PROVISIONING | Provisioner is running — an operator hit Provision (or Retry). | Provisioner |
| SMS_SENT | All setup SMS accepted by 1NCE (HTTP 201). Not yet confirmed by the device. | Provisioner |
| DEVICE_ACCEPTED | SinoTrack only. Device replied SET OK and its RCONF read-back shows the redirect to our ingest. (Teltonika skips this and confirms straight from live data.) |
Provisioner |
| DEVICE_SENDING_DATA | Terminal success. The tracker is actually reporting positions to our ingest (a live position row exists). Works the same for both device types. | Provisioner |
| TO_RETRY | An operator hit Reset — the SIM is queued to re-provision from scratch (derived fields cleared). Moves to PROVISIONING as the provisioner picks it up. | Admin (Reset) |
| FAILED | A setup SMS could not be sent to 1NCE (API error). The device may be fine — use Retry / Provision again. | Provisioner |
| PROVISIONED | Legacy. Success marker from an older provisioner, before the end-to-end data check existed. Not written anymore; not proof the unit is currently reporting. | — |