An “item not received” dispute sounds simple, but the evidence can become messy when an order is split across packages, delivered to a parcel locker, rerouted by the customer, replaced after a delay, or marked delivered without a signature. The merchant’s task is to connect the purchase record to a clear fulfillment story.
Card-network and processor terminology changes over time, so use the category shown in the active dispute notice. The workflow below focuses on the facts that tend to matter operationally rather than assuming one network rule applies to every case.
Connect the order to the shipment
Start with an order record showing the customer, items, amount, shipping address, order time, and fulfillment reference. Then pair it with the carrier record. The reviewer should not have to infer that tracking number 1Z… belongs to the disputed transaction.
If the customer changed the address after checkout, include the message or account action requesting that change. An unexplained mismatch between order address and delivery address can weaken an otherwise valid delivery scan.
Show the complete carrier path
Capture the meaningful events: acceptance, in-transit scans, attempted delivery, locker or pickup placement, final delivery, and signature when available. Avoid relying on a cropped status badge if the underlying carrier page provides a detailed event history.
For split shipments, label each package and identify which disputed items were in each one. If only part of the order was missing, make that distinction explicit.
Add customer messages that clarify receipt
Support messages can resolve ambiguity. A customer who writes “the box arrived but the blue size is wrong” has acknowledged receipt even if the later dispute is categorized as non-receipt. Conversely, a thread showing repeated delivery complaints may reveal that the merchant knew the shipment was unresolved.
Use messages as factual context, not as a gotcha. Quote only the relevant portion and keep the surrounding thread available in case the statement needs context.
Deal with porch theft and post-delivery loss carefully
A carrier showing delivery does not automatically resolve what happened after the package reached the address. If your policy, shipping protection, replacement process, or carrier claim applies, document what the business actually did after the customer reported the loss.
The dispute packet should not overstate what a delivery scan proves. State the scan, location context available to you, follow-up actions, and any customer acknowledgement.
When not to contest
If tracking shows the package was returned to sender, delivered to a clearly wrong address because of a merchant error, or never entered the carrier network, a representment may not be the best use of time. Record the operational failure and correct the customer experience.
A strong chargeback program measures avoidable losses as well as wins. Fulfillment quality is part of dispute prevention.
Example: three packages, one missing item
Consider an order with a shirt, shoes, and a jacket shipped in three parcels. Two tracking numbers show delivery, while the jacket parcel stalled and was later returned to sender. A single screenshot saying the order was 'partially delivered' is not enough. The merchant should map each item to each tracking number and reconcile the disputed amount to the jacket if that is what the customer says never arrived.
If the merchant then sent a replacement jacket, the replacement becomes a fourth fulfillment event with its own tracking and delivery status. The strongest packet tells that full story. Submitting the two successful deliveries while omitting the failed package would create the appearance that the merchant is answering a different allegation.
If the merchant replaced the missing item or issued a refund after the original delivery problem, add that remedy to the chronology and adjust the amount being defended. The case should reflect the customer's final economic position, not freeze the story at the first shipment.
Five delivery scenarios that require different evidence
A normal doorstep delivery is the simplest non-receipt case: connect the order address to the carrier record, show the final delivery event, and add any customer communication that confirms receipt or raises a different complaint. A parcel-locker case needs more detail. Show where the package was placed, what pickup notice or code was issued if available, and whether the customer later acknowledged accessing the locker. A generic 'delivered' scan may be too ambiguous if the carrier history actually shows delivery to a third-party pickup point rather than the customer's address.
A customer-requested reroute is different again. Preserve the original checkout address, the later request to change delivery, the merchant or carrier action implementing that request, and the final destination. Without that chain, the final carrier address can appear to contradict the order. For a signature-required shipment, explain who signed and what the carrier record can legitimately establish. A signature with an unfamiliar surname may require context; do not claim the signature proves the cardholder personally received the parcel unless the record supports that conclusion.
Split shipments need item-level accounting. Map each product to a tracking number, note delivery or failure for each package, and reconcile the disputed amount to the affected item. If two parcels arrived and one was lost, proving two successful deliveries does not answer a dispute about the third. Replacement shipments should be treated as a new fulfillment event with their own order or shipment identifier. Show why the replacement was sent, when it was accepted as a remedy, and whether it arrived before or after the dispute was filed.
The hardest scenario is a carrier status that says delivered while the customer consistently reports non-receipt. The merchant should avoid overstating the scan. Add available destination details, delivery photo or signature information if legitimately available, support history, carrier claim activity, and any replacement or refund offered. Then decide whether the evidence establishes the merchant's performance strongly enough to contest. The operational lesson is broader than one dispute: repeated 'delivered but missing' cases may point to address verification, carrier, packaging, theft-risk, or customer-communication problems that deserve prevention work.
Account for delivery exceptions that a single tracking status hides
Carrier histories can contain exceptions that materially change a non-receipt case: address correction, forwarding, weather delay, held-at-location, refused delivery, return to sender, damaged package, delivery to a locker, or an attempted delivery that never completed. Preserve the full event chain and identify which event actually corresponds to the disputed item. A top-line status such as delivered or returned is too compressed when the preceding scans tell a different story.
If the customer reported non-receipt before the final scan, keep that communication in sequence. If the merchant opened a carrier claim, replaced the item, or later recovered the package, show those events as part of the resolution path. The strongest evidence does not merely prove that a carrier moved a parcel; it explains what happened to the specific goods represented by the disputed amount and what the merchant did after any delivery problem became known.
VERIFY CURRENT RULES
Primary references
Processor interfaces, reason-code mappings, filing windows, and network rules can change. Check the active dispute notice and current official documentation before submitting.