Choose shipment tracking software by testing the journeys your customers and operations team handle every week. Start with representative orders, agree what a successful result looks like and ask each supplier to show the same cases. Keep the supplier’s stated scope, observed evidence and remaining questions in separate records.
Shipment tracking supplier scorecard
Complete one copy per supplier using the same records. Add your own result and named owner beside each test; leave unsupported claims open for review.
| Criterion | Evidence to request | Pilot test |
|---|---|---|
| Lane coverage | Named service, destination, event source and known coverage gaps. | Trace the international handoff and verify both parcel references. |
| Order and parcel model | A view linking one order to its individual parcels and histories. | Deliver one parcel while the second remains in transit. |
| Event quality | Original event, source time zone and readable status together. | Inspect a repeated event and an update received out of sequence. |
| Customer communication | Localized page and message examples with a documented trigger. | Read the address exception and identify the customer’s next action. |
| Operational ownership | Investigation owner, handoff process and escalation contact. | Ask support to take a missing-update case through its next review. |
| Commercial scope | Written inclusions, charging unit, dependencies and support terms. | Reconcile the proposed pilot with the quote and unresolved items. |
Define the job your team is buying for
Write down who needs the information and the decision it supports. Customer tracking, an operations investigation and a support reply require different views of the same parcel. Establish your first market, customer language and order patterns. If your main requirement is route planning or driver dispatch, assess that requirement separately from the post-purchase tracking journey.
Ask for evidence on your actual shipping lanes
Give each supplier a redacted set of order references, parcel identifiers and partner handoffs. Ask which events are available for each lane, where they come from and how gaps are identified. Record the coverage claimed in the proposal beside what the evaluation demonstrates. A carrier appearing on a list leaves questions about a particular service, destination and handoff.
Compare the same four journeys
Prepare an expected result before the demonstration. For each case, record the event shown, the customer explanation, the next owner and any missing evidence. Ask the supplier to identify which parts use sample records and which have been verified against an available production source.
- Normal delivery: follow one parcel from acceptance to completion.
- Split order: keep a delivered parcel separate from one still travelling.
- International handoff: preserve the original and local references when the delivery partner changes.
- Address exception: show the confirmed issue, the customer’s action and the team responsible for follow-up.
Inspect event quality and the customer explanation
Check the original event, its time zone and the readable milestone together. Add a repeated event and a late-arriving update to the evaluation. Ask how the team would review a confusing sequence. Read the tracking page and proposed message in the customer’s language. An arrival date needs an identified source, and a missing scan needs a clear investigation route.
Make scope and responsibilities comparable
Ask for a written account of data preparation, connection availability, customer wording, message delivery and support responsibilities. Record the charging unit, included work and conditions that change the quote. Assign an owner and due date to every unresolved dependency. In a JetonTrack discussion, use the interactive example to explain your requirements, then confirm the production scope for your operation.
Use the scorecard to decide the next step
Copy the table into your evaluation notes and add columns for supplier claim, observed result, gap, owner and review date. Keep the original evidence with each result. Mark an untested requirement as pending. Before approving a pilot, agree who accepts the customer journey and what happens if an important lane or exception remains unresolved.
Common questions
Should carrier count decide the shortlist?
Use your routes and services to build the shortlist. Ask for evidence of the events and handoffs you need, then record gaps that could affect your customers.
What does the JetonTrack demo prove?
It shows illustrative customer and team workflows with sample records. Confirm available connections, data sources, communication arrangements and operating responsibilities for your proposed production scope.