CIAMA
CIAMA
English
Shipment tracking
Multi-carrier tracking: planned scope, not yet delivered.
A tracking number in one tool, an order in another, a customer waiting for an answer. The multi-carrier tracking planned for CIAMA aims to bring this information back into the context of the sale.
Logistics follows the shipment. Sales answers the customer. A shared order context helps both teams refer to the same delivery across multiple sales channels.
The channel, reference and sales information establish the context for the shipment.
The carrier and tracking number identify the parcel being reviewed.
Statuses available from the source help explain delivery progress.
A missing event is not a confirmed delivery. Read each status with its date and source.
The aim is a shared operational view, not a reinterpretation of carrier events. Missing or outdated statuses should remain identifiable, so missing data is not mistaken for a confirmed delivery.
Your deployment scope
This module is part of the planned offering and is still to be delivered. Tracking does not implicitly include label purchasing, automatic carrier selection, claims or customer notifications. These operations require separate scoping.
CIAMA is licensed software deployed on-premise. Connections, enabled features and adaptations are defined for your deployment.
Coverage is still to be defined. UPS and DPD are examples under consideration, not a list of available or certified connections.
Freshness will depend on the sources and collection approach. Universal real-time tracking is not promised.
That is the goal of scoping: bring useful information into CIAMA while preserving the responsibilities of your logistics tools. The exact flow depends on your system.
Start with that question to define order-to-shipment links, priority carriers and the events that matter to customer service and logistics.
Scope your shipment tracking ↗