Corporate Year-End: Delivering Suits in Batches Without Breaking the Block

A buyer for a nine-store chain wrote to us in October two years ago with a number and a deadline: thirty jackets, for staff who would be in front of clients through the last two months of the year, needed in stores before the first week of December. Straightforward enough, except six of the nine stores had their measurements in within a week and the other three took until the middle of November, by which point the first six jackets were already cut, sewn, and sitting in a box waiting for a courier. She had a choice nobody had put to her plainly before: ship the first six stores now and the last three three weeks later, or hold everyone back to leave together. She chose to ship in two batches. The question she asked us afterward, once the second parcel had gone out, was the right one and came too late to change anything: were the two batches actually the same order.

They were, because we had cut both from the same spec sheet and the same fabric bunch. But I have seen chains get a different answer to that question, and the difference was never the tailoring. It was whether anyone had written the specification down once and held it still between batches, or let it drift a little each time someone asked a small question along the way.

Why a year-end order rarely ships as one parcel

Nine stores submitting measurements on nine different schedules is the normal case, not the exception, and a chain's year-end order usually has to move regardless of who is still catching up. Staff need jackets before a specific week, not before every store has finished. That forces a choice between waiting for the slowest store, which pushes everyone's date back to match, and shipping in batches, which gets the ready stores dressed on time and leaves a second, later shipment for the rest.

Neither choice is wrong on its own. What goes wrong is treating the batches as an accident of scheduling rather than a decision, because a decision gets planned for and an accident does not. If a chain knows from week one that batch two is coming three weeks after batch one, that is a plan. If a chain finds out it has a batch two because three stores never responded to the first deadline, that is a scramble, and scrambles are where a specification gets quietly changed to save time rather than held to save consistency.

What actually breaks between batches

Nothing about our cutting or sewing changes between a first batch and a second. The atelier is the same 200 house tailors, the machines are the same, and a jacket cut in the second week of November is made to the same standard as one cut in the first week of October. What can genuinely differ, and what a chain needs to guard against on its own side, sits in three places.

The specification gets a small edit. Someone in store four asks for a slightly different lapel width after seeing batch one on a colleague, and it seems reasonable to say yes, because it is one small change for one store. Multiply that by three stores across two batches and the "matching set" a chain thought it ordered is now four or five slightly different orders that happen to have arrived in the same shipping window.

The fabric bunch shifts. A cloth that was in stock for batch one may need to be reordered for batch two if enough time has passed, and a reorder can land as a different production lot even when the bunch number on the swatch card is identical. Two rolls under the same bunch reference are not automatically the same dye lot, which is why we push every buyer, on this order and every other, to ask for the bunch reference rather than a colour name and to ask specifically whether batch two is coming off the same lot as batch one.

Measurements get re-taken differently the second time. A store that measured its own staff for batch one may have a different person doing it for batch two, weeks later, following the same form but not necessarily the same habits. We wrote at length about what actually varies across stores measuring the same programme, and the same drift shows up across time within one store just as easily as it shows up across locations within one chain.

None of these three failures look like a factory problem when the jackets arrive. They look like inconsistency, and inconsistency gets blamed on whoever cut the cloth last, which is us, even when the actual cause was a decision made three weeks earlier on the chain's side of the order.

What to lock before batch one is cut

This is the checklist we ask a chain to work through before any fabric is touched, not after batch one has already shipped and someone is asking why batch two looks slightly different.

• Style specification, written once, for every store in the programme. Lapel width, pocket style, vent, canvas construction: pick them once for the whole order and do not revisit them store by store or batch by batch.
• One fabric bunch reference for the entire order, confirmed against the physical swatch, not a colour name on a screen.
• A written answer on what happens if the fabric needs reordering between batches: does the same bunch get sourced again, and who checks the new lot against the first before cutting proceeds.
• A single measurement method, ideally the same person or a documented process, used across every store and every batch, not whichever staff member happens to be free that week.
• A cutoff date for each batch, decided at the start of the programme rather than discovered when a store misses the first one.
• A named owner who reviews every measurement sheet before it goes to production, across both batches, checking for the same things on sheet ten as on sheet one.

A programme built from that list before cutting starts has a real basis for calling batch one and batch two the same order. A programme without it is hoping the second batch happens to match the first, and hope is not a specification.

Working the calendar backward, twice

Production runs 14 to 20 working days from the point measurements and cloth are both confirmed, and that window does not compress because a chain is in a hurry at year-end. The mistake we see most often is planning that window once, for the whole programme, when a two-batch order actually needs it run twice, on two different start dates.

Work backward from the date each batch actually needs to be in stores, not forward from when the programme was approved. If batch one needs to land the first week of December and batch two the last week, those are two separate 14-to-20-working-day countdowns, each with its own cutoff for confirmed measurements, and each one competing for production capacity against every other order moving through the same weeks. A chain that only calculates the calendar for its first batch and assumes the second will simply follow along is the chain most likely to find its second shipment arriving later than promised, into a December that has no slack left in it.

Add shipping and customs clearance on top of the production window for each batch separately, and build in time for at least one remake, the same way we would ask any group order to plan for it. We covered the deadline math for a single-event group order in more detail here, and the same backward-planning logic applies to each batch of a staggered chain order, just run more than once instead of once.

What we will tell you, and what we will not promise

We will tell you, honestly, whether batch two is being cut from the same fabric lot as batch one, because we can check that against the bunch reference on both orders. We will hold a specification exactly as written across every batch you send us, because that is a matter of following the sheet, not a matter of judgement. What we will not do is promise an exact shade match across two production runs separated by several weeks without checking the lots first, because cloth dyed at different times is not always identical even under the same bunch number, and I would be careful of any supplier who tells you otherwise without looking.

That is not a hedge. It is the same distinction we ask every buyer to get in writing before an order goes in: what counts as a matching set that we can guarantee by process, cutting every batch to the same locked spec, and what counts as a variable that sits with the cloth itself, which we will flag rather than paper over.

Before the next year-end programme starts

A thirty-piece order across nine stores was never going to arrive as one box, and there is no reason it should have to. What decides whether it reads as one programme or several is whether the specification, the fabric reference, and the measurement method were locked once at the start and held across every batch that followed. Do that, and a three-week gap between shipments is a scheduling detail. Skip it, and the gap becomes the reason the second half of the chain's staff look like they belong to a different order than the first half.

If you are planning a year-end programme across multiple stores and know already that it will have to ship in more than one batch, tell us the store count and the dates each batch needs to land, and we will lay out the production calendar for each one separately, with the same specification held across all of them from the first cut to the last.