Regulations & compliance

Linking tracking devices to the WASL platform

Integration is not a button you press. It is a technical chain running from the device, through connectivity, to the operations platform, and on to the competent authority. This page explains that chain and what has to be verified before any supplier makes you a promise — ourselves included.

Our position on integration, stated plainly

This page claims no official approval, qualification or direct access to any government system, and commits to no integration outcome before verification. We confirm integration for your case only after reviewing the device model, the establishment's eligibility and activity, and the integration requirements in force, and what we agree is written into the quote. The existence of a linkage requirement in a regulation does not by itself mean any given device or supplier is qualified for it.

Last reviewed: 16 October 2026

The integration chain: four links, any of which can break it

Understanding these links stops you paying out and then discovering the integration never completed, for a reason that had nothing to do with the device.

  1. The device

    The tracker model itself: whether it supports the required protocol and data format, and whether it is correctly installed and tested on the vehicle. Devices are not interchangeable here.

  2. Connectivity

    The SIM, data plan and coverage. A transmission gap shows up as an unlinked vehicle even when the device is healthy and the integration is in place.

  3. The platform

    The operations platform that collects the data and exports it in the required format. This is where technical compatibility and contractual eligibility have to be verified.

  4. The competent authority

    Receiving the data, validating it, and recognising the vehicle's status. That link is not in our hands, and we do not promise a decision that it issues.

What we verify before committing

We go through this list with you before anything is written into a quote.

  • The tracker model currently fitted, or proposed, and whether it supports the required data
  • The establishment's registered transport activity, since integration requirements vary with it
  • Establishment eligibility: commercial register and a valid licence for the activity
  • The vehicle list and the identifying data the integration process needs
  • Subscription and SIM status per vehicle, because a lapse breaks the link
  • Who owns the platform account and who on your side is authorised to administer it

A security note: never share passwords or access tokens through a website form or a general message. If integration needs any credentials, that happens over a direct channel with limited scope, and no chassis, plate or IMEI numbers are published on any public page.

What we actually provide here

  • Supplying and installing trackers, documenting serial numbers and mapping each device to its vehicle in the platform.
  • Setting up vehicles and users on the operations platform and monitoring transmission continuity.
  • Watching for connectivity gaps and resolving the technical cause: device, installation, SIM or coverage.
  • Stating what the device and platform support before purchase, so you are not deciding on an assumption.
  • Telling you straight when your case needs a route we do not cover — which does happen.

Frequently asked questions

Are your devices "approved" for integration?
We avoid the word "approved" on this page, because it needs current documentary proof per device model. Tell us your activity and the device model, and we will answer with what we can evidence for your specific case. If we do not have the evidence, we will say so rather than reach for a vague word.
I have devices from another supplier — can they be integrated?
It depends on the model, the protocol, and whether data can be forwarded. Send us the device model and vehicle count and we will set out the options: keep the devices, replace some, or confirm it is not feasible. We will not give a generic answer to a model-dependent question.
Does integration guarantee my vehicle will be accepted by the authority?
No. Integration is one technical aspect. Acceptance depends on fully meeting your activity's conditions and on the competent authority's decision. See the operating card page for the published conditions.
How long does integration take?
We do not give a fixed duration. It depends on vehicle count, the installation schedule, how complete your vehicle data is, and processing time at the authority. The quote sets a schedule for what we control — installation, testing and setup — without promising another party's timeline.
If transmission stops, who is responsible?
We diagnose the cause first: device, installation, SIM or coverage. Installation or device faults within warranty are handled as written in the quote. Causes such as coverage or a subscription lapsed on your side, we explain to you rather than leaving you to guess.

Official references

Always start from the competent authority to establish the integration requirements in force for your activity. We have not listed a platform-specific technical page here because we could not confirm which is the current official reference.

Ask about integration compatibility for your case

Tell us the current device model if you have one, the number of vehicles, and your registered activity. Do not send passwords or credentials here.

  • Phone & WhatsApp +966 54 204 3869
  • Business hours Saturday – Thursday, 9:00 AM – 10:00 PM
  • Coverage Installation and field service in Riyadh, Jeddah and Dammam, with installation arranged in other cities depending on the request and fleet size.

Ask about integration compatibility for your case

e.g. 0541234567 or +966541234567

We never ask for official documents at first contact.

Or continue on WhatsApp
Get a quote