Playbook, fashion retailer
One order, several lines, and they did not all leave together
The person writing this has usually bought the same piece twice, in two sizes, intending to keep one. They are not confused about what they ordered. They are looking at one parcel, one despatch email and a total that no longer matches, and the shop's own account page is describing the order as a single object when the warehouse has been treating it as three.
Why this is not the general answer
The handling pattern for order status holds across every trade. What follows is the part that does not.
- Ordering one garment in two or three sizes is ordinary behaviour in this trade rather than a mistake, and it is precisely the order most likely to be split, because the sizes rarely sit in the same place and are rarely released together.
- A line can leave an order after payment, because the last unit on the rail turned out to be a returned garment that failed inspection at the pick, and the customer meets the refund for that line before anybody has explained where it went.
- A drop or a launch compresses an enormous number of orders into one minute, so the comparison the customer is making is against somebody else who ordered in the same minute, which is a standard no published timescale answers.
- The set matters more than the parcel here, because two sizes arriving a week apart cannot be tried against each other, and by the time the second one lands the window on the first has been running for days.
How it arrives
- i ordered three sizes and only one has arrived
- why has part of my order been refunded
- did my order go through on the drop
- one of the sizes is missing from my parcel
- will the rest of my order come separately
- my order still says processing after the launch
What has to be indexed for this to work
| Whether you split despatch, and on what basis | Written as a rule rather than as an apology: which lines travel together, whether sizes of the same piece are picked from the same location, and whether the customer is told in advance. A shopper who knows the sizes may arrive separately plans the try on differently. |
|---|---|
| What happens when a line fails at the pick | The garment that comes off the rail marked, faded or with a pulled thread and cannot be sent. Say plainly that this happens, that the line is refunded, and roughly how quickly, because the refund arriving without a word is what turns this into a second contact. |
| Your drop day operating note | What happens to orders placed in the first minutes of a launch, whether they are picked in sequence, and whether a confirmation email is the point at which the size is genuinely yours. Publish it before the drop, not during it. |
| How the return window is counted on a split order | Whether the clock starts per parcel or per order, because a customer holding two sizes that arrived a week apart is trying to work out which date they are counting from and there is usually nothing written. |
The reply
I cannot open orders, so I cannot tell you where yours is, but the pattern you are describing is the usual one rather than a fault. Sizes of the same piece are frequently picked from different places and released separately, so a despatch email covers what was in that parcel rather than the whole order [1]. If part of the order has been refunded without arriving, that normally means the last unit of that size failed inspection at the pick and could not be sent [2]. On the return window, it is counted from the day each parcel is delivered rather than from the order, so the two sizes are on separate clocks. If you want somebody to look at the order itself, leave your name, the email you ordered with and the order number.
It names the behaviour as ordinary in the first breath, because the customer's actual fear is that something has gone wrong with money. The failed pick is explained rather than left to be inferred from a refund line, which is the single most alarming thing this shop can do silently. The window clarification is volunteered because a shopper holding two sizes is already counting days and would otherwise count from the wrong one.
Where it stops
The trigger. The visitor names an order, gives a date, says an amount has been refunded that they did not expect, or says a parcel has not arrived at all.
I have no view of orders and cannot chase one. Leave your name, the email on the order, the order number and which pieces are missing, and the team will open it and reply to that address.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say an order has shipped, is being picked or is on its way, because the assistant reads documents and has no view of any order record.
- Never say a missing size is coming separately, since it may have been refunded off the order at the pick and the customer would then stop watching for the refund.
- Never say a size was reserved by placing the order, because on a drop the confirmation and the allocation are not always the same moment.
- Never tell somebody their return window is fine without saying what it is counted from, since on a split order the two parcels are on different dates.
Questions
- Can it tell a customer which parcel their second size is in?
- No. There is no document anywhere on a shop that describes one customer's order, so there is nothing to read. What it can do is explain that split despatch is normal here, which is most of the message, and collect the identifiers for the part that needs a person.
- Is the failed pick really worth publishing?
- It is the highest value paragraph in this cell. Every clothing shop sends out fewer garments than it sold, because rail returns fail inspection, and every one of those refunds arrives at a customer with no explanation attached. One published sentence converts a suspicious refund into an understood one.
- What should it say on a drop day when volume is high?
- The truth about sequence, and nothing about timing. It should not offer a picking estimate it cannot know. Saying that orders are worked in the order they were placed answers the comparison people are actually making with their friend's order.
Keep reading
- Everything for a fashion retailerFit is both the most asked pre-purchase question and the biggest cause of returns. Here is what a clothing retailer can safely automate.
- Handling order status in generalThe most asked question in retail support and the one a document-based assistant cannot answer. What it can do instead, and where handover sits.
- The date in their head belongs to somebody elseThe deadline is an event, not a preference. Cut-offs, pre-order windows and a collection counter that closes before the shop does.
- Two histories end with the same mark on a sleeveA security tag left on, a pulled thread, a dropped hem. Transit damage and a garment fault look identical and take different routes.
- Three numbers on one swing ticket and none of them is wrongWas, now and further reduced are three numbers on one ticket. Codes that die on sale lines, and one size cleared while the run stays full price.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.