OnTrac Tracking

OnTrac and LaserShip: current brand and legacy naming

OnTrac is the current unified public brand for the combined network. LaserShip still matters because users may encounter the legacy name in old shipment references, searches, and current legal material. The January 5, 2026 Terms identify the contracting carrier as LaserShip, Inc. dba OnTrac Final Mile.

That continuity does not mean every OnTrac-attributed movement was personally performed by an OnTrac employee. Current terms allow performance through OnTrac Logistics and, in certain territories, licensed third-party motor carriers; OnTrac also publicly recruits Regional Service Providers. An OnTrac tracking event therefore identifies the carrier system that recorded the event, not the specific employer, contractor, or legal entity that handled that parcel.

Use an OnTrac tracking number, not a retailer order number

OnTrac distinguishes a retailer order number from the carrier tracking number. If a retailer only gave you an order reference, use the retailer's shipment details to find the carrier tracking number before treating an OnTrac lookup result as attributable to your order.

The current OnTrac FAQ publishes these tracking-number prefix families:

A matching prefix does not prove that the number belongs to your order or that OnTrac physically has the package. If the number is rejected or unavailable in the official carrier lookup, use Tracking Number Not Found or Not Working rather than inventing a format rule.

Does OnTrac physically have the package?

This is the most important OnTrac-specific distinction.

retailer says shipped
→ merchant/commercial evidence
≠ carrier possession

OnTrac tracking record exists
→ carrier data exists
≠ carrier possession by itself

exact current OnTrac Label Created message
→ OnTrac says it has not received the package for delivery

later item-level OnTrac facility event
→ materially stronger evidence of carrier-network possession

The current FAQ explains the exact message:

“LABEL CREATED, TRACKING DETAILS WILL BE AVAILABLE ONCE THE PACKAGE ARRIVES AT THE ONTRAC FACILITY”

For that exact state, OnTrac says the package has not been received for delivery. This is stronger than a generic assumption about what “label created” usually means.

There is an important counter-boundary. Current Additional Terms contemplate a package being physically tendered before applicable manifest data is received. Therefore, outside that exact Label Created state, a missing or delayed public scan alone is not universal proof that physical handoff never occurred.

If a sender or merchant says the parcel was physically handed over but the public record still has no reliable acceptance evidence, use Dropped Off but Not Scanned to classify the tender evidence. If the record already shows stronger OnTrac possession and then stops changing, use Tracking Not Updating.

If Label Created does not change for 3 business days

In the current delayed-package FAQ context, OnTrac says that if the tracking status has not changed in 3 business days, the consumer should contact the retailer for assistance.

That clock is an action route, not a loss declaration:

3 business days without a change
≠ package legally lost
≠ retailer fault
≠ universal proof physical tender never happened

For the general meaning of pre-possession carrier records, compare Label Created with Carrier Received Package.

Failed delivery: next attempt and contractual ceiling are different rules

Current OnTrac consumer guidance and shipper terms describe two different layers:

An Attempted or failed-delivery record also does not prove the recipient was absent, at fault, or caused an access problem. Use the exact event and the next recorded outcome. If the attempt becomes the primary issue, use Delivery Attempted. If an Out for Delivery event does not resolve, use Out for Delivery but Not Delivered.

Estimated dates and times are not a contractual guarantee of delivery on that exact day or at that exact time. Weekend delivery is also eligibility-scoped: the current FAQ says Saturday and Sunday delivery is available in select service areas, not for every address or shipment.

Address changes and delivery instructions are separate workflows

After shipment, the current FAQ says an address change requires retailer approval for security. That is different from supplying delivery instructions or access details through OnTrac's support/Wink workflow.

Keep the states separate:

address change requested
≠ retailer approval
≠ carrier record updated

delivery instructions submitted
≠ operationally available
≠ applied

If the parcel is already Out for Delivery, OnTrac says newly submitted instructions may not be available to operations until the next delivery attempt.

Use Wrong Address or Address Information Required when the address itself is the problem. For a broader reroute/hold decision, use Change Delivery Address, Reroute, or Hold.

A refusal request is not Return to Sender

The current FAQ provides a refusal-request path through OnTrac support/Wink and, when the parcel is already Out for Delivery, describes a door-note option.

A submitted refusal request is only a request state. It does not prove that the carrier accepted the request, that reverse movement started, that the retailer cancelled the order, or that a refund was approved. The decisive evidence is a later return/RTS event.

If refusal is the primary user job, use Can You Refuse a Package?.

Delivered and Photo on Delivery: what the evidence can prove

Current OnTrac Privacy material says a delivery vendor may capture a photograph showing package placement. A photo is therefore not guaranteed for every shipment. If a photo is captured and passes OnTrac quality standards, it may become visible through OnTrac tracking.

A qualifying delivery photo is useful placement/location evidence, but its evidentiary ceiling matters:

Delivered or delivery photo
≠ named-recipient personal receipt
≠ contents verified
≠ package condition verified
≠ infallible proof of correct-address delivery

If the package says Delivered but you cannot locate it, use Delivered but Not Received. If the photo, signer, location, or other proof appears wrong, use Proof of Delivery, Photo, or Signature and, when the proof itself is materially disputed, Challenge Incorrect Proof of Delivery.

Delivered but missing: investigation is not a claim or refund

For a Delivered-but-missing package, current OnTrac FAQ/Support directs the consumer to submit an inquiry so OnTrac can investigate.

Current Support asks users to allow up to 48 hours for investigation of the latest information and next steps. Separately, current FAQ/Support says that if more than two business days pass without an update or package location, the consumer should contact the retailer.

Those are different first-party formulations in different contexts; this page does not convert them into one mathematical SLA.

OnTrac inquiry / case number
≠ package location
≠ contractual Shipment Claim
≠ retailer refund or replacement

If the support case itself becomes the primary problem, use Carrier Investigation Open, Pending, Closed, or No Resolution.

Consumer investigation, retailer remedy, and Shipment Claim are three different processes

Current Terms and Additional Terms make the contractual Shipment Claim a shipper-facing process. A recipient should not treat “file an OnTrac claim” as the default consumer remedy when the shipper or retailer owns the contractual/commercial route.

For general claim preparation after the correct role is established, use How to File a Package Claim. If a retailer or payment deadline may expire while a carrier issue is unresolved, use Protect Refund, Dispute, and Chargeback Deadlines.

Current OnTrac claim documents conflict on the filing deadline

OnTrac's current first-party claim documents do not support one safe deadline statement:

• the January 5, 2026 Terms say the Shipper must file a Shipment Claim within 15 calendar days of the anticipated due date;
• the claim form currently linked by OnTrac still says claims for damage, loss, or delay must be submitted within 30 calendar days of delivery.

These are different clocks with different triggers, and OnTrac's published materials do not establish which formulation controls every case. Shippers should verify the current OnTrac claim requirements directly rather than relying on the longer form deadline. This is not a recipient refund deadline and is not a statement about legal enforceability.

Filing a Shipment Claim also does not establish liability, approval, or payment.

Next decisive evidence

When the current record is ambiguous, identify the next observable that would actually change the conclusion.

Protect shipment data and keep the product boundary clear

Treat full tracking numbers, addresses, delivery photos, case records, and claim documents as private shipment data. Share them only in the official workflow that needs them.

11Tracking can help you read supported public tracking events and distinguish evidence stages. It cannot create an OnTrac scan, authenticate a private shipment, access private driver data, identify the actual contractor from brand attribution alone, change an address, submit delivery instructions, refuse a parcel, start Return to Sender, retrieve a private delivery photo, open or influence an investigation, file a Shipment Claim, issue a retailer refund or replacement, guarantee delivery, or provide live driver GPS.