E-commerce
June 28, 2026
"I ordered blue in size M, I received black in L." The customer sends a photo of the box. Your agent checks Shopify: correct SKU shipped. Warehouse or customer? Three days of doubt. A scathing review.
Mixbit ranks the received product error among the top 3 e-commerce returns, often linked to SKU confusion in picking (Mixbit, Order Errors 2026). Nventory recommends immediate auto-approval on wrong item: it's your fulfillment error, not the customer's (Nventory, RMA 2026).
This guide #186 covers incorrect product received support: wrong item, incorrect variant, missing item in multi-product packages. Operational topic absent from existing content. Distinct from breakage (#182) and partial returns (#185): here, picking or shipping error.
Summary
Why do received product errors explode into tickets?
A product received different ticket combines customer frustration, double shipping costs and a risk of negative reviews.
Three business impacts
Double cost: re-shipping + return of incorrect item or stock loss
Chargeback: customer perceives non-delivery of the correct product
Ops loop: without SKU logging, the same error is repeated
Typical volume
Mixbit estimates that a customer-reported error rate higher than 2% of the shipped volume justifies immediate action. Multi-SKU fashion brands: 3 to 6% of post-delivery tickets concern wrong/missing item.
Difference vs breakage
Breakage = correct product damaged. Wrong item = incorrect SKU delivered intact. Workflow and evidence differ.
Wrong item ticket cost
Reship + return label + agent time = often €25 to €45 per incident depending on the cart. Resolution within 24 hours limits chargebacks and post-delivery 1-star reviews.
How does this subject differ from neighboring disputes?
Map nearby content so as not to mix macros and policies.
Breakage and damage (#182)
Fragile guide (#182): damage photos, carrier claim. Here: incorrect item received in good condition.
Partial returns (#185)
Partial returns (#185): customer wants to return part of the kit. Here: they never received the right item.
Unboxing and experience
Unboxing experience: packaging prevention. The #186 = after-sales service resolution.
Promise #186
Quick sorting, resolution within 24 hours, warehouse feedback by SKU.
Which scenarios of receiving a different product should be mapped?
Six types of fulfillment errors require distinct responses.
CS Typology
Wrong SKU: completely different product ordered
Wrong variant: right product, wrong size or color
Missing item: order line missing from the package
Extra item: unordered surplus
Confusing split shipment: customer believes everything is missing, 2nd package on the way
Unaccepted substitution: out-of-stock item replaced without customer agreement
Gorgias Tags
wrong_sku, wrong_variant, missing_item, split_shipment, substitution_dispute.
Verification before blaming the warehouse
Compare packing slip, 3PL pick list, and Shopify line items. Casekit reminds: always check split fulfillment before missing (Casekit, wrong item 2025).
How to triage a ticket in less than five minutes?
The received different product triage avoids impossible promises and accelerates resolution.
6-step triage workflow
Authenticate: email + order #
Read ordered line items vs customer description
Verify fulfillments: one or more packages, active tracking
If partially fulfilled: explain the 2nd package before wrong item
Request photos if in doubt (received + packing slip)
Choose resolution in section 5, communicate timeframe
Split shipment
Macro: "Order #[X] shipped in 2 packages. Package 1 delivered, package 2 in transit tracking [link], ETA [date]. If package 2 arrives incomplete, contact us again." See order tracking (#181).
Internal SLA
First response 2 hours. Resolution (re-shipment launched or refund) 24 business hours max on proven warehouse error.
Claimlane and return portal
Wrong item reason in Loop or Claimlane = auto-approve without agent delay. The customer chooses reship or refund, return label generated if necessary. Reduces contacts by 4.2× according to Zendesk via US Tech 2026.
What resolution should be proposed depending on the case?
The wrong item resolution matrix must be documented, not improvised.
Rules per scenario
Proven Wrong SKU / variant: express reshipment + free return label or keep item if value is < €20
Confirmed missing item: dispatch missing item within 48 hours or refund line
Customer wants refund, not reshipment: OK if warehouse error, full refund + free shipping fees
Extra item: customer keeps or free return, never bill
Substitution dispute: reshipment of original SKU or refund if out of stock was not communicated
Reshipment priority
Inventory: wrong item = auto-approve, do not penalize the customer with a slow process. Replace first unless there is an explicit refund request.
Financial thresholds
Order < €30: reship without returning the incorrect item. > €150: express reship + customer call if it is an urgent gift.
Partial missing item multi-line
Immediate refund of the missing line or dispatch within 48 hours depending on stock. Do not wait for the return of the rest of the package to ship the forgotten item. Tag partial_missing separate from wrong_sku.
What proof should you ask for without frustrating the customer?
Wrong item proof photos protect against fraud and fuel warehouse investigations.
Standard request (2 photos)
Item received: SKU/barcode label visible if possible
Packing slip or package label with order #
When not to ask
High LTV, 1st mistake, obvious mismatch (PDP photo vs received in customer message). Trust accelerates CSAT.
Photo request macro
"To correct this within 24 hours, please send a photo of the item received + packing slip. These images help our warehouse prevent this from happening again. Upon receipt, we will dispatch the correct product." Aligned with #178 MANO.
Which scenario-triggerable macros?
Macros Incorrect product CS ready in Gorgias.
Wrong variant confirmed
"Sorry for the error on order #[X]. We are shipping [correct SKU] with priority within 48 hours. Tracking available within 24 hours. Keep the received item or find the free return label attached: [link]."
Missing item, not split
"Missing item [name] confirmed by the warehouse. Shipping within 48 hours or refund of [amount] €: please reply SHIP or REFUND."
Warehouse investigation in progress
"Investigation launched with the warehouse. Next update tomorrow at 2 PM. If the error is confirmed: immediate reshipment or refund, your choice."
Reshipment processed
"Correct product shipped. Tracking : [link]. Estimated delivery on [date]. We remain available if needed."
How to connect customer service and the warehouse to prevent errors?
Each wrong item ticket must feed into ops, not disappear after the refund.
Weekly feedback loop
Export tags wrong_* / missing_* by SKU
Top 3 SKUs: error rate / shipments
Cause: SKU naming, barcode, pick bin, BFCM rush
Ops action: color label, double scan, visual separation
Mixbit root causes
Similar SKUs BLK-TEE-M vs BLK-TEE-ML = human error under pressure. Renaming or adding a pick bin photo reduces incidents.
Mandatory Shopify note
wrong_variant | ordered : SKU-A | shipped : SKU-B | action : reship SKU-A | 3PL ticket #123.
Product tickets link
How to pre-qualify in the bot before agent handoff?
A wrong item bot collects data and triggers a reship if clear rules are met.
5-step bot flow
Order + fulfillments lookup
Customer describes discrepancy (variant, missing, wrong product)
Split shipment branch if a 2nd package is pending
Upload 2 photos if value > threshold
Reship / refund choice if auto-approve policy applies
Auto-resolution conditions
Proven warehouse error in 3PL log, 1st customer incident, correct SKU stock > 5: auto draft fulfillment via Shopify Flow. Otherwise handoff tag wrong_item_review.
Returns bot
Completes return prequalification, distinct intent from wrong_item_received.
Friendly fraud
Repeat wrong item customer (> 3 in 90 days): mandatory photos + manual review. Compare shipping address and return history before automatic reship.
Which KPIs and SKU signals should be monitored?
Measure the fulfillment quality via tickets, not just overall returns.
Leading KPIs
Wrong+missing tickets / shipments: target < 2%
Wrong item resolution time: < 24 h
Messages before resolution: < 2 using macros from section 7
Recontact within 48 h with same intent: < 10%
Lagging KPIs
Reship + wrong item return cost. Post-dispute CSAT. 90-day repeat purchase rate post-error resolved in under 24 h. US Tech: self-service portal reduced refund follow-up tickets by 88% (US Tech, 2026 returns).
Monthly review
Top 5 wrong item SKUs, 1 ops action, 1 macro tweak.
How does Qstomy speed up incorrect product disputes?
Qstomy detects split shipments, collects evidence, and proposes resolutions without long ticketing processes.
Features
wrong_item / missing_item Intent: multi-fulfillment lookup
Compare ordered vs received via customer description + photo
Split branch: reassures 2nd package before escalation
Reship/refund choice: according to section 5 matrix
SKU error report: for weekly ops
Quantified DTC Scenario
fashion brand, 5,800 orders/month, 4.1% wrong/missing tickets (238/month), 18 min/ticket manual sorting, 0 3PL feedback. Deployment of Qstomy wrong item + section 7 macros + section 8 ops loop. After 9 weeks: wrong/missing tickets -38%, resolution time 14 hours, messages/ticket 1.8, joggings SKU error rate -52% after renaming, dispute CSAT +1.4 pts.
Explore AI support, Shopify, request a demo.
Which operational playbooks should be launched this week?
Playbook 1: resolution matrix (1 h)
Document section 5. Share support + ops. Display Gorgias sidebar.
Playbook 2: macros for 4 scenarios (45 min)
Copy section 7. Variables #, SKU, tracking, delay.
Playbook 3: split shipment sorting (30 min)
Train team: always check fulfillments before missing. Test 5 multi-package orders.
Playbook 4: 3PL feedback (weekly 20 min)
Export wrong_* tags. Top SKU. Warehouse ticket if recurring.
Playbook 5: chargeback prevention (1 h)
Link fast wrong item resolution to chargeback prevention. Systematic Shopify note.
Useful links
A picking error is expensive. A clear resolution in under 24 hours often turns a furious customer into a loyal customer.
Enzo
June 28, 2026
