For a wrong item in an order, compare the purchased and received lines using variant identifiers. Avoid asking the customer to describe the whole purchase again. Collect one missing detail that establishes the difference, then offer a resolution after checking the store’s actual capabilities.
Compare the purchased line rather than today’s product page
The customer ordered a blue mug and received a green one. Open the relevant order and inspect the variant recorded at purchase. The current product page may have another picture, name or availability.
Do not use it as the only evidence that the customer selected something else. The reference is the line in this particular order.
A report may concern colour, size, model or quantity. Distinguish these before requesting pictures. “I received a different product” does not identify the difference.
If number and variant are already in the conversation, confirm them instead of sending the complete form again. Your question should address what remains unknown, not repeat established information.
Scroll the table sideways to see all columns.
| Element | What to compare |
|---|---|
| Model | Purchased and received names or identifiers. |
| Variant | Colour, size or another selected characteristic. |
| Quantity | Ordered quantity and quantity reported by the customer. |
| Bundle | Contents associated with the purchase and the different or missing part. |
An order with several similar lines needs identification of the relevant one. Do not assume the first item is the reported item. WooCommerce customer support covers platform context; regardless of the store, compare the same unit and variant. An apparently matching name may refer to a different size or package.
Ask for the identifier that will establish the difference
A whole-product picture may not show size or model. Ask for the relevant label marking or a transcription. If colour is visible but lighting complicates assessment, do not treat the photograph as a decisive measurement.
A variant identifier may provide more dependable information than several similar pictures that leave the same uncertainty unresolved.
- Confirm the purchased variant.Check the purchase record in the store system. Keep its historical line distinct from the current catalogue name.
- Identify the missing detail.Request a model or size marking when absent from the description. Do not require the entire order in photographs for one item.
- Compare identifiers.Match ordered and received information. Distinguish a renamed product from an actual variant difference.
- Check the available resolution.Only after establishing the difference, check the correct product and possible operations. Comparison is not a replacement shipment.
Request: “The order shows the blue variant in size M. Your description indicates another variant. Please provide the size and model marking from its label; you can type it. We do not need the full address or pictures of every product. After comparing them, we will check an available resolution.”
Do not turn an unresolved difference into an accusation
If identifiers match but the customer still describes a difference, establish what they see. It could involve a misleading catalogue image, another batch, an unclear description or a bundle part. “Everything is correct in the system” does not answer the discrepancy. Matching codes are a fact, but do not automatically explain the entire report.
Avoid asking “are you sure you ordered the right size?” in a way that implies fault. Write: “The order and label show M; please describe the characteristic that differs from what you expected.” Use the earlier description to avoid repeating a question. You can inspect purchase details without imposing another credibility test on the customer.
If the label contains another code, identify the confirmed difference without inventing a warehouse cause. “Ordered A, received B” is enough to begin the next check. The appropriate person investigates causes and internal actions. Complaint handling covers the wider process and how to keep the customer informed.
This article concerns receiving and explaining information. It does not establish return, exchange or legal obligations. The message should reflect an actually approved decision.
Missing photographs are not presented as an automatic rejection basis; use the appropriate decision route for the particular case rather than deriving rules from a template.
Check the exact variant before offering an exchange
A confirmed mismatch does not mean the correct product is available. Check the exact model, colour and size rather than general stock quantity.
When another person must decide, identify that stage. The customer needs to know whether they are hearing a proposal, an approved option or an action already performed.
After comparison: “The order specifies blue M, while the received label says green M. We confirmed that difference. We are checking availability of the correct variant and the next actions in our process. No new shipment has been created. We will provide a specific proposal after checking the available option.”
When the option is approved, explain what the customer needs to do and what they need not repeat. Do not require another order if your process does not need one. Do not provide a tracking number that does not yet exist. Each resolution statement should follow a completed check or authorised decision, not merely an expectation.
For a bundle, identify whether the proposed action concerns one part or the complete set. The customer should not infer scope from “we will replace the product”. Check component compatibility and name the variant. This avoids another delivery that still does not match the purchased line, especially when visually similar parts have different identifiers.
Keep a brief comparison and the result of the store operation
In Meetlead customer support, conversations, tickets and private pictures in human contact preserve context. Use requires an account, website and permissions. Meetlead does not edit orders or independently check store inventory. An authorised person performs those operations in the sales system and communicates their actual result.
“Line 2: ordered A, received B; identifier supplied by customer; resolution under review” is more precise than “warehouse mistake”. Update the actual state once an operation occurs. Do not mark the conversation solved simply because an initial proposal was sent and the customer has not confirmed it. A proposal is a conversation stage, not proof of delivery.
If an offer description caused confusion, forward the exact relevant passage for correction. The guide to a store product page explains clear characteristics. Do not promise catalogue changes before their scope is approved.
If the name changed after purchase, preserve the earlier identifier in the comparison; a new name alone does not prove another product was delivered. Explain any matching variant using specific characteristics without dismissing the customer’s observation.
Check five points before replying
- The relevant line of the particular order is identified.
- The purchased characteristic is compared with what was received.
- Only the identifier needed to explain the difference was collected.
- The exact variant was checked before being promised.
- A proposal and an executed operation have distinct messages.
Do not require another label photograph when its marking is already readable in the history. The next operator can use the recorded comparison scope. If the approved resolution involves a refund, the next article explains a refund still in progress. A refund decision and its actual processing also need separate descriptions.
When “a different product” remains ambiguous
Is a photograph always needed? No. A typed identifier may settle the variant comparison. An image helps with appearance, bundle contents or a detail the customer cannot name.
Establish the question first, then choose the material rather than automatically collecting pictures for every mismatch.
Does the same code close the case? Not automatically. Check the reported difference and purchase description.
A code can confirm the model without explaining misleading presentation or another characteristic. Answer the customer’s actual concern, including any discrepancy that remains after comparing labels.
Should the warehouse receive the whole report? Share the necessary scope through your company process. A short comparison, identifier and agreed operation may be sufficient.
Avoid duplicating an entire private conversation unrelated to the check. The next team needs actionable information rather than every message.
Shopify describes managing particular orders and fulfilment. Available operations depend on the store system: managing orders.
