About HUB EZ
HUB EZ is the carrier identity supplied for this tracking page. Carrier-specific service, number-format, network, claims, and contact details should be taken from the official HUB EZ website rather than inferred from a tracking result.
| Field | Verified information |
|---|
| Carrier display name | HUB EZ |
| Official website | https://my.hub-ez.com/ |
| Tracking role | Use the official HUB EZ website to identify the applicable shipment service and available tracking events. |
Pro Tip: A tracking result can contain events created by a shipping partner, customs authority, or last-mile carrier. The event location and wording matter when deciding who currently has the parcel.
Quick Answer
Enter the shipment tracking number—not the marketplace order number—on the official HUB EZ website or in the 17TRACK tracking tool. If no result appears, check the characters, remove spaces or hyphens, wait for the first carrier scan, and ask the seller to confirm the correct identifier. 17TRACK is an independent tracking platform and does not transport parcels, change addresses, issue refunds, or approve claims.
How to Track HUB EZ Packages
Use either the official HUB EZ tracking route or 17TRACK. The official route is the first place to check for carrier-specific instructions; 17TRACK can help consolidate events when a shipment involves more than one logistics provider.
- Copy the tracking number from the seller’s dispatch email, shipping label, receipt, or shipment page.
- Enter the number on the official HUB EZ website, or use 17TRACK.
- Compare the latest event, event location, and date with the delivery address and order details.
- If the result is empty, verify the identifier with the seller before opening a delivery dispute.
Tracking Statuses and Meanings
Tracking status wording differs by service. The practical distinction is whether a label was created, the parcel received a physical scan, the parcel is moving, or a delivery exception requires action.
Status Quick Lookup
| Status | Lifecycle stage |
|---|
| Label created or pre-shipment | Shipment preparation |
View all details for pre-shipment status| What it means | Shipment data may exist before a physical acceptance scan. |
|---|
| Responsible party | The seller, label creator, or collecting logistics provider should confirm physical handover. |
|---|
| Next step | Allow time for the first scan and contact the seller if the shipment was stated as dispatched. |
|---|
|
| In transit | Movement between processing points |
View all details for in-transit status| What it means | The latest recorded event indicates movement or processing, but tracking is not a continuous location feed. |
|---|
| Responsible party | The provider named in the latest event is the best starting point for shipment-specific questions. |
|---|
| Next step | Review the latest scan and estimated delivery information supplied for the shipment. |
|---|
|
| Delivered | Delivery event recorded |
View all details for delivered status| What it means | A delivery scan was recorded; the parcel may have been left at an approved location or accepted by another person. |
|---|
| Immediate action | Check the delivery location, household members, reception desk, neighbors, and any proof-of-delivery information. |
|---|
| Escalation | Contact the delivery provider and seller promptly if the parcel remains missing. |
|---|
|
Services and Delivery Times
A delivery estimate depends on origin, destination, service selection, handoffs, address quality, weekends, holidays, weather, and customs where applicable. An estimate is not the same as a guaranteed delivery commitment.
Service Comparison
| Service | Best use |
|---|
| Shipment service selected by the sender | Use the service shown on the label, receipt, or seller dispatch record. |
Delivery Time
| Timing basis | How to interpret it |
|---|
| Shipment-specific estimate | Treat the displayed date or window as an estimate and recheck after a new scan or exception. |
Common Tracking Problems and Solutions
Start with the latest event and the party named in that event. The sender should normally handle merchant-side delivery disputes, while the recipient can check the address, delivery location, local notices, and customs requests.
Problem & Solution
| Problem or status | Check first |
|---|
| Invalid number or no result | Compare every character with the label and confirm that it is a tracking number rather than an order number. |
View all details for an invalid or inactive number| Immediate action | Remove accidental spaces or punctuation, then ask the seller to confirm the identifier and dispatch status. |
|---|
| Possible cause | The label may have been created before acceptance, or the shipment may be handled under another provider’s identifier. |
|---|
| Escalation | Escalate to the seller when the promised dispatch period has passed or the order protection deadline is approaching. |
|---|
|
| Long period without an update | Check the date and location of the latest physical scan. |
View all details for a shipment with no recent update| Possible cause | Some transport legs are visible only when a facility, partner, customs office, or delivery provider submits a new event. |
|---|
| Recipient action | Check for customs messages, address issues, local delivery notices, and the seller’s stated delivery window. |
|---|
| Sender action | Ask the shipping provider about an inquiry or investigation where the applicable service rules permit it. |
|---|
|
| Delivered but not received | Check the entrance, mailbox, safe place, household, reception desk, and nearby addresses. |
View all details for delivered but missing shipments| Next action | Review proof-of-delivery information, contact the delivery provider, and notify the seller with the order record. |
|---|
| Information to provide | Tracking number, delivery address, delivery scan date, purchase record, and photographs or security evidence where relevant. |
|---|
| Refund boundary | 17TRACK cannot approve a refund or determine whether a shipment was lost. |
|---|
|
Tracking API
// Carrier official tracking API:
// Current public official tracking API documentation for HUB EZ was not established
// from the available evidence. Obtain current credentials and endpoint details
// directly from HUB EZ before implementing an integration.
// 17TRACK API:
POST https://api.17track.net/track/v2.4/register
Headers:
17token: YourKey
Content-Type: application/json
Body:
[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]
// Confirm the current HUB EZ carrier code in 17TRACK documentation
// before sending production requests.
Sources & References
17TRACK is an independent tracking platform and is not affiliated with HUB EZ.
