Anchanto Parcel Tracking provides integrated Estimated Delivery Date (EDD) calculations, real-time SLA status tracking, and carrier delivery performance analytics. The system calculates precise delivery expectations upon carrier check-in by evaluating route commitments against destination-country business calendars. This guide details how to view parcel-level delivery insights, filter shipments by SLA status, and evaluate carrier service-level metrics.
Prerequisites:
Permissions: Access to the Parcel Tracking module and the Business Dashboard / Analytics view.
Backend Master Data Setup: Carrier and service-type master data, SLA transit time commitments (minimum/maximum transit days per route), and destination business calendars (weekends and public holidays) must be configured by your Anchanto account or implementation team via master templates.
Scope Limitations: SLA calculations apply exclusively to outbound shipments. Return-journey SLA monitoring, automated breach push notifications, and self-service calendar configuration are currently not supported.
Understanding the EDD and SLA Calculation Logic
The delivery calculation engine computes expected delivery timelines using a five-step business-day-aware workflow:
Identify the Start-Clock Event: The system detects the initial qualifying scan event when a parcel enters the carrier network (e.g., Carrier Check-in, Pickup, or Handover).
Identify the Applicable SLA: The calculation engine evaluates shipment attributes using progressive precision matching. It checks parameters in the following hierarchy:
{Carrier} -> {Service Type} -> {Origin/Destination Country} -> {Origin/Destination City} -> {Origin/Destination Postcode}
The system applies the most specific matching rule first, falling back to broader route or carrier rules only when detailed postcode-level rules are unavailable
Apply the Destination Business Calendar: The engine checks the destination country's working-calendar rules, automatically excluding weekends, national holidays, and configured operational closures.
Calculate the Delivery Window: Minimum and maximum SLA business days are added to the start-clock timestamp to establish the delivery window. The maximum expected date serves as the Estimated Delivery Date (EDD).
Evaluate SLA Status:
In SLA: The shipment is actively progressing or was delivered within the configured maximum SLA business days.
Missed SLA: The actual business-day transit duration exceeded the maximum SLA threshold upon delivery or stop-clock event.
Viewing Estimated Delivery Dates on Parcel Details
Go to Parcel Tracking → Click Track Parcels → Select Parcels. Go to Search Bar → Type [Tracking Number / Package ID] → Click Search.
Go to Search Bar → Type [Tracking Number / Package ID] → Click Search. Go to Search Results Table → Click [Shipment Tracking ID] → System opens the Parcel Details page.
Go to Search Results Table → Click [Shipment Tracking ID] → System opens the Parcel Details page.
Go to Insights Section → Review Creation Date, Delivery Time, SLA Status, Estimated Delivery Date, and Route Visualization.
Filtering Shipments by SLA Status in Advanced Search
Go to Parcel Tracking → Click Track Parcels → Click Advanced Search.
Go to SLA Status Dropdown → Select [In SLA] or [Missed SLA].
Go to Additional Filter Fields → Select optional criteria (Carrier, Service Type, Store Name, Origin, Destination, or Date Range).
Go to Action Buttons → Click Search → System displays the filtered shipment population matching your SLA selection.
Analyzing Carrier Delivery Performance
Go to Business Dashboard → Click Analytics → Select Carrier Performance Analysis.
Go to On-Time Delivery % by Carrier Widget → Locate [Carrier Name] → Review Overall Delivery Rate Percentage.
Go to Carrier Row → Click [Carrier Name] → System updates the On-Time Delivery % by Service Type panel.
| If the system shows this error | Follow these steps to fix it |
Estimated Delivery Date is blank or missing on the Parcel Details page.
| Verify that an SLA commitment rule is configured for the shipment's carrier, service type, and route. If SLA master data has not been submitted to Anchanto for backend configuration, the system cannot derive an EDD. Contact your implementation manager to submit the required SLA template. |
Shipment EDD extended beyond standard calendar count (e.g., 3-day SLA takes 5 days). | Check if the transit window overlaps with destination-country weekends or public holidays. The engine automatically excludes non-working days based on the destination business calendar. |
SLA performance data does not appear in the Carrier Performance Analysis dashboard. | Confirm that carrier scan events (Pickup, Check-in, Delivery) are being successfully ingested. SLA status calculation requires valid start-clock and stop-clock event payloads. |
Newly provided SLA or business calendar master data is not reflecting on recent shipments. | Master data updates execute on automated processing cycles. Allow the system to complete its next scheduled processing cycle. If issues persist, verify with Anchanto support that the backend update job executed without data formatting errors. |
Comments
0 comments
Article is closed for comments.