Return Package Not Updating or Seller Says It Was Not Received

A return can be authorized, handed over, delivered to a returns facility, and still remain unmatched in the seller's system. Identify the last transition your evidence actually proves, then contact the actor who controls the next missing transition. Keep every live merchant, marketplace, payment, and transport deadline open while the return is investigated. A label or QR code does not prove handover, a receipt does not prove every item inside, and Delivered does not by itself prove merchant intake, item matching, inspection, or refund.

First, identify the last state you can prove

Do not treat the return as one continuous status. Compare your evidence with these separate states:

Use this rule:

last transition supported by evidence
→ next transition not yet supported
→ actor who controls that transition
→ live deadline that must remain protected

Verify that every number belongs to the return rather than the original delivery. An order number, RMA, QR code, drop-off reference, carrier tracking number, and merchant case number can describe different records.

If the parcel was never intentionally returned by the customer and is instead going back after failed delivery, use the Return to Sender guide. If this is an ordinary outbound parcel with no return authorization, use the Tracking Not Updating guide.

What to do for the status you see

There is no safe universal instruction to wait a fixed number of days. Use the promised timeframe in the exact return method and the live deadline displayed in your official merchant or marketplace case.

Preserve a return evidence packet

Keep the records privately and share only what a verified official channel needs:

1. Authorization: current return confirmation, authorized items and quantities, RMA or Return ID, method, destination, and live return date.
2. Parcel identity: the return label or QR kept private, the return tracking number distinguished from the outbound number, physical parcel count, and which items went into which parcel.
3. Tender: receipt or digital confirmation, date, time, location, parcel count, and any recorded weight.
4. Movement: the complete official tracking history, last checked date, exceptions, handoffs, and destination shown for Delivered.
5. Merchant case: written explanation of what not received means, support case numbers, partial acknowledgements, and marketplace deadlines.

A method-specific receipt can be strong evidence that an operator recorded your handover. It usually does not independently prove every item or its condition. A recorded weight may help reconcile parcel identity, but weight alone does not prove exact contents.

Do not edit or recreate receipts, change image metadata, reuse a label, combine returns contrary to the instructions, or state that an item was inside without a truthful basis. Do not upload order numbers, labels, QR codes, addresses, receipts, invoices, signatures, or account screenshots to 11Tracking.

A QR code may not be the tracking number

Different QR and label-less methods create different records:

• A QR can retrieve and print a conventional package label. USPS Label Broker documents a code used by participating Post Offices to retrieve a stored label. The code's existence is not evidence that USPS received the parcel.
• A retailer QR can be scanned by staff who then print a label and accept the sealed return, as described in the current FedEx U.S. returns flow.
• A QR can identify an unpackaged item that is bagged and later consolidated with other returns. Happy Returns describes individual returns moving through shared boxes, hubs, sorting, and retailer-bound pallets.
• A code can start a locker lodgement process. The relevant tender evidence may be the completed locker event or confirmation rather than the QR itself.

Canada Post separately describes merchant Return IDs, authorization numbers, QR codes, labels, and tracking numbers across print-at-home and label-free methods. That is why you should locate both the merchant confirmation and whatever package or return-network identifier the chosen method generated.

Do not conclude that a label-less return is untrackable. Ask the merchant or return operator whether it has an item-level record, a package number, a consolidated-network status, or an account-native return status.

If there is a receipt but no tracking movement

First identify what created the receipt. Counter, locker, parcel-shop, pickup, and street-posting methods do not produce identical evidence.

For example, Australia Post distinguishes Post Office scans and receipts, eligible Parcel Locker scans and confirmation emails, and street-posting methods whose tracking evidence depends on the postage product. InPost UK describes a post-drop-off email confirmation and an on-screen way to request a receipt when the operator does not already have the user's email address. These are product-specific examples, not universal receipt rules.

Ask the operator:

• What exact event was recorded: label print, acceptance, locker closure, collection, or carrier handoff?
• Which parcel or operator reference was attached?
• Can the original confirmation be reissued through the official process?
• Was parcel count or weight recorded?
• Did the return enter a consolidated network?
• Which carrier or account holder controlled the next handoff?

Then notify the merchant or marketplace in writing before its deadline. Do not send a replacement parcel or reuse the return credential unless the merchant gives verified instructions that preserve the original case.

If tracking says Delivered but the seller says not received

Read the destination before assuming Delivered means the merchant completed the return. It may be a merchant warehouse, partner seller, loading dock, third-party returns center, carrier station, consolidator, or return hub.

Ask the seller to translate not received into one of these operational states:

• no delivery record to the expected facility;
• no parcel found at receiving;
• parcel delivered but not entered into warehouse intake;
• parcel entered but not matched to the RMA or order;
• only some items or parcels recognized;
• correct return received, but inspection or refund still pending.

That distinction determines the owner. The carrier or its account holder investigates the transport and delivery event. The merchant investigates dock receipt, intake, RMA association, and item matching.

This boundary is visible in real return systems. ASOS addresses cases where return tracking shows delivery before the merchant's later processing communication. A consolidated network can also insert hubs and sorting between customer drop-off and final merchant receipt. These examples do not prove what happened to your return; they show why carrier delivery and merchant intake must be checked separately.

If the merchant confirms the correct return has been received and matched, and the only remaining issue is refund approval, processing, or payment, the logistics investigation is no longer the main problem. Move to the received-but-no-refund guidance.

Who should open the carrier investigation?

Identify who bought or generated the return transport before assuming the physical returner can file a claim.

Evri's current UK guidance gives a useful scoped example: the retailer starts the investigation for a free return, while a customer who paid Evri directly approaches Evri. UPS U.S. claim guidance also shows that shipper account restrictions, detailed claim visibility, and payment can be controlled by the shipper. Other carriers, regions, and accounts differ.

Ask the merchant directly: “Who purchased this return shipment, who is the carrier account holder, and who must open the transport inquiry?” Use the carrier support directory for a verified carrier route and Who Should I Contact About a Package? when several parties keep redirecting you.

Do not assume that starting an inquiry guarantees recovery, disclosure of internal records, compensation, or a refund. CCTV, manifests, scan details, recorded weights, delivery proof, and warehouse records may be unavailable or restricted.

Reconcile multiple items and multiple parcels

One return is not always one item, one parcel, or one label. Valid arrangements include one item in one parcel, several items in one parcel, one return split across several parcels, and several item returns consolidated into a shared transport container.

If only part of the return is recognized:

1. Compare the authorized item and quantity list with what was actually packed.
2. Record how many physical parcels or bags were used.
3. Match every label, QR, receipt, and tracking reference to its parcel.
4. Check whether the merchant permitted items to be combined.
5. Ask whether the parcel arrived but a specific item or RMA failed to match.
6. Treat receipt weight only as supporting context, not proof of exact contents.

If the merchant has received the parcel but alleges an empty box, wrong item, altered item, or condition mismatch, the dispute is no longer only about return transport. Preserve the intake and inspection record and use the appropriate contents, condition, claim, or appeal guidance.

Protect every live deadline

A return dispute may contain separate clocks for the return authorization, QR or label, marketplace case, merchant refund process, carrier inquiry, payment provider, and—for international returns—customs or storage action. One investigation does not automatically pause the others.

For each active route, record the exact deadline shown in the official account, what triggers it, what evidence is required, and what closing the case does. Do not close a marketplace return solely because a seller promises to refund later. eBay's current U.S. guidance, for example, ties returns to case-specific dates and tracking actions and says a voluntarily closed return request cannot be reopened for the same transaction. Follow the current rules displayed in your own case rather than copying a fixed period from another return.

Before opening an additional payment or carrier process, verify whether it is compatible with the existing merchant or marketplace case. Do not seek duplicate recovery. If the parcel later appears or a refund, carrier payment, marketplace reimbursement, or provisional card credit is issued, update the other active cases truthfully.

For a cross-border return, check the exact merchant and carrier instructions for customs forms, item descriptions, origin, value, quantity, and return purpose. Missing or incorrect documents can affect acceptance or movement, but requirements and responsibility vary by route and jurisdiction. Do not reuse outbound documents or guess customs values.

The goal is not to prove the whole return with one screenshot. It is to preserve the last supported handoff, identify the next missing handoff, and keep the correct operational and commercial routes available until the records are reconciled.