Dispute reason responses

Shopify Product Not Received Chargebacks: Build the Right Response

Package left on doorstep.
Photo: Matthew Henry / Burst

A product-not-received response should establish what the customer says is missing and whether the merchant can document delivery of that specific obligation. Physical goods, digital access, and services require different records. A shipping label cannot prove a digital download, and an appointment booking does not establish that a service was performed.

Start with the disputed scope and the promised delivery or performance event. Then compare the available record with that promise. If the merchant did not fulfill the obligation, acknowledge the gap and choose the appropriate case route rather than assembling unrelated evidence that the order existed.

Define the missing obligation

Read the issuer allegation and the customer’s prior messages. Determine whether the complaint concerns the whole order, one package, one digital entitlement, or part of a service. The amount disputed can help identify scope, but it should not replace the actual statement of the claim.

Shopify’s nonreceipt category includes goods and services. Shopify dispute reasons.

Locate the promised delivery expectation and any agreed change. A parcel that arrived after the customer’s relevant deadline may present a different issue from a parcel delivered as agreed before the dispute. Record dates accurately and do not silently substitute a revised estimate the customer never accepted.

Confirm the response options and live merchant deadline in the actual case. Some cases may have a different resolution route or no available evidence window. Preparing a careful narrative does not create a right to contest a case that the provider has already resolved under its applicable process.

Choose records that fit the delivery type

For physical goods, connect the disputed items to the shipment and the shipment to the destination and delivery event. A carrier record may support movement and delivery location, but check what it actually displays. A label created event is not carrier acceptance, and carrier acceptance is not completed delivery.

For digital goods, distinguish sending access from actual access. An email with a link shows a delivery attempt to an address; a relevant access record may show use of the purchased entitlement. Link the event to the correct order without exposing unnecessary account data.

For services, distinguish reservation, attendance, and completion. A booking confirmation shows that time was reserved. A dated completion record or customer acknowledgment may address whether the promised work occurred. If only part of a service was delivered, identify the remaining scope.

Shopify’s guidance varies evidence by delivery type. Shopify response guidance.

Use those categories as a starting point, then build an original explanation of your own records. Do not assume every record in a generic checklist is available or decisive for the case.

Work through a delivery-proof decision table

The following reusable table helps determine whether a record answers the actual nonreceipt question.

Purchased obligation Record available What it establishes Gap to investigate
Physical item Shipping label Intended shipment details Whether carrier received and delivered it
Physical item Carrier delivery record Recorded delivery event and available destination Item-to-parcel and destination linkage
Digital access Access email Access information was sent Whether entitlement was usable or accessed
Digital access Order-linked usage event Recorded use of the entitlement Identity and event interpretation
Service Appointment booking Scheduled service Whether performance occurred
Service Completion record Documented work and date Whether it covers the purchased scope

In a hypothetical order, a merchant sells a printed guide and an online workshop. The printed guide is delivered, but the customer disputes the workshop because the session was canceled. A parcel-tracking record does not answer the missing workshop claim. The merchant must assess the service obligation and any completed credit or agreed alternative.

The example shows why “the order was fulfilled” is often too broad. Different parts of one purchase can have different delivery outcomes.

Explain fulfillment gaps and select the response

Write the response around the missing obligation: what was promised, the relevant delivery event, and the records linking that event to the disputed purchase. If a replacement or alternate performance occurred, state when and under what agreement. Do not imply that any later substitute automatically defeats the original claim.

Include known limitations. If the carrier record reveals only a postal area, do not describe it as a full-address confirmation. If a digital log records automatic background activity, do not call it customer use. A precise qualification is more credible than a broad conclusion the record cannot support.

Where the merchant’s own records establish an unfulfilled obligation, follow the appropriate acceptance or resolution route. Check payment status before any separate reimbursement to avoid an uncoordinated duplicate action during an active dispute.

Submit any permitted response through Shopify or the actual provider and verify the resulting status. The response should make the delivery question easier to decide, with the disputed scope, relevant event, and remaining uncertainty visible. It should not ask the reviewer to infer receipt from evidence that proves only that an order was taken.

Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.

Monitor Your Disputes

Related reading in this collection: