What Do You Say When a 500-Piece Bag Shipment Is Delayed?
Classify it first — a non-critical stage, a critical stage, a vendor dependency or a buyer decision — then ask for the thread, the revised date and the options in writing. We do not promise the fastest 20 days. We promise a delivery date you can calculate.

A delay has to be classified before it can be managed: a stage delay on a non-critical thread, a stage delay on the critical one, a dependency delay at the mill or the tool vendor, or a decision delay on the buyer side. Each has a different script. Ask for the thread, the revised date and the recovery option in writing, and give a response window rather than an expression of disappointment.
Every programme slips at some point, and the difference between the buyers who recover and the ones who do not is rarely the size of the slip. It is whether the slip was classified within a day of being known. An unclassified delay is a feeling; a classified one is a thread, a date and a decision. This piece is the four classifications, the script for each, and the escalation ladder that follows when the first response is not good enough.
What Kind of Delay Is It?
Four kinds, and the script differs completely between them. A stage delay on a non-critical thread costs nothing yet and may be absorbed by float. A stage delay on the critical thread costs day for day. A dependency delay at a mill or a tool vendor costs more than the delay, because the queue has to be rejoined. A decision delay on the buyer side costs whatever the decision takes and is the only one the buyer fully controls.
| Kind of delay | How to recognise it | What it costs | The first question to ask |
|---|---|---|---|
| Stage delay, non-critical thread | A later row moved and the final date did not | Nothing yet; it consumes float | How much float is left on that row? |
| Stage delay, critical thread | The material or the sewing block moved | Day for day on the ETD | What is the revised date in writing? |
| Dependency delay at a vendor | The mill or the tool vendor missed | The delay plus a place in a new queue | When is the next available slot? |
| Decision delay, buyer side | A dip, an approval or a deposit is outstanding | Whatever the decision takes | Who owns it and by when? |
The second column is the one to read carefully, because a vendor update will rarely tell you which kind it is. Updates describe events — the fabric is late, the line is busy — and events have to be translated into threads. A buyer who can do that translation themselves does not have to wait for somebody else to volunteer the answer, and the difference is usually several days.
What Should the First Message Say?
Three things and nothing else: which thread moved, what the revised date is, and what the options are. Not why, not yet. The explanation is valuable later and it is a distraction in the first exchange, because the first exchange is about establishing whether the date is recoverable and what recovery costs.
The wording matters more than buyers expect. "Please confirm which thread moved and issue a revised schedule with a date" produces a document. "We are very disappointed and need this back on track" produces an apology, a promise and nothing checkable. Disappointment is a legitimate feeling and an ineffective instrument.
How Do You Ask for Recovery Without Damaging the Order?
By asking for options rather than for a promise. There are four recovery instruments and each has a price: overtime or a second shift on the line, premium vessel space, air freight on part of the quantity, and a split shipment that sends the first cartons on the earlier sailing. Ask which of the four is available and what each costs, then choose.
The asking itself is not the damaging part. What damages an order is a request for compression that has no price attached, because it forces the vendor to choose between absorbing a cost and disappointing you, and the vendor will choose the latter eventually and quietly. A request that names the instrument and asks the price is a commercial conversation rather than a demand.
What Are the Six Rungs of an Escalation Ladder?
- Written confirmation of the revised date, requested the same day the slip is known.
- A named recovery option with its price, requested within one working day.
- A re-issued schedule with a version number, requested within two working days.
- A named person at the next level, requested if the schedule does not arrive.
- A contractual remedy on the named milestone, invoked if the revised date is missed as well.
- A written notice reserving rights, issued before any further payment is made.
The last two rungs are the ones buyers hesitate on, and the hesitation is understandable but expensive. A remedy invoked on a named milestone in week three changes behaviour in week three. A remedy invoked on the final date in week eight changes nothing, because by then the goods are late and the only remaining question is who pays.
What Should You Never Say in a Delay Conversation?
- "Just do whatever it takes." It delegates a commercial decision to the party with the least incentive to tell you the price.
- "This is unacceptable." True, and it produces an apology rather than a date.
- "We will move the programme to another partner." Sometimes necessary, and useless in week five of a run that only one line can make.
- "Send it anyway and we will sort it out later." That is an unwritten waiver, and it is how a rejected lot becomes an accepted one.
- "Keep us posted." It releases the other side from the obligation to produce a date.
The last item is the one that does the most quiet damage. "Keep us posted" converts a commitment to produce a revised schedule into a commitment to send messages, and the buyer discovers the difference in the final week. Ask for a document with a date on it and the obligation stays where it was.
How Does a Delay Interact With Inspection?
Badly, and this is the interaction most often missed. A run that is late is a run that will be inspected under time pressure, and time pressure is when a first submission gets passed that should not be. The buyer lever here is explicit: state in writing that the inspection standard has not changed and that a waiver is the buyer decision to make, not a consequence of the schedule.
On a 500-piece lot the draw is code letter H at General Inspection Level II under ISO 2859-1, 50 units, accept 3 and reject 4 at AQL 2.5 for major defects. That does not change because the goods are late. What changes is the calendar around it: a late run frequently has its inspection window compressed, and the re-check branch is the first thing to be quietly dropped.
What Records Should Be Kept During a Delay?
- Date the slip was known
- Not the date it was told to you; the date it happened
- Thread affected
- Named, with whether it is on the critical path
- Original date and revised date
- Both, with the number of days
- Recovery options offered
- Each with its price and its effect on quality
- Decision taken
- By whom, on what date, in writing
- Effect on the final date
- Recomputed, in writing
- Any waiver granted
- Signed, dated and specific to a defect class
Seven fields, and the conversation that happens six weeks later — about who caused what — is a check of a document rather than a contest of recollections. We do not promise the fastest 20 days. We promise a delivery date you can calculate. A delay handled this way is still a delay, but it is one with a number on it.
When Is a Delay the Point to Change the Specification?
When the recovery options all cost more than the delay. That happens more often than buyers expect: overtime raises the defect rate, premium space is expensive, and air freight on 500 soft goods is rarely justified by the margin. Where the launch date is genuinely fixed and the options are all poor, the honest answer is sometimes to accept a later date and move the launch.
The other case is the one where changing the specification is less costly than waiting: a component that is stuck in a tool vendor queue can sometimes be replaced with a stock article, and the units already made can be finished with it. That is a change, it needs a written change note and a new pre-production sample, and it is frequently faster than the second option.

What Should Happen After the Goods Finally Ship?
A short review, and almost nobody does one. Twenty minutes with the schedule, the delay record and the inspection report, asking three questions: which thread actually caused the slip, when it was first knowable, and what would have caught it earlier. The answer is usually a milestone that existed but had no artefact, or a buyer-owned decision that had no response window.
Then change the next order accordingly. A programme that adds a written response window to the buyer-owned milestones and an artefact to the row that slipped will usually avoid the same delay second time, which is the only return available on a bad experience.
What Do the Four Recovery Instruments Cost?
| Instrument | What it recovers | What it costs | What it risks |
|---|---|---|---|
| Overtime or a second shift | 3 to 5 days on the sewing block | A premium on the labour and some output | A higher defect rate at the tail of a long shift |
| Premium vessel space | 3 to 7 days on the booking leg | A higher freight rate for the same transit | Nothing on the goods; it is a money decision |
| Air freight on part of the quantity | 7 to 12 days on the transit leg | The highest per-unit freight cost on soft goods | It shortens transit, not production |
| A split shipment | The first cartons on the earlier sailing | Two bookings, two document sets, two reports | A partial delivery to manage at the receiving end |
The table has one property worth noticing: three of the four instruments act on the last two weeks and none of them acts on the fabric thread. That is the mechanical reason a slip found in week one is less costly to fix than the same slip found in week six. The instruments that would work on material are not instruments at all — they are decisions that belonged before the order was placed — and a buyer who is offered overtime for a dye-house queue is being offered something that cannot work.
The prices are also paid in different currencies, which is what makes them a choice rather than a comparison. Overtime is paid in money and in defect rate, premium space in money alone, air freight in money and in margin, and a split shipment in administrative work and in the coherence of the delivery. Two of those costs are measured in the condition of the goods that arrive rather than in the invoice, and they are the ones that surface later, at inspection or at the receiving warehouse.
When Is Accepting the Delay the Right Call?
More often than buyers expect, and it is the hardest of the options to take. The test is arithmetic: where the least costly instrument that would recover the date costs more than the commercial value of the date, the money is better left unspent. On a 500-piece programme that calculation surprises people, because air freight on soft goods is expensive per unit and a launch date is rarely worth the whole margin on a first order.
There is a second case for it, which is where the date was never firm. A launch built on a quoted window that was never written down as a milestone with a trigger is a launch whose date was an aspiration, and spending money to defend an aspiration is spending it on the wrong thing. The honest move there is to reissue the date in writing, tell every downstream party the same day, and change the way the next order is specified rather than the way this one is recovered.
What should not happen is for the delay to be accepted silently. A date that slips with no revised schedule in writing is a date that will be argued about later, and the argument will be about who knew what rather than about what could have been done. Write the new date down, note the reason it is not being recovered, and the acceptance becomes a decision on the record instead of a drift that nobody owns.
Managing a delay
- Classify it within a day: non-critical, critical, dependency or decision.
- Ask for the thread, the revised date and the options. Do not ask for an explanation first.
- Name the recovery instrument and ask the price; a compression request with no price gets absorbed quietly.
- Invoke the remedy on a named milestone in week three, not on the final date in week eight.
- Say in writing that the inspection standard has not changed and a waiver is your decision.
- Review the schedule afterwards. The usual answer is a row that had no artefact.

Get a schedule whose delays are classifiable
Send the style, the quantity and the date you need the goods on board. You get a schedule with named threads, float and artefacts, so a slip is a number rather than a feeling. Sampling 6-10 working days, bulk 35-50 days, AQL 2.5, FOB Xiamen.
Frequently Asked Questions
What should I say first when a bag order is delayed?
Ask which thread moved, what the revised date is and what the recovery options are. Do not open with why, and do not open with disappointment.
What are the four kinds of delay?
A stage delay on a non-critical thread, a stage delay on the critical thread, a dependency delay at a mill or tool vendor, and a decision delay on the buyer side.
Why does classifying the delay matter so much?
Because the script differs completely. A non-critical slip consumes float and costs nothing; a dependency slip costs the delay plus a place in a new queue.
How do I ask for recovery without damaging the order?
Ask for options and prices. Overtime, premium space, air freight and a split shipment each have a price, and naming the instrument makes it a commercial conversation.
What should I never say in a delay conversation?
Just do whatever it takes, keep us posted, and send it anyway and we will sort it out later. The last one is an unwritten waiver.
When should a contractual remedy be invoked?
When a named milestone is missed, in week three rather than at the final date in week eight, because by then nothing can be changed.
Does a delay change the inspection standard?
No. The draw stays at code letter H, 50 units, accept 3 and reject 4 at AQL 2.5. What gets compressed under pressure is the re-check branch, so state in writing that it has not changed.
What is a waiver and should I grant one?
A written acceptance of a lot that failed inspection. It is a legitimate commercial decision when the date matters more than the defect, and it must be signed, dated and specific to a defect class.
When should I change the specification instead of waiting?
When every recovery option costs more than the delay. A component stuck in a tooling queue can sometimes be replaced with a stock article, with a written change note.
What records should I keep during a delay?
Seven fields: the date the slip was known, the thread, both dates, the options with prices, the decision, the recomputed final date, and any waiver.
What should happen after the goods ship?
A twenty-minute review asking which thread caused the slip, when it was first knowable, and what would have caught it earlier.
How long is sampling before a delay can even happen?
6-10 working days, or 12-15 on a complex build. Delays inside the sampling window are usually dependency or decision delays rather than capacity ones.
What is the MOQ and does it affect how a delay is handled?
500 pcs per style and colourway, with 300 open to discussion on a repeat. A smaller order has less claim on a recovery slot than a larger one, which is worth knowing before the slip.
Can a split shipment rescue a launch date?
Often yes. It sends the first cartons on the earlier sailing at the cost of two bookings, two document sets and two inspection reports.
People Also Ask
What do I say when my bag order is delayed?
Ask which thread moved, what the revised date is in writing, and which recovery options are available with their prices.
How do I recover a delayed bag order?
Choose from four instruments: overtime on the line, premium vessel space, air freight on part of the quantity, or a split shipment.
Should I accept a delayed shipment that failed inspection?
Only with a written waiver you sign, dated and specific to a defect class. An unwritten waiver is how a rejected lot becomes an accepted one.
When should I escalate a production delay?
If a re-issued schedule with a version number does not arrive within two working days, and then to the contractual remedy on the named milestone.
How do I prevent the same delay next time?
Review the schedule afterwards. The usual answer is a row that had no artefact or a buyer-owned milestone with no response window.
Sources and further reading
Every figure on this page is either our own programme data or attributed below. Open the originals before you write them into a specification.
- ISO 2859-1 — sampling procedures for inspection by attributesInternational Organization for Standardization
- ICC — Incoterms rules allocating delivery risk, cost and timingInternational Chamber of Commerce
- International Trade Centre — sourcing and supply-chain management toolsInternational Trade Centre