About Route
Route is a shopping and post-purchase package-tracking platform that connects participating merchant orders with shipment updates. Route is not the seller, carrier, payment processor, or universal owner of every order shown in its app.
Official website: https://route.com/. Tracking may be available through the Route app, a Route tracking link, the merchant’s order page, the carrier’s website, or 17TRACK when a carrier tracking number is available.
| Order party | Primary role |
| Route | Post-purchase tracking and, where applicable, package-protection services. |
View all details for Route| What it controls | Its own app, tracking presentation, and applicable Route service workflows. |
|---|
| What it cannot control | Merchant fulfillment, carrier scans, delivery addresses, carrier routes, or a merchant’s refund decision. |
|---|
| Why it matters | A Route screen can summarize shipment data without replacing the merchant or carrier’s records. |
|---|
|
| Merchant or store | Accepts the order, fulfills the goods, and handles most order, return, and refund questions. |
View all details for merchant or store| What it controls | Order confirmation, inventory, address-change policy, dispatch, returns, and refund authorization. |
|---|
| What it cannot control | Every carrier scan or the physical movement of a parcel after handoff. |
|---|
| Why it matters | The merchant is normally the first contact for an order that has not shipped or requires cancellation. |
|---|
|
| Carrier | Transports the shipment and creates operational tracking events. |
View all details for carrier| What it controls | Pickup, sorting, transit, delivery attempts, and delivery scans. |
|---|
| What it cannot control | Merchant refunds, product quality, or the original order record. |
|---|
| Why it matters | A carrier can investigate a physical delivery event, but usually cannot change the merchant order. |
|---|
|
| Buyer | Provides order information, receives the shipment, and starts eligible merchant or Route workflows. |
View all details for buyer| What to retain | Order email, order number, tracking number, seller name, delivery address, photos, and return documents. |
|---|
| Important limitation | Access to Route does not by itself prove that a merchant accepted a return or approved a refund. |
|---|
|
| 17TRACK | Independent tracking platform for available carrier tracking numbers. |
View all details for 17TRACK| Can do | Accept a carrier tracking number, identify a supported carrier, and display available events. |
|---|
| Cannot do | Open private Route or merchant order details, modify an order, contact a seller, or issue a refund. |
|---|
|
Quick Answer
To track a Route order, open the Route app or the tracking link supplied by the participating merchant, then open the shipment details. If a carrier tracking number is displayed, you can also enter it on the carrier’s website or 17TRACK.
A Route order number identifies the purchase; it is not necessarily a carrier tracking number. If no tracking number appears, the merchant may still be preparing the order, or the carrier may not have posted its first scan. Contact the merchant for order and shipping questions, the carrier for a physical delivery event, and Route for an issue handled through an applicable Route service workflow.
Pro Tip: 17TRACK can track an available carrier number, but it cannot retrieve private Route order data or initiate a merchant refund.
How to Track Route Orders
Start with the merchant’s order record or Route’s shipment view. Sign in where required, open the order, select shipment or tracking details, and check whether the order has multiple shipments.
| Tracking path | Use when |
| Route app or Route tracking link | The order is connected to Route. |
View all details for Route app or Route tracking link| Identifier needed | Access to the applicable Route account, email, or tracking link. |
|---|
| What you can see | Available shipment events and information supplied by the merchant or carrier. |
|---|
| Next step | Open the shipment and copy the carrier number if one is shown. |
|---|
| Limitation | Not every merchant order is connected to Route and some events may update after a carrier scan. |
|---|
|
| Merchant account or order email | The Route view is unavailable or the order is not linked. |
View all details for merchant account or order email| Identifier needed | Merchant order number, email address, or guest-order lookup details. |
|---|
| What you can see | Order status, shipment links, seller information, and return options when supplied by the merchant. |
|---|
| Next step | Use the shipment link or copy the carrier tracking number. |
|---|
| Limitation | An order number normally works only in the merchant’s own system. |
|---|
|
| Carrier website or 17TRACK | A carrier tracking number is available. |
View all details for carrier website or 17TRACK| Identifier needed | Carrier tracking number, not a Route order number. |
|---|
| What you can see | Available carrier scans, routing events, delivery attempts, and delivery status. |
|---|
| Next step | Compare the latest event with the merchant order record. |
|---|
| Limitation | Tracking data cannot approve a return, change an address, or determine refund eligibility. |
|---|
|
| Guest, gift, or recipient route | Someone else placed the order or no Route account exists. |
View all details for guest, gift, or recipient route| Identifier needed | The purchaser’s order email, merchant tracking link, or carrier tracking number. |
|---|
| Next step | Ask the purchaser or merchant to share the shipment link or number. |
|---|
| Limitation | The recipient may not be able to access private order, payment, return, or refund details. |
|---|
|
Order Numbers, Tracking Numbers and Where to Find Them
Use the identifier in the system that issued it. A Route or merchant order number can locate a purchase in that system, while a carrier tracking number is the identifier normally accepted by 17TRACK.
| Identifier type | Where users find it |
| Merchant or Route order number | Confirmation email, merchant order page, or connected Route order view. |
View all details for merchant or Route order number| Example | Use only the number supplied by the merchant; do not infer a format. |
|---|
| Issuer | Merchant order system or Route-connected order record. |
|---|
| Can 17TRACK use it? | Usually no. |
|---|
| What it proves | It identifies an order record, not carrier custody or delivery. |
|---|
|
| Carrier tracking number | Shipment details, dispatch email, Route tracking view, or carrier label. |
View all details for carrier tracking number| Example | Use the actual number supplied for the shipment; never use another customer’s number. |
|---|
| Issuer | Origin carrier, destination carrier, or logistics provider. |
|---|
| Can 17TRACK use it? | Often yes, when the carrier and number are supported. |
|---|
| What it proves | It links to carrier events; it does not prove refund approval or product condition. |
|---|
|
| Return tracking number | Return label, return receipt, or carrier return record. |
View all details for return tracking number| Issuer | The return-label carrier or merchant return system. |
|---|
| Can 17TRACK use it? | Yes, when it is a supported carrier number. |
|---|
| What it proves | Transit of the return parcel; it does not prove the merchant accepted or inspected it. |
|---|
|
| Seller reference or marketplace ID | Seller message, marketplace order page, or invoice. |
View all details for seller reference or marketplace ID| Issuer | The merchant, seller, or marketplace. |
|---|
| Can 17TRACK use it? | Not unless it is also a recognized carrier tracking number. |
|---|
| What it proves | It identifies a commercial transaction or seller record, not a physical parcel. |
|---|
|
Fulfillment, Sellers and Carriers
Route does not appear to be a conventional retailer or marketplace that fulfills every item itself. The merchant, seller, warehouse, and carrier can vary by the original store and destination.
| Fulfillment model | Who ships it |
| Merchant warehouse | The original store or its logistics provider. |
View all details for merchant warehouse| Tracking updater | The carrier posts scans; Route may display data received through the merchant or carrier connection. |
|---|
| Delivery issue owner | Carrier for a transport event and merchant for order resolution. |
|---|
| Check first | Merchant dispatch confirmation and the carrier number. |
|---|
|
| Third-party seller or cross-border fulfillment | The seller or an export and delivery partner. |
View all details for third-party seller or cross-border fulfillment| Tracking updater | Origin, line-haul, destination, and last-mile carriers may each add events. |
|---|
| Delivery issue owner | Contact the seller or merchant for order action and the relevant carrier for a scan investigation. |
|---|
| Check first | Whether the number is an origin number, a last-mile number, or a replacement number. |
|---|
|
| Split shipment | One order can be dispatched in separate parcels. |
View all details for split shipment| Tracking updater | Each parcel’s carrier updates its own tracking record. |
|---|
| Delivery issue owner | The merchant handles a missing item; the carrier handles a parcel event. |
|---|
| Check first | Open every shipment line in the merchant or Route order view. |
|---|
|
| Store pickup or digital order | The store, pickup operator, or digital-service system. |
View all details for store pickup or digital order| Tracking updater | A pickup-ready or service system may update the order rather than a parcel carrier. |
|---|
| 17TRACK limitation | 17TRACK cannot create parcel scans for orders that have no carrier shipment. |
|---|
| Check first | The merchant’s pickup or service instructions. |
|---|
|
Tracking Statuses and Meanings
| Status shown | Lifecycle stage |
| Order confirmed or processing | Order accepted or being prepared. |
View all details for processing| Usually means | The purchase exists, but a carrier handoff may not have occurred. |
|---|
| Responsible now | Merchant or seller. |
|---|
| Customer action | Check the stated processing information and contact the merchant if the order appears overdue. |
|---|
|
| Label created or shipped | Dispatch preparation or carrier handoff stage. |
View all details for shipped| Usually means | A label or dispatch event exists; it may not yet mean the carrier has completed an acceptance scan. |
|---|
| Responsible now | Merchant for handoff confirmation; carrier after acceptance. |
|---|
| Customer action | Check the carrier page and wait for the first physical scan before treating it as in transit. |
|---|
|
| In transit or out for delivery | Carrier movement or final-mile delivery. |
View all details for in transit or out for delivery| Usually means | The carrier has posted movement or has assigned the parcel to a delivery route. |
|---|
| Responsible now | Carrier and local delivery network. |
|---|
| Customer action | Monitor the latest event and follow any delivery-attempt instructions. |
|---|
|
| Delivered, exception, return, or refund | Completion or an unresolved exception. |
View all details for delivered, exception, return, or refund| Usually means | Delivered is a carrier event; return and refund are separate merchant workflows. |
|---|
| Responsible now | Carrier for delivery evidence, merchant for return or refund decisions. |
|---|
| Customer action | Keep the event record and escalate through the correct party without assuming a delivery scan equals refund approval. |
|---|
|
Delivery Time and Delay Factors
Route does not set one universal delivery time for all connected orders. The merchant’s delivery estimate, selected service, origin, destination, inventory position, and carrier events control the applicable expectation.
| Scenario | Primary timing source |
| Domestic shipment | Merchant estimate and selected carrier service. |
View all details for domestic shipment| Possible delays | Warehouse processing, weekends, peak volume, weather, address issues, and carrier network disruption. |
|---|
| When updates appear | After the carrier or logistics provider creates and processes an event. |
|---|
| Contact first | Merchant for an order estimate; carrier for an active delivery exception. |
|---|
| Caveat | An estimated date is not automatically a delivery guarantee. |
|---|
|
| Cross-border shipment | Merchant estimate plus origin, international, customs, and destination-carrier events. |
View all details for cross-border shipment| Possible delays | Export processing, customs review, duties or documentation, carrier handoff, and local delivery capacity. |
|---|
| When updates appear | Events may pause while the parcel changes networks or awaits a scan. |
|---|
| Contact first | Merchant for documentation or order questions; carrier or customs channel for an active clearance request. |
|---|
| Caveat | One shipment can show separate origin and last-mile identifiers. |
|---|
|
| Preorder, backorder, or split shipment | Merchant inventory and dispatch information. |
View all details for preorder, backorder, or split shipment| Possible delays | Item availability or different fulfillment locations. |
|---|
| When updates appear | Each parcel can update independently after dispatch. |
|---|
| Contact first | Merchant or seller. |
|---|
| Caveat | Do not assume one delivered parcel completes every item in the order. |
|---|
|
Common Problems and Next Steps
| Problem shown | Check first |
| No tracking number | Merchant dispatch email, Route shipment details, and order status. |
View all details for no tracking number| Likely cause | The order is still processing or a label has not been shared. |
|---|
| Immediate action | Ask the merchant whether the parcel has been handed to a carrier. |
|---|
| Escalate when | The merchant’s stated processing or dispatch expectation has passed. |
|---|
| Contact | Merchant or seller, not 17TRACK. |
|---|
|
| Tracking number not working | Characters, carrier selection, and first-scan status. |
View all details for tracking number not working| Likely cause | Label created before acceptance, incorrect number, unsupported carrier, or delayed data exchange. |
|---|
| Immediate action | Copy the number again and check the carrier or merchant page. |
|---|
| Escalate when | The merchant confirms dispatch but no carrier record appears after a reasonable processing interval. |
|---|
| Contact | Merchant first; carrier if its system recognizes the number. |
|---|
|
| Package stuck, delayed, or customs hold | Latest event, event location, and any carrier request. |
View all details for package stuck, delayed, or customs hold| Likely cause | Network congestion, handoff, customs processing, weather, address issue, or missing documentation. |
|---|
| Immediate action | Follow the carrier’s request and ask the merchant about replacement or escalation options. |
|---|
| Contact | Carrier for transport or clearance instructions; merchant for order remedies. |
|---|
|
| Delivered but not received | Delivery location, household, reception desk, neighbors, photo, and proof of delivery. |
View all details for delivered but not received| Immediate priority | Check safe locations, household members, building staff, neighbors, and the carrier’s delivery photo or event details. |
|---|
| Next action | Report the discrepancy to the carrier and merchant promptly using the delivery evidence. |
|---|
| Route limitation | A delivered scan does not by itself guarantee a refund or establish who is liable. |
|---|
|
| Wrong, damaged, or missing item | Order contents, photos, packing materials, and every shipment record. |
View all details for wrong, damaged, or missing item| Immediate action | Document the condition and contact the merchant or seller through its support or order channel. |
|---|
| Split shipment check | Confirm whether another shipment remains in transit before reporting an item as missing. |
|---|
| Contact | Merchant or seller for replacement, return, or refund eligibility. |
|---|
|
| Return not updating or refund pending | Return tracking, acceptance scan, return authorization, and merchant case record. |
View all details for return not updating or refund pending| Important distinction | Return tracking shows parcel movement; refund status shows the merchant or payment channel’s financial workflow. |
|---|
| Immediate action | Send the merchant the return number and proof of drop-off. |
|---|
| Contact | Merchant first, then the payment channel only when its dispute rules apply. |
|---|
|
Returns, Exchanges and Refunds
Start a return, exchange, cancellation, or refund request with the original merchant unless the specific Route service or protection workflow expressly provides another route. 17TRACK can show return-carrier events but cannot approve a refund.
| Scenario | Where to start |
| Return or exchange | Original merchant order page, returns center, or support channel. |
View all details for return or exchange| Identifier needed | Order number and, when issued, return authorization or label number. |
|---|
| Return tracking | Keep the carrier return number and drop-off receipt; enter it into 17TRACK when supported. |
|---|
| Refund dependency | Merchant receipt, inspection, policy conditions, and payment processing may affect the outcome. |
|---|
| Limitation | Route tracking does not replace the merchant’s return policy. |
|---|
|
| Lost, damaged, or stolen package | Carrier and merchant; review any applicable Route protection workflow. |
View all details for lost, damaged, or stolen package| Identifier needed | Order number, tracking number, delivery evidence, and photographs where relevant. |
|---|
| Who can start it | The buyer or eligible account holder, using the merchant or applicable Route workflow. |
|---|
| Refund dependency | Eligibility depends on the applicable terms and review; no outcome should be assumed from tracking alone. |
|---|
|
| Refund status | Merchant order support and the original payment channel. |
View all details for refund status| Identifier needed | Order number, return case, refund confirmation, or payment reference. |
|---|
| Return tracking | Useful only to show movement or delivery of the return parcel. |
|---|
| Important limitation | 17TRACK cannot see a private payment ledger or confirm that a refund was approved. |
|---|
|
Customer Service and Escalation
Use the party that owns the unresolved event. Before contacting support, prepare the order number, carrier tracking number, seller name, account email, delivery address, latest event, photographs, invoice, return label, and any case or refund reference.
| Channel | Best for |
| Route Help Center or Route support | Questions about Route’s app, tracking presentation, or an applicable Route service. |
View all details for Route Help Center or Route support| Where to access | Route’s official website and its linked support resources. |
|---|
| Prepare | Route account email, order information, screenshots, and the applicable shipment or protection details. |
|---|
| Limitation | Route support cannot act as the merchant for ordinary cancellations, product returns, or merchant refunds. |
|---|
|
| Original merchant or seller | Order not shipped, wrong item, cancellation, return, refund, or address issue. |
View all details for original merchant or seller| Where to access | Merchant order page, help center, return center, or seller message channel. |
|---|
| Prepare | Order number, item details, delivery address, tracking history, photographs, and return evidence. |
|---|
| Limitation | The seller may need to coordinate with the carrier before offering an order remedy. |
|---|
|
| Carrier | Delivery attempt, address correction request, physical loss, or delivery scan dispute. |
View all details for carrier| Where to access | Carrier website using the shipment’s tracking number. |
|---|
| Prepare | Tracking number, latest event, address, delivery instructions, and proof of delivery. |
|---|
| Limitation | Carrier support generally cannot authorize a merchant refund or change the product order. |
|---|
|
Seller, Marketplace and Buyer Responsibility
Route is not presented here as a marketplace for independent sellers. When a Route-connected order comes from a marketplace or third-party merchant, responsibility remains divided among that platform, its seller, the carrier, and the buyer.
| Issue | First owner to check |
| Seller has not shipped or supplied wrong tracking | Seller or original marketplace order support. |
View all details for seller shipping issue| Platform role | May display the order and provide a seller-contact or dispute process. |
|---|
| Carrier role | Can validate a recognized tracking record. |
|---|
| Buyer action | Keep seller messages, order confirmation, and the incorrect or inactive number. |
|---|
| Evidence | Timestamped order status, dispatch promise, messages, and tracking screenshots. |
|---|
|
| Item not received or delivery scan conflict | Carrier for scan evidence and seller or marketplace for remedy. |
View all details for item not received or delivery scan conflict| Platform role | May administer buyer protection or dispute rules, if applicable. |
|---|
| Seller role | Responds to the order claim and may coordinate replacement or refund. |
|---|
| Buyer action | Check delivery locations and preserve proof of delivery or non-receipt evidence. |
|---|
| Limitation | A Route or carrier status alone does not decide a marketplace dispute. |
|---|
|
| Return dispute or refund after delivery failure | Original seller or marketplace case channel. |
View all details for return dispute or refund| Carrier role | Provides movement and delivery evidence for the parcel. |
|---|
| Buyer action | Submit return tracking, photographs, seller correspondence, and case identifiers. |
|---|
| Evidence to keep | Return receipt, delivery scan, merchant policy, and all case decisions. |
|---|
|
Brand App, Notifications and Delivery Options
Route provides an app-based post-purchase experience for connected orders. The exact notification and delivery options depend on the merchant, carrier, destination, and the shipment data available to Route.
| Feature | Use case |
| Route app tracking | Review connected purchases and available shipment events. |
View all details for Route app tracking| Where to enable | Use the official Route app and its account or order-connection flow. |
|---|
| When it appears | After a participating merchant order is connected and shipment data is available. |
|---|
| What it can change | How the shipment is viewed and which available notifications are received. |
|---|
| Limitation | It does not change carrier routing, merchant fulfillment, or refund decisions. |
|---|
|
| Email or push notification | Receive updates when the connected order or shipment produces an available event. |
View all details for email or push notification| Where to enable | Notification settings in the applicable Route or merchant account, where offered. |
|---|
| When it appears | Timing depends on the underlying merchant or carrier event. |
|---|
| Limitation | A notification is not a new carrier scan and may not include private order details. |
|---|
|
| Delivery instructions, reschedule, pickup, or locker | Only when the merchant or carrier makes that option available. |
View all details for delivery instructions, reschedule, pickup, or locker| Where to enable | Usually the carrier or merchant delivery page, not a general Route setting. |
|---|
| What it can change | Only the delivery preference allowed by that carrier or merchant. |
|---|
| Limitation | Do not assume Route can reschedule, redirect, release a signature, or create a pickup order. |
|---|
|
Business, Seller or Developer API
A current public official Route order-tracking API was not confirmed for this page. Merchants should use Route’s current business documentation or support channels for integration questions and should not infer an API from the consumer tracking experience.
| Option | Primary use |
| Route merchant integration | Connect eligible merchant order and shipment information to Route. |
View all details for Route merchant integration| Provider | Route. |
|---|
| Coverage | Depends on the merchant relationship, supported data, and current Route documentation. |
|---|
| Access | Confirm current requirements directly with Route. |
|---|
| Limitation | This page does not claim an undocumented endpoint, credential scheme, or webhook contract. |
|---|
|
| 17TRACK API | Register and query carrier tracking numbers independently of a Route order. |
View all details for 17TRACK API| Coverage | Carrier tracking events for numbers supported by 17TRACK. |
|---|
| Authentication | 17token header as specified in the current 17TRACK documentation. |
|---|
| Primary limitation | It requires a carrier tracking number, not a Route order number, invoice number, or payment reference. |
|---|
| Documentation | 17TRACK API documentation. |
|---|
|
FAQ
Basic FAQs
1. How do I track my Route order?Open the Route app or the merchant’s Route tracking link and select the shipment details. If a carrier number appears, it can also be checked on the carrier website or 17TRACK.
2. Where can I find my Route tracking number?Look in the merchant’s shipping email, order details, or the connected Route shipment view. The carrier number may appear only after dispatch information is supplied.
3. Can I track a Route order number on 17TRACK?Usually not. A Route or merchant order number identifies the purchase, while 17TRACK normally requires the carrier tracking number.
4. What should I do if my Route order has no tracking number?Check whether the order is still processing and then contact the original merchant. The merchant must confirm dispatch or provide the carrier number.
5. Why is my Route tracking number not updating?The label may exist before the carrier’s first acceptance scan, or data may be delayed during a carrier handoff. Verify the number with the merchant and carrier.
6. How long will my Route order take to arrive?There is no single Route delivery time for all connected orders. Use the original merchant’s estimate and the carrier events for that specific shipment.
7. What if my Route package says delivered but I cannot find it?Check the delivery location, household members, building staff, neighbors, and proof of delivery, then contact the carrier and merchant. A delivered scan does not automatically guarantee a refund.
8. Can I track a Route return?Yes, enter the return carrier’s tracking number into the carrier website or 17TRACK when supported. Return movement is separate from the merchant’s return decision.
9. Can 17TRACK show my Route refund status?No. 17TRACK may show a return parcel’s movement, but only the merchant or payment channel can confirm refund processing.
10. Who should I contact about a Route order?Contact the merchant for order, shipping, return, and refund decisions; contact the carrier for delivery events; and contact Route for Route app or applicable Route service questions.
Expert FAQs
11. Is Route the seller or carrier for my order?No. Route is generally the post-purchase tracking and service layer, while the original merchant sells and fulfills the goods and a carrier transports them.
12. Can one Route order have multiple tracking numbers?Yes, if the merchant splits the order into multiple shipments. Open each shipment line and track each carrier number independently.
13. Does Route control the carrier’s delivery status?No. The carrier creates the operational scans, while Route can display the shipment data it receives through the connected order or carrier integration.
14. Can a gift recipient track a Route order?A recipient can use a shared merchant or Route tracking link or the carrier number, but private order, payment, return, and refund details may remain available only to the purchaser.
15. How do cross-border Route shipments affect tracking?Cross-border shipments can pass between origin, international, customs, and destination carriers. Tracking may pause during handoffs, and a later last-mile number may be supplied by the merchant or carrier.
16. Does Route provide a public order-tracking API?A current public official Route order-tracking API was not confirmed here. Merchants should verify integration access and documentation directly with Route rather than use an inferred endpoint.
17. Can the 17TRACK API register a Route order number?No. The 17TRACK API example is intended for a carrier tracking number; a Route order number must first be matched to the shipment number supplied by the merchant.
Tracking API
curl --request POST \
--url https://api.17track.net/track/v2.4/register \
--header '17token: YourKey' \
--header 'Content-Type: application/json' \
--data '[{"number":"TRACKING_NUMBER"}]'
Sources & References
17TRACK is an independent tracking platform and is not affiliated with Route.