Custom Bag Lead Times: What to Demand in Writing

Why a verbal timeline is not a timeline

Most bag disputes are not about quality. They are about a date that two people remember differently, and the reason they remember it differently is that it was never written down. One party remembers being told six weeks. The other remembers saying six weeks if the material arrives. Both are telling the truth, and the gap between them is where a campaign's delivery promise dies. The purpose of a written timeline is not to create a legal instrument, although it helps. It is to make the two memories identical by making them external.

There is a second and subtler benefit. Writing a timeline forces the two parties to agree what each date is triggered by, and that is the conversation that actually prevents delays. A sample that starts when the tech pack arrives is a different commitment from a sample that starts when the deposit clears, and the difference is several days. A bulk order that starts on release is a different commitment from a bulk order that starts on deposit, and the difference can be two weeks. These distinctions are invisible in conversation and obvious in writing.

The third benefit is that a written timeline can be referenced without a confrontation. When a date is at risk, the useful message is not an angry one. It is a short one: per the schedule, the sample finish was the 14th, and we are now on the 18th. That sentence works because the schedule exists. Without it, the same message becomes an accusation and the conversation becomes about tone rather than about the four days. For the wider working relationship, the partner onboarding reference covers what else should be in writing before production starts.

The six dates every bag programme has

Every bag programme, regardless of format, quantity or complexity, contains six dates. Naming them separately is what makes a timeline usable, because each has a different owner and a different thing that can go wrong. Most programme schedules collapse three or four of them into one, and that is where the slippage hides. A schedule that says samples in two weeks and then production in six has hidden four dates inside two, and all four can move without either headline changing.

The overall shape of a sourcing programme is set out in the bag manufacturing guide for campaign creators; what follows is the schedule inside it. Two of those six dates belong to the creator, and this surprises people. The sample cannot start until the pack and the deposit are with the production team, and the bulk cannot be released until the creator releases it. A creator who treats the schedule as something that happens to them, rather than something they operate, will lose time at both points and will attribute the loss to production. Being clear about which dates you own is the fastest available improvement to a bag timeline, and it costs nothing.

The two dates that most often get collapsed are bulk release and bulk finish, and the collapse is expensive. A programme that says production takes 6 weeks, measured from the moment the deposit is paid, will produce an argument if the release comes 3 weeks after the deposit. A programme that says bulk finishes 35 to 50 days from release will not, because the six to eight weeks of calendar between deposit and goods are then visibly composed of three weeks the creator spent deciding and 40 days of production. Both are true descriptions of the same period. Only one of them is a usable schedule.

Sampling: 6 to 10 working days and what working excludes

The standard sampling figure is 6 to 10 working days, and the complex construction figure is 12 to 15 working days. Working days excludes weekends and public holidays, which in practice means a sample requested on a Thursday is not a sample in six days' time; it is a sample in six working days, which on a calendar is around eight to ten days. Creators who convert working days directly into calendar days are the source of their own disappointment, and this is the single most common arithmetic error in a bag timeline.

The second thing to establish in writing is what the clock starts from. Six to 10 working days from a confirmed and complete tech pack is a materially different commitment from six to 10 from a conversation, because the pack is the thing that makes the sample buildable. A pack that arrives with an unresolved material call-out, a missing hardware reference or an unspecified colour will generate questions, and every question adds a day while it is answered. Ask for the clock to start on pack confirmation and make sure your pack is complete enough to be confirmed.

Complexity is the third variable and it should be named in the schedule rather than discovered in it. A complex construction in this context means one that needs tooling, moulding, die-cutting, multiple material types or a new pattern drafted from scratch rather than adapted. A moulded EVA shell, a bag with a die-cut foam insert, a style with a leather-trimmed handle and a structured build with a moulded base are all complex. A flat tote, a simple drawstring and a basic pouch are not. Naming which side of the line your product is on before sampling starts is worth more than any discussion afterwards. The sampling standard reference covers the comparison in detail.

Bulk: 35 to 50 days and what starts the clock

The bulk figure is 35 to 50 days, and the range is real rather than hedged. A simple style at a moderate quantity in an available material sits at the short end. A complex style, a large quantity, a material that has to be ordered, or a style with printed or embroidered panels that have their own production step sits towards the long end. The schedule should state which end your order is expected at, and it should say why. A schedule that says 40 days without a reason is a number; one that says 45 days because the printed panels add a step is a plan.

The clock starts on release, and release should be a written event with a stated condition. The condition is usually one of three things: approval of the pre-production sample, arrival of the material, or receipt of the deposit. Stating which one it is prevents the most common bulk dispute, which is a production team that started and a creator who did not think they had asked it to. A written release with a condition also protects the creator, because goods produced before the condition was met are goods produced at the production team's risk rather than theirs.

Inside the 35 to 50 days there are operations that a creator can influence, and naming them makes the range meaningful. Cutting, printing or embroidery, sewing, trimming, inspection and packing each take a share, and the two that most often expand are printing and inspection. Printing has its own setup and its own drying or curing time and it sits before sewing. Inspection failing its first pass adds a rework cycle. A schedule that names the stages lets a creator see where a delay is occurring, rather than receiving a single revised date and no information. The partner onboarding reference sets out the milestone structure we would recommend.

Approval gates that stop the clock

An approval gate is a point at which the schedule pauses until the creator acts, and they exist at four places in a bag programme: approval of the tech pack, approval of the first sample, approval of the pre-production sample and approval of the print or embroidery strike-off. Each is a genuine quality control and each is also a place where a week disappears. The purpose of naming them in the schedule is not to remove them. It is to make the elapsed time attributable, so that a six-week programme that took ten weeks can be accounted for.

• Tech pack approval before the sample clock starts, because a sample built to an unapproved pack is a sample that will be rebuilt.
• First sample approval before any revision, because revisions without an approved baseline are unbounded.
• Strike-off approval for print or embroidery before bulk panels are made, because colour is the slowest thing to correct.
• Pre-production sample approval as the release condition for bulk, which is the gate that should hold the production start.

The approval that does the most damage is the one that never arrives. A creator who receives a sample, looks at it, forms a view and does not communicate it has stopped the programme, and the production team will usually not chase for several days because they have other work. The discipline that prevents this is a stated response window on both sides: the creator responds within a stated number of working days, and the production team responds to that response within a stated number. Two numbers, agreed once, remove the largest invisible delay in a bag programme.

The other discipline is to approve in writing, including approval with changes. A verbal approval with three changes attached will be remembered as an approval by one party and as a rejection by the other. A written note that says approved subject to the three listed changes, with the changes themselves listed, produces a single shared understanding and it also becomes the revision instruction. For what to check before signing that note, the sample approval reference is the concrete list.

Material lead time is a separate date

Material arrival is the date most often omitted from a bag schedule and the one that most often causes a delay, because it is not a production date and it is not a creator date. It is a production partner date that sits between them. A fabric that is in stock at the mill arrives in days. A fabric that has to be woven or dyed to order arrives in weeks, and a custom-dyed webbing or a non-standard zip tape can take longer than the bag itself takes to sew. At 500 pcs per style and per colourway, a made-to-order lot is usually close to the smallest quantity a mill will run, which is why custom colours carry both a surcharge and a longer lead time. Asking for the material date as a separate line in the schedule is the cheapest risk reduction available.

There are three questions to ask about each material line, and they should be asked at quotation stage rather than at release. Is the material in stock or made to order? If it is made to order, what is the lead time and what is the minimum lot? And if the lot is not available, what is the approved substitute? The third question is the one that prevents a delay, because an unapproved substitute discovered at release produces a conversation at the worst possible moment, whereas an approved substitute decided in advance produces a decision.

The material date also matters for a specific and avoidable reason: it determines whether the 35 to 50 day clock can start at all. Bulk cannot begin on release if the fabric lands two weeks later, and a schedule that shows release and bulk finish but omits material arrival will show a delay that appears to come from nowhere. Putting material arrival between release and production start makes the shape visible, and it usually reveals that the right move is to order material at deposit rather than at release, which removes two to three weeks from the calendar at no cost beyond earlier payment.

Buffers: how much and where

A buffer is time added to a schedule deliberately, and the two mistakes are adding none and adding one at the end. Adding none produces a schedule that is wrong the first time anything moves. Adding one at the end produces a large single buffer that hides where the time was lost and gets consumed by the first problem. The correct approach is three small buffers at the three places where slippage actually occurs, rather than one large one at the end where it is not needed.

The three places are after sampling, before release and after bulk finish. After sampling, because a second sample round is common and a schedule with no room for one will absorb it from the production window. Before release, because the creator's own decisions are the least predictable part of the programme, and a schedule that assumes immediate release will be wrong. After bulk finish, because inspection rework and freight booking both sit there and both can take a week. Three buffers of a few days each are more useful than one of a month.

The other buffer question is what the public date should be, and it should be a later date than the internal one. A campaign page should not carry the internal schedule. It should carry the internal schedule plus the buffers plus a stated freight and customs allowance, and it is worth saying that the internal date and the published date are two different numbers by design. Creators who publish their internal date are publishing a number they will miss, and the follow-on is a support burden rather than a production problem. The delivery date guide covers the published side of the arithmetic.

Payment milestones that move with the dates

The standard terms are T/T with 30 percent deposit and 70 percent balance, and the two payments attach to two dates. The deposit attaches before bulk begins, and the balance attaches before shipment. Making that attachment explicit in the schedule is what prevents the most awkward moment in a bag programme, which is finished goods sitting on a production floor waiting for a payment that has not been arranged. The production team cannot ship without the balance and the creator often does not arrange it until asked, and the gap costs days.

There are three details worth getting in writing on the payment side. The currency, so that the exposure sits in one place and a conversion does not become a delay. The bank and account details, confirmed through a channel that is not the one that carried the last change. And the date on which the balance falls due in relation to the ex-factory date, which should be before it and not on it, because an international transfer takes time to land. A balance sent on the ex-factory date arrives after it.

The third point is about the deposit and the material. Because material lead time sits before production start, and because a custom material may need to be ordered before release, there is a real question about whether the deposit covers the material purchase. In most programmes it does, and that is efficient, but it means the deposit is spent before any bag exists. The protection for the creator is a written material list with the quantities and costs stated, so that a deposit spent on material is visibly spent on something that has been bought for their order. The trade term FOB Xiamen should also be stated, so that risk transfer is unambiguous.

Delay notification clauses

A delay notification clause is an agreement that if a date will be missed, the party responsible says so within a stated period, and it is the most valuable clause in a bag schedule because it converts a surprise into a warning. Without it, a delay is discovered on the date itself. With it, a two-week delay is known nine working days before the date, which is enough time to change a freight mode, to resequence a packing plan, or to update a backer before they think of asking.

The clause should be specific in three ways. It should state the notification period, which for a bag programme is typically a few working days from the point the delay becomes known. It should state the form, which should be written, because a verbal notification is the thing this whole document exists to avoid. And it should state what the notification contains: the new date, the cause, and what is being done. A notification that says there will be a delay is not useful. One that says the date moves from the 22nd to the 29th because a material lot was rejected and a replacement is due on the 18th is.

The clause should also be reciprocal, and creators often forget this. The production team notifies delays in sampling, in production and in inspection. The creator notifies delays in approval, in release and in payment. A reciprocal clause is both fairer and more effective, because a production team that is obliged to notify a delay will usually try harder not to create one, and a creator who is obliged to notify an approval delay will usually respond faster. The mechanism works in both directions and it is worth asking for it explicitly.

A written timeline you can send

The schedule below is the form we would recommend, and it can be sent as a short document at quotation stage. It is deliberately short enough to be maintained. A three-page schedule will not be updated; a one-page one will, and a schedule that is not updated stops being a schedule and becomes a historical document. Each line has a date, a trigger and an owner, and the three buffers are visible rather than hidden in the dates.

1. Tech pack confirmed, owner creator, date stated. Sample clock starts here.
2. Sample finish, owner production team, 6 to 10 working days from confirmation, or 12 to 15 for a complex construction.
3. Sample approval, owner creator, within a stated number of working days of receipt. Approved, or approved subject to listed changes.
4. Print or embroidery strike-off approval, owner creator, before bulk panels are made.
5. Material arrival, owner production team, stated as a separate line and in stock or made to order as applicable.
6. Bulk release, owner creator, on a stated condition, usually pre-production sample approval.
7. Bulk finish, owner production team, 35 to 50 days from release, with the expected end of the range and the reason.
8. Inspection, owner production team, at AQL 2.5 to ISO 2859-1, with the register shared.
9. Balance due, owner creator, a stated number of days before ex-factory, not on it.
10. Ex-factory, owner production team, on FOB Xiamen, with freight booked.

The two lines that do most of the work in that list are the material arrival line and the release condition. The first makes an invisible supplier visible, and the second makes the production start a decision rather than an assumption. Everything else is either a number that the two parties will agree easily or an operation that will happen anyway. If you only take two things into your next negotiation, take those two and put them in the document.

What to do when a date slips

A date will slip. The useful response has three parts and none of them is anger. The first is to establish where the slip occurred, using the schedule: which of the six dates moved, and by how much. This matters because a slip in the sample finish and a slip in the bulk finish have completely different recoveries. A sample slip can often be recovered by parallel activity, by approving with changes and starting the revision immediately. A bulk slip can only be recovered by compressing what is left or by changing the freight mode.

The second is to ask what the new date is and what has changed, in writing, and to ask it the same day the slip is known. A production team that is asked on the day will usually have an answer, because they have already had to think about it. The same team asked a week later will have to reconstruct it, and the reconstruction will be less accurate. The third is to decide the recovery before communicating it: whether to accept the later date, to pay for air freight at the end, or to resequence the packing so that the most urgent units go first.

The final part is the one creators handle worst, which is telling backers. The correct sequence is to tell them once you know the new date and the recovery, not before, and to tell them in the form of a revised date rather than an apology. A message that says the goods will now ship in the week of a stated date, because a material lot was replaced, is reassuring and specific. A message that says there has been a small delay is neither. The schedule is what makes the first message possible, and it is the reason to write one before you need it.

Frequently Asked Questions

People Also Ask