What one week of late tech packs costs a $20M apparel brand

It is Tuesday morning at a $20M contemporary womenswear brand. The design director is still finishing a colorway on a jacket that was supposed to release to the factory last Wednesday. The production coordinator has a WhatsApp thread with the mill asking, again, which of three lining weights is final. The sourcing lead is holding a bulk quote that expires Friday. Downstream, an allocator is trying to confirm a March 15 ship window for a major specialty account that ordered the style at market three months ago. Nobody in the building thinks of this as a crisis. It happens every season. That is the problem.

What is the real cost of late tech packs for a $20M apparel brand?

When operators ask about the cost of late tech packs apparel brands absorb each season, they usually expect a soft answer about missed calendars. The honest answer is more expensive than that. A late tech pack is not a design problem. It is the first domino in a chain that ends at a retailer chargeback, an air freight invoice, or a markdown taken in month nine to clear inventory that should have landed in month six.

A tech pack is late when any component the factory needs to quote and cut, so construction callouts, graded specs, BOM with confirmed trims, approved colorways, and final artwork placement, is not locked by the date the critical path requires it. Not the date design wants. The date the factory needs it to hold the quoted price, the booked capacity, and the promised ex-factory. Those three things move together, and when the tech pack slips, all three move against you.

At a $20M brand running roughly 250 to 400 SKUs per season across two to three drops, one style slipping a week is not the story. The story is that ten to fifteen styles slip a week, every season, and the cost stacks silently.

Why does a week of slippage matter so much?

Because the apparel calendar is not linear. It is a set of dependent windows, and each one is shorter than the last.

On most mid-market production calendars, the gap between tech pack release and ex-factory sits around 90 to 120 days for cut-and-sew, less for basics, more for anything with wash or specialty trim. Inside that window, roughly two weeks are protolyping, two weeks are fit rounds, one to two weeks are PPS approval, and the rest is bulk. Slip the tech pack by a week and you do not get a 90-day window that starts a week later. You get an 83-day window, because the retailer ship date does not move, and every step downstream is now compressed.

Compressed steps are expensive steps. A PPS that would have shipped by sea now flies. A bulk run that would have been quoted in a normal window is now quoted with an expedite premium. A fit round that would have caught a sleeve issue gets waived to protect the calendar, and the issue surfaces later as a returns spike.

From the vendor evaluations I sit in on each week, this is the pattern buyers describe when they finally start looking at PLM. They rarely open with “our tech packs are late.” They open with “our air freight is out of control” or “our chargebacks doubled last year.” Two questions in, we are talking about design handoff and version control on the tech pack. The cost lives at the end of the chain. The cause lives at the start.

What actually breaks when the tech pack slips a week?

Five things break, and they break in sequence.

First, the sample round compresses. The factory still needs to fit the garment. If the tech pack lands late, the proto ships by air instead of sea, adding $80 to $200 per sample depending on lane and weight. On a season with 300 styles and two sample rounds per style, that is meaningful money before a single bulk unit ships.

Second, the bulk quote loses its hold. Factories quote against a booking window. Miss the window and the quote reopens, usually up two to five points because the mill has already committed the yarn or fabric elsewhere. On a $40K bulk PO, that is $800 to $2,000 per style, and it is money that used to be margin.

Third, capacity slips down the factory’s line. When your tech pack is late, someone else’s on-time program takes the slot. You now cut in a slower week, with a smaller team, and your ex-factory moves out. Sometimes the factory absorbs this. Usually they do not.

Fourth, the retailer ship window is now at risk. Wholesale ship windows are typically 14-day corridors. Miss the start and you are shipping into a narrowing window. Miss the end and the retailer either cancels the PO or takes it at a markdown allowance, and either way you eat a chargeback. If retailer chargebacks are running above one percent of wholesale revenue, the tech pack calendar is usually part of the cause, and no amount of warehouse discipline will fix it.

Fifth, DTC allocation gets messy. The units you planned for the site launch are now landing three weeks late, past the window the paid media plan assumed. The launch either slips or runs against inventory you do not have yet, which is where oversell happens. On a $15M brand running wholesale plus DTC plus 3PL, we already see 2 to 3 percent oversell rates at peak; late tech packs push that number up, not down.

What is the actual dollar cost of one late week?

Here is the back-of-envelope for a single style at a $20M brand, holding a $50K bulk PO and a wholesale plus DTC split. These are conservative and defensible.

• Expedited proto and PPS freight: $400 to $800 per style, per round
• Bulk quote drift: two to five points on $50K, so $1,000 to $2,500
• Air freight on bulk to hold the ship window: three to five points of PO value on partial air, so $1,500 to $2,500 per style if half the PO flies
• Retailer chargebacks from missed ship windows: 3 to 8 percent of the wholesale portion of the PO if the window is missed at all, so $900 to $2,400 on a $30K wholesale allocation
• Markdown risk on units landing late to the floor: often 10 to 20 percent of the DTC portion clears at reduced margin, so $2,000 to $4,000 per style

One style, one week late, at a $20M brand: $5,800 to $12,200 in absorbed cost. Multiply that by the ten to fifteen styles that slip in a typical season and you are looking at $58,000 to $183,000 per season, per drop. Two drops a year and the number moves into the $120K to $360K range. That is real EBITDA on a $20M brand.

The range is wide because the outcome depends on which downstream steps you defend. Brands that defend the retailer ship window pay in air freight. Brands that defend the margin pay in chargebacks and cancels. Brands that defend nothing pay in markdowns. Most brands pay in all three.

Why is this a BP1 problem, not a production problem?

This is where most teams misdiagnose. When tech packs run late, the reflex is to push harder on production, add a coordinator, tighten the WhatsApp threads with the factory. That treats a symptom. The root cause sits earlier, in Breakpoint 1 of the 6 Breakpoints framework, where product data starts fragmenting.

BP1 shows up when the tech pack lives in three places at once. The construction spec is in a shared Google Sheet. The artwork and flats are in Illustrator files on a designer’s laptop. The BOM is in a PLM tool nobody has updated since last season, or in a separate spreadsheet the sourcing lead maintains. Colorways are in a Dropbox folder. Fit comments live in email threads.

When these fragments are out of sync, the tech pack is never actually “done.” It is “done as of last Thursday.” A designer updates a sleeve length in Illustrator and it never makes it to the spec sheet. Sourcing sends a version to the factory that is missing the new trim. The factory quotes the wrong construction. The proto comes back wrong. The fit meeting slips a week. That week is the week we just costed.

The fix is not process discipline. Process discipline degrades under pressure, and apparel calendars are pressure. The fix is architectural: one live tech pack that carries specs, BOM, colorways, artwork, and fit history in one record, with a critical path that flags slippage automatically. That is what Uphance PLM is built around, and specifically why the bidirectional Illustrator plugin matters. Designers stay in Illustrator, but the flats, colorways, and artwork sync both directions with the tech pack in real time. No file uploads, no version drift, no “which PDF is current.” The tech pack is the single record.

The critical path calendar is the other half. Every style and season tracks against milestones and dependencies. When one milestone slips, the ones downstream flag automatically. You see a week of slippage in week one, not week six when the freight bill lands. Most brands find out about tech pack slippage retroactively, when it is already too late to protect the ship window.

Where does this show up in evaluations?

The objections I hear most often when a $10M to $30M brand evaluates PLM are about scope and change management. “We already have a PLM.” “Design will not adopt anything new.” “Our tech packs are fine, the factory issues are the problem.”

The first two are real and worth taking seriously. The third one is almost always wrong. When we walk through a specific late style with a prospect, tracing back from a chargeback or a markdown, the trigger is a tech pack version issue in eight out of ten cases. A trim spec that changed after the BOM was quoted. A colorway that was approved verbally but never updated on the tech pack. A graded spec that referenced the wrong base size. The factory did what the paperwork said. The paperwork was wrong.

The reason “we already have a PLM” is worth pressing on is that most mid-market PLMs are essentially structured file storage. They hold tech packs. They do not connect design changes back to Illustrator, they do not enforce a critical path, they do not talk to the production and sourcing operating model downstream. A PLM that stores tech packs but does not move information between design, sourcing, and production is not solving BP1. It is filing BP1.

The adoption objection is fair. The way through it is not more training. It is picking a PLM that meets designers where they already work. If the designer never leaves Illustrator, adoption stops being a fight. If the sourcing lead sees the same tech pack the designer edits, the WhatsApp thread with the factory shortens by half.

What should a $20M brand do about it this season?

Start by measuring, not fixing. For the next four weeks, log every tech pack against its critical path date. Note when it went to the factory, what changed between first send and final, and how many downstream events had to compress to hold the ship window. Score styles against the product data scorecard if you want a structured way to do this. Most teams cannot fix what they have never counted.

Then look at the last two seasons of chargebacks, air freight invoices, and markdown taken. Tag each event back to a root cause. If more than a third trace back to product data or tech pack timing, BP1 is your cost center, not your factory.

The uncomfortable POV: at a $20M brand running wholesale, waiting until next year to fix the tech pack workflow is a decision to absorb another $120K to $360K in avoidable cost. That is not a scaling problem. That is a today problem, and it is one of the few operational fixes in apparel where the payback shows up in a single season.

The line that gets missed

Late tech packs do not look expensive on the day they are late. That is why they persist. The cost lands two, three, sometimes six months later, on line items that nobody traces back to design handoff. Air freight looks like a logistics problem. Chargebacks look like a warehouse problem. Markdowns look like a merchandising problem. They are all, in many cases, the same problem, showing up in different departments.

Brands that fix this stop paying for it. Brands that do not, keep paying for it, quietly, every season, on lines they have stopped questioning. The tech pack is where product operations either hold or break, and at a $20M brand, the difference between the two is worth roughly one FTE of margin per year.