A wholesale customer sends a photo of a torn carton on WhatsApp and asks for a replacement today. An immediate apology and replacement promise might feel helpful, but it can create a bigger dispute before anyone knows whether the packaging or the product is damaged, when the damage was noticed, and who can authorize a remedy. Start by documenting the condition and protecting affected stock. Decide on a remedy only after a clear quality and commercial review.
Distinguish damaged packaging from damaged goods
A photograph of a crushed box does not by itself establish that the goods inside are unusable. Equally, an intact outer carton does not guarantee that every item is sound. Ask what the receiving team actually observed. Is the issue limited to packaging, the product itself, or only part of the shipment? If there is a safety concern, advise the customer not to use the affected items pending review under your approved safety procedure.
Collect the purchase order or invoice reference, product code, batch number where relevant, affected quantity, delivery time, and clear photos of the package, item and shipment label. Request the receiving document and any note made by the receiver or carrier. Avoid collecting unrelated personal information, and store the evidence in an authorized channel with appropriate access controls.
Proof of delivery is not always proof of product condition
A receiving clerk may sign for the number of packages delivered and discover damage only when opening them. Another clerk may note visible damage on the delivery receipt. The meaning of either record depends on the contract and the company's and carrier's procedures. Do not treat a signature as conclusive evidence of good condition, or a chat message as conclusive evidence of fault.
Microsoft's sales returns guidance separates registering a return request, inspecting returned items, and deciding whether to replace, credit or take another action. Its returned-item inspection guidance also shows why different units may need different dispositions. These are international operational examples, not Egyptian legal advice or evidence that Mr. AI integrates with a warehouse system.
A practical sequence from report to decision
At intake: open a case linked to the order, request only relevant evidence, assign an owner and set the next update time. Before stock is moved: ask the customer to separate affected units and preserve packaging, unless safety rules require another action. Do not request an unapproved return shipment. After review: determine whether quality needs more photos, a site inspection or a physical return. The authorized decision-maker can then approve replacement, repair, credit, or a reasoned rejection.
Consider a hypothetical shipment of 60 units. Four outer packages are torn, but visible product damage appears in only two. Recording all 60 as damaged would be misleading. Recording no damage because the delivery count matches would be equally wrong. Track the quantity received, the quantity reported as affected and the final inspection outcome separately.
A customer reply that is useful without pre-approving compensation
“Thanks for reporting the damage. We are reviewing it as a priority. Please share the order reference, photos of the package and affected items, the quantity involved, and any note on the delivery receipt. We will confirm the next step after our quality and operations review. A replacement or credit has not yet been approved.”
This acknowledges the issue without blaming the carrier or customer. If the incident stops the customer's production line, escalate the urgency internally and give a credible update time. Do not invent a replacement dispatch date.
Measure evidence quality as well as resolution speed
Review reports missing order references or usable photos, time from report to quality decision, compensation promises made before inspection, and repeat incidents by product or carrier. Closing a ticket quickly is not enough if the wrong resolution produces a second dispute.
This differs from a short-delivery quantity dispute, which starts with counting what arrived, and from a broader WhatsApp returns and exchanges workflow. The focus here is establishing the condition of goods before making a financial or logistics commitment.
What Mr. AI can help with
Mr. AI can receive the report, reply using approved company knowledge, summarize the conversation for a human reviewer and help track the next step. That is not a claim of automatic damage detection from photos, legal fault determination or autonomous compensation approval. Define the evidence requirements and decision owner first, then test the intake workflow with examples from your operation.
