Integrations

• Carrier and parcel scan sources. Connect the provider that supplies physical milestone events. Preserve provider event identity, tracking number, event time and the correct load association. Define how repeated notifications return the existing result without creating another milestone.
• Fleet and driver authority sources. Use the external fleet identifier and driver authority reference to connect the records your team relies on for readiness and eligibility. Agree how changes reach planning before a driver or vehicle is committed.
• Recipient proof sources. Arrange the source that supplies actual delivery time and recipient proof. Retain the reference on the correct stop and attach supporting files where the operating review needs them.
• Exchange-rate source. Establish the approved read-only supply of effective rates. Agree any use of those rates explicitly while retaining the USD meaning of the load’s freight amount.

App Administrator establishes team membership and operating context. During setup, authorize each provider connection through the appropriate access controls. Transport Supervisor agrees what evidence is sufficient for scan acceptance or delivery completion. Preserve source references through the receiving procedure so an event can be traced after a delay or repeated delivery.

Rehearse a repeated scan event, a different milestone for the same tracking number and an event mapped to another organization’s load. Check recipient proof against the correct stop before using it to complete delivery. Keep provider credentials in the approved connection setup and expose only the evidence references needed for operational work.

When an action result is uncertain, inspect its receipt and local effects before another external execution. Use Correct and reconcile to agree that follow-up procedure.