Definition
A GPS mirror account is read-only access to the carrier's satellite tracking platform so the shipper or 3PL can see units on their trips without owning hardware or changing the carrier's configuration.
Without a mirror, tracking is a phone call. With a mirror and no rules, it is decorative telemetry.
In Laredo and the Bajío, learning at 8 minutes vs 2 hours is OTIF — or a detention dispute.
Opening the portal by hand is still a human bridge; the agent closes tracking with a file.
What GPS mirror account means in practice
The carrier creates the limited user; you or the agent read position, history, and (if available) temperature/events, and match them to the trip-ID appointment and geofence.
It is not “your GPS”: you do not install devices or edit carrier geofences. It is also not generic track-and-trace without access: without a mirror (or API), you only have WhatsApp. Neighbors: computer use, geofencing, POD.
Why it matters (shipper / 3PL / carrier)
1.Shipper / AP
Evidence for On Time, diversion, and detention for OTIF and pre-pay disputes — the same GPS leg required by invoice audit.
2.3PL / control tower
One multi-portal view without headcount linear to 15+ distinct carrier logins.
3.Carrier
Shares visibility without giving away the carrier GPS or edit rights; fewer “where is it?” calls.
When it applies (and when it does not)
It fits Mexico–US multi-carrier networks (spot + contract), strict appointment lanes, high-value freight, or when AP requires a geofence for detention/accessorials.
Having a login is not enough: without alert SLA, geofence, and owner, the mirror does not save the shipment. If the carrier already exposes a stable API to the TMS, prefer integration; the mirror covers the rest of the network.
| Signal | With a governed mirror | No mirror / WhatsApp only |
|---|---|---|
| Visibility | Position on carrier portal | Call or late paste |
| Alert | Minutes (target <10) | Hours or next day |
| OTIF / detention | Defensible timestamp + geofence | Dispute by “version” |
| Pre-pay audit | GPS as 4th match source | AP pays on faith |
| Escalation | Agent + exception owner | Tower as endless bridge |
Checklist: mirror account ready to run
1.Read-only
No editing fleet, geofences, or carrier users.
2.Scoped to the trip
Units on the shipment — not the whole carrier fleet.
3.Credential rotation
Password/MFA and offboarding when the carrier changes.
4.Geofence + appointment
Origin, destination, and OTIF windows on the trip ID.
5.SLA <10 min
Who acts and in how many minutes on a diversion.
6.KPI
% trips with active mirror; median minutes to first alert.
Short flow: from mirror to alert
Request access
Read-only user
Bind trip
Unit + geofence
Watch
Portal or agent
Alert
Exception with owner
Common mistakes in Mexico
1.Asking for edit rights
The carrier rejects it or revokes access; the standard is read-only mirror.
2.Having a mirror and not alerting
Without a <10 min SLA the map does not protect OTIF. Playbook: GPS 10-min alert.
3.Credentials in chat
Access leakage and no rotation when the carrier changes.
4.GPS detached from the file
If position is not hung off the trip ID, it helps neither AP nor POD.
OCL and the shipment file (light)
OCL uses computer-use agents to enter mirror accounts, read position, and raise alerts with a file — without every carrier API or day-one TMS replacement.
OCL can stamp invoices and Carta Porte. Mirror GPS feeds tracking and pre-pay matching; tax issuance stays with the carrier and its PAC.
Sources and further reading
- Guide: GPS mirror accounts.
- Playbook: GPS 10-min alert.
- Pillar: computer use in logistics · glossary computer use.
- Audit: CFDI + CP + GPS + POD.
- POD: what is POD · shipper convention.
- Thesis: fake freight digitization.
Key takeaways5 points
- GPS mirror account = read-only user on the carrier tracking portal.
- It does not replace the carrier GPS: it shares visibility without your hardware or editing their fleet.
- The value is not the map: it is a useful alert in <10 minutes hung off the trip ID.
- On multi-carrier Mexico networks there is rarely one API; computer use operates dozens of portals.
- Geofence + appointment + exception owner turn telemetry into OTIF and detention evidence.
Want <10 min GPS alerts without an API?
Frequently asked questions
Read-only access to the carrier's satellite tracking portal so the shipper or 3PL can see units on their trips without owning hardware or changing the carrier's configuration.
No. The carrier keeps its platform; the mirror only shares visibility. You do not install devices or edit their fleet.
Multi-carrier networks rarely share one tracking API. Without a mirror (or integration), tracking lives in WhatsApp and alerts arrive late.
Early alerts protect On Time; history + geofence support detention and the GPS leg of pre-pay audit with CFDI, Carta Porte, and POD.
No. The mirror coexists with your TMS/tower; an agent can operate it with computer use. See traditional TMS vs OCL.
Yes. OCL can stamp invoices and Carta Porte; it also runs tracking and verification with a file.