The Anchanto Parcel Tracking platform extracts and displays complimentary event metadata directly from supported carrier tracking API payloads. This automated architecture dynamically stores and maps extended carrier information, providing deeper visibility into shipment milestones directly within the system user interface. Operations, customer support, and carrier management teams can utilize these granular details to resolve delivery queries quickly, diagnose transit exceptions, and analyze carrier messaging patterns.
User Role Permissions: Access to the Order Tracking module requires valid system credentials with adequate viewing permissions (e.g., Super Admin or regular operations operator roles).
Carrier API Capabilities: The carrier assigned to the parcel must natively transmit additional metadata tags within its XML tracking payload (e.g., Chronopost France).
Automated Framework: No manual mapping is required; the system handles incoming carrier-specific structures via an integrated scalable storage structure.
Step-by-Step Instructions
Filtering for Supported Carrier Shipments
Go to Anchanto Parcel Tracking Portal → Click Order Tracking Module from the left navigation menu → The main Track Parcels interface loads.
Go to Track Parcels Search Bar → Click Advanced Search → The system expands the advanced filter dropdown menu.
Go to Advanced Search Filters → Select Status = Delivered (or any other operational status) and choose a metadata-supported carrier from the checklist, such as Carrier = Chronopost.
Go to Advanced Search Options → Click Search → The system updates the screen to show a list of parcels matching your selected status and carrier requirements.
Accessing Enriched Carrier Event Details
Go to Parcels Search Results Grid → Click Any Shipment/Parcel Record Row (e.g., Parcel ID 52505576) → The screen redirects you to the detailed Parcel Details workspace.
Go to Parcel Details Workspace → Scroll down to Carrier Events Information Grid → The platform displays the complete log of sequential tracking updates along with a dedicated column containing extracted carrier-specific metadata.
Go to Carrier Events Information Grid → Review Extracted Event Fields → You can analyze specific, contextual data points captured directly from the carrier API payload. Depending on the carrier's transmission, these include:
Comment: Text logs or annotations inputted by the courier regarding specific delivery actions.
Scan Location / Location: The specific physical facility code or scan location where the parcel barcode was read.
Message Type: Behind-the-scenes system triggers or communication event categories.
Media Type: Media or formatting definitions related to the transmission log.
Partner Number / Order Reference: Connected vendor or enterprise business references embedded within the payload.
Common Errors:
| If you see X | Do Y |
Complimentary event details or locations show as NA or blank fields inside the grid | Verify that the specific carrier for that parcel natively transmits metadata within its API tracking tags. If the carrier provides metadata but fields remain blank, contact your carrier coordinator to check if the carrier modified their API tag nomenclature. |
| Advanced search filters return empty results or cannot locate active shipments | Expand your search boundaries. Change or widen the Select Date Range parameter type (for example, switching from Shipment Creation Date to a broader timeline) to capture older or transit-delayed records. |
| The carrier description appears unexpected or doesn't match standard milestone wordings | Review the Harmonized Code or Reason Code column within the Carrier Events Information grid. The platform automatically retains the raw carrier descriptions alongside standard system codes to assist operations teams with diagnostic tracking. |
Comments
0 comments
Article is closed for comments.