Articles on: Asset management
This article is also available in:

Moving gateway from the warehouse to the client's account from the panel

Why should I not move a gateway directly from the warehouse to a customer account on the Panel?


Moving a gateway directly from the warehouse to a customer account on the Panel is not recommended for several reasons:

ID Changes:
When a gateway is moved, its identifier (ID) changes. If this move is not initiated from Fleeti Admin, you may not have the updated ID. This can lead to data corruption in our database, as the ID will no longer match the records.
No further actions will be possible on the gateway in Fleeti Admin.

Data Corruption:
If the gateway is associated with an installation or asset, moving it from the Panel can corrupt the data, as the ID will no longer be the same, and actions on the gateway will no longer be feasible due to this discrepancy.
Gateway data in Fleeti Admin will no longer be reliable or accurate.

Synchronization Issues:
It is not possible to directly synchronize the gateway's ID from Navixy to Fleeti Admin. Gateways and their clones share the same IMEI, making it difficult to differentiate them based solely on the IMEI. This complicates the synchronization process.
Data synchronization will be impossible.

Risk of Deletion:
An internal program runs daily and deletes gateways in Fleeti Admin with IDs not found in Fleeti Tracking. This poses a risk, as if the gateway was associated with an asset, it could be deleted.
The asset and gateway will be deleted, making them no longer viewable on Fleeti Admin.

Impact on Customer Experience:
You may think the customer does not see the assets because they use Fleeti Tracking and see the gateways, but:
- This is a bad practice in using our system and will greatly impact the customer when Fleeti One is launched.
- If a customer integrates the Fleeti API, direct movements can lead to errors in their data, creating inconsistencies and potential issues in the system.
- You will need to bring the gateway back to the warehouse and create a new installation for it, which can result in the loss of historical data, affecting record accuracy.
Complete reinstallation on Fleeti Admin after placing the gateway in the warehouse.

Limited Support for Gateway Linking:


If such movements are performed, support may not assist in linking the gateway, as the context for gateway linking is generally limited to replacements.

Updated on: 26/01/2024

Was this article helpful?

Share your feedback

Cancel

Thank you!