When a dropshipping customer reports a problem, the first question is not "what refund applies?" It is "which review does this belong to?" Treat the following as a hypothetical example: an operator receives a message saying the nails "look wrong" and the parcel "hasn't arrived." That single message contains two different jobs. One needs product-quality evidence; the other needs a tracking stage and delivery status check. Running them through the same queue is how operators either refund a genuine defect too slowly or chase a courier about a product that arrived damaged.
Decide by evidence, not by tone. The sections below give you a triage sequence: gather product-quality evidence, read tracking stage and delivery status, confirm or reject a quality issue, pick the communication path, then choose only the resolution options that the confirmed category actually supports.
Step 1: Capture product-quality evidence before you interpret it
Product-quality review starts with artifacts, not adjectives. Ask the customer for clear photos of the affected pieces on a plain surface, a close-up of the specific fault, and a photo of the packaging and any batch or style label. Get the item in hand where possible, and note the style, shape, length, and finish the order was supposed to be. "The color is wrong" is not evidence; a photo of the delivered set beside the listing image is.
Keep that evidence attached to a single order record. If your supplier runs custom work, the reference point is stronger when approval happened earlier: 365nails custom projects include sample approval before production and quality-check progress in the project workspace. That means a confirmed defect can be compared against an approved sample rather than a memory of one. For dropshipping orders, 365nails dropshipping support covers product quality checking, neutral or branded packing, direct shipping to the buyer, and tracking through delivery. Product quality checking is a defined part of that support, so quality review is a real track with real evidence standards, not just a polite way of saying no.
Step 2: Read tracking stage and delivery status like a timeline
Delivery-tracking review asks a narrower question: where is the parcel, and has that status changed recently? Record the latest scan, its timestamp, the stage it represents (accepted, in transit, out for delivery, delivered, or an exception), and whether the tracking has gone quiet. Compare that against the delivery address the customer gave you. Then check whether the customer has the parcel in hand at all.
This step is what stops misclassification. A parcel still in transit cannot yet be judged as a quality problem, because the product has not been used. A parcel marked delivered with no customer receipt is a delivery investigation, not a quality claim. Only when the parcel is confirmed delivered, and the customer has the product, does product-quality evidence become the deciding factor.
Step 3: Decide whether a quality issue is confirmed
Write the conclusion in one line: confirmed quality issue, unconfirmed quality issue needing more evidence, or not a quality issue. Confirmed means the evidence shows a fault that matches a real product problem: breakage, a shape or size mismatch against the order, a finish defect, or a missing or wrong piece in the set. Unconfirmed means you are still waiting on photos or the item. Not a quality issue means the report is really about delivery, expectations, or fit.
Do not let a delivery delay silently become a quality claim, and do not let a genuine defect sit in a tracking queue. This split matters commercially, because the resolution options differ by category. For confirmed quality cases, 365nails supports a defined path: For a confirmed product quality issue, 365nails supports a refund without requiring return of the affected product. The team reviews the issue and confirms refund details. Read that literally. The issue is reviewed, the details are confirmed by the team, and only confirmed quality issues reach that route. A tracking exception is not a confirmed quality issue and should not be routed there.
Step 4: Choose one communication path per category
Every order should have one owner and one thread. Assign the exception to a single category: quality review or tracking review. Send the customer a precise, category-specific message. Quality review asks for the evidence list in Step 1 and gives a review expectation. Tracking review shares the latest scan stage and what happens next with the carrier. Mixing both asks in one reply is how customers send photos into a tracking thread and tracking questions into a quality claim.
Internally, the handoff should carry the same categories. Quality review goes to whoever owns product standards and supplier follow-up. Tracking review goes to whoever owns carrier and delivery follow-up. If the supplier covers fulfillment, the tracking inquiry belongs with them: tracking through delivery is part of the dropshipping support scope, so ask the supplier for the delivery status in the same thread rather than opening a parallel quality ticket.
Step 5: Apply only the resolution options the category supports
Quality-review outcomes are limited by the confirmed finding. If the evidence confirms a defect, the refund route above is the relevant option. If the evidence is unconfirmed, the option is further evidence gathering, not a refund decision. If the product was not defective, the case moves to expectation management or to the tracking track.
Tracking-review outcomes are limited by the parcel status. In transit means monitoring and a clear update. A delivery exception means a carrier inquiry. Delivered-but-not-received means a delivery investigation. None of these should be recorded as a product quality failure, because the evidence does not support that conclusion.
365 Take
The expensive mistake in dropshipping triage is not slow refunds; it is a category error. A quality claim routed as a tracking inquiry burns customer patience while you refresh a scan page, and a tracking delay routed as a quality claim teaches your team to refund defects without evidence. Separate the two reviews at intake, attach evidence to the quality side, attach scan status to the tracking side, and let the confirmed finding decide the resolution. That discipline protects both your margin and your customer's trust.
Operator Move
Today, open your exception queue and add two fields to every order record: quality evidence status and tracking stage. Label each open case as quality review or tracking review using the five steps above, and require a one-line confirmed or unconfirmed finding before any resolution is chosen. For supplier-side follow-up, route quality questions and delivery questions through separate threads. If you need help mapping your order exceptions to the right track, contact the 365nails team.
