Production

Apparel operations for swimwear brands: preseason, drops, and dead weeks

Apparel operations for swimwear brands: preseason, drops, and dead weeks
By Venkat Koripalli · Reviewed by Shubham Singh · · 10 min read

Picture the second week of February at a $12M swim brand. The design team is finalizing Resort 26 tech packs. The production team is chasing a Vietnam supplier who slipped shell fabric by eleven days, which pushes the first cut into a window that collides with Lunar New Year shutdowns. The wholesale team has already written orders against a linesheet that assumes an April 15 in-DC date. The DTC team is planning a March drop of carryover styles nobody has reforecast since November. And the warehouse is sitting on 40 percent of Resort 25 that did not sell through, which finance has not written down yet. Every one of those decisions was made in a different tool by a different person. None of them agree on what is actually shippable in April.

What is a swimwear brand operations playbook?

A swimwear brand operations playbook is the documented sequence of production, inventory, order, and warehouse decisions that a swim brand runs against its own calendar, not a generic apparel calendar. It defines when preseason wholesale orders close, when consumer drops release, how the same inventory pool gets allocated between the two, and what happens during the dead weeks when neither channel is producing revenue but the warehouse and the finance team still are.

The reason a swim-specific playbook matters is that swim compresses more of its year into fewer weeks than almost any other apparel category. A contemporary womenswear brand can miss a February drop and recover in March. A swim brand that misses its Memorial Day window has effectively lost a quarter. The operational tolerance for drift is close to zero, and the systems most swim brands run on were built assuming drift is fine.

Why does swim break normal apparel operations?

Most apparel operations stacks assume a four-season cadence with roughly even demand across the year and a wholesale calendar that runs six months ahead of at-once. Swim does not work that way. Swim has a preseason wholesale window that closes in September and October for the following resort and summer, a set of consumer drops that release from January through May, a peak sell-through window from Memorial Day to the Fourth of July, and then a long tail from mid-July into fall where the category effectively goes dormant for most brands that do not sell into year-round warm-weather markets.

When I started Uphance, the pattern I saw repeatedly was that seasonal categories were forcing operational decisions through tools that had no concept of a compressed calendar. A swim brand doing $12M was running preseason wholesale in one spreadsheet, drops in Shopify’s native flow, and 3PL inventory in a third system that reconciled overnight. In February the numbers agreed. In April they did not, and nobody knew which one was right when a wholesale rep asked whether they could still confirm a 400-unit reorder from a Florida boutique.

That drift is where BP2 of the 6 Breakpoints framework lives. Production and supply execution stop matching the plan the commercial team is selling against. In evergreen categories that gap is expensive. In swim it is fatal, because the recovery window does not exist.

What does the swim calendar actually look like?

A useful way to lay out the swim calendar is in four operational phases, each with its own dominant risk.

Phase one is preseason, roughly August through November. Design finalizes the range, PLM carries the tech packs, and wholesale sells against a linesheet with committed delivery windows. The dominant risk is overselling capacity or making commitments against fabric that has not been secured. This is where the critical path calendar earns its keep, because every style has a chain of dependencies (fabric approval, lab dip, size set, PP sample, bulk cut) and any one of them slipping by a week compounds into a missed in-DC date three months later.

Phase two is production and inbound, roughly November through March. Bulk is cutting, containers are moving, and the warehouse is receiving. The dominant risk is inbound slippage that the commercial team learns about too late to reallocate. If a container is going to land two weeks late, wholesale needs to know before the retailer’s cancel date, not after.

Phase three is release and sell-through, roughly February through June. Drops go live to DTC, wholesale ships against confirmed POs, and reorders start hitting the desk. The dominant risk here is channel conflict on a shared inventory pool. A DTC drop that sells through 60 percent of a style in 48 hours can eat the inventory a wholesale account was counting on for a May 1 in-DC date, and the brand finds out when the pick fails.

Phase four is the dead weeks, roughly mid-July through October. Sell-through slows, markdowns start, returns are still posting, and the warehouse is being paid to hold inventory that will not move at full price. The dominant risk is carrying cost and reactive reporting. Finance does not know the true margin on the season until eight weeks after it has ended, which means the buy for the next season is already in motion against numbers that will turn out to be wrong.

How should preseason and drops share one inventory pool?

This is the operational question that separates swim brands that run cleanly from swim brands that spend the summer firefighting. The wrong answer is to run wholesale and DTC as if they are two separate businesses with two separate inventory positions. The right answer is one physical pool with rule-based allocation.

A channel-aware ATS is the mechanism. Every SKU has a total on-hand and on-order position, and each channel sees a different available-to-sell number based on rules the commercial and planning teams set together. A style that is committed 70 percent to wholesale POs for a May in-DC window should not show 100 percent of on-hand as available to DTC in March, even if the physical units are sitting in the warehouse. That is how you oversell, and the 2 to 3 percent oversell rate we see at peak in a $15M brand running wholesale plus DTC plus 3PL is almost always driven by this exact failure.

Wholesale should not run through Shopify’s native flow. Shopify does not understand PO windows, cancel dates, retailer compliance rules, or EDI 850 to 855 to 856 to 810 sequencing. A swim brand that tries to force wholesale through Shopify ends up building a second reconciliation layer in a spreadsheet, and that spreadsheet is where the oversell risk actually lives.

What should the production calendar enforce?

The critical path calendar for swim has to enforce a few non-negotiable milestones, because slippage on any of them compounds faster than in other categories.

Fabric approval and lab dip sign-off need to close by a fixed date, because printed and dyed nylon and elastane blends have longer lead times than cotton wovens, and the mills that produce them run their own capacity calendars that do not care about your drop schedule. PP sample sign-off has to close before bulk cutting, because a swim fit issue that shows up in production is functionally impossible to recover from inside the season. Bulk shipment booking has to be locked against a specific vessel and ETA, because air freight to rescue a swim drop can eat the entire margin on that style.

The critical path should flag slippage automatically the moment a milestone moves. The bidirectional Illustrator plugin matters here because the design change that triggers a spec revision at week ten should sync to the tech pack without a manual file upload, so the factory is working from the current version and the merchandiser is not reconciling three versions of the same flat by email.

How should drops be sequenced against wholesale ship windows?

The sequencing rule most swim brands violate is releasing DTC drops on the same styles that are actively shipping to wholesale accounts in the same two-week window. The retailer expects exclusivity or at least a lead, and the DTC customer expects the drop to be in stock. Both cannot be true if the inventory pool is shared and the buy was tight.

A cleaner sequence is to release the drop to DTC either two to three weeks before the wholesale in-DC date, using a segment of the buy explicitly reserved for DTC, or two to three weeks after wholesale has landed and the retailer has had a chance to merchandise. Which side of the wholesale window the drop sits on depends on the account mix and the retailer relationship. What matters operationally is that the decision is made in planning, encoded in the ATS rules, and visible to both channels before the drop calendar is published.

What happens during the dead weeks?

The dead weeks are where reporting has to shift from reactive to operational. This is BP6 territory in the framework, and it is where finance and planning either get ahead of the next season or find themselves buying against last season’s assumptions.

Three things need to happen in the dead weeks. First, the season needs to be closed out with true landed cost margin by style, not by category. Duties, freight, and returns processing all have to be allocated back to the SKU. Returns should post to inventory in days, not weeks, because a style that shows 80 percent sell-through on paper but has 12 percent of that sitting in a returns queue is not actually at 80 percent, and the reorder decision on it is wrong.

Second, carryover has to be marked and physically segregated, because carryover styles that get commingled with new season inventory in the warehouse create pick errors that show up as chargebacks in September. Third, the buy for the next preseason has to be sized against actual sell-through curves from this season, not against the plan that was written twelve months ago.

OTB during the dead weeks can move to monthly. During preseason and the drop window it needs to run weekly. Monthly OTB during selling season is too slow to catch the reallocation opportunities that a weekly cadence surfaces.

What does this cost when it goes wrong?

The defensible back-of-envelope for a $15M brand running wholesale plus DTC plus 3PL is 6 to 9 hours per week of reconciliation across Shopify, 3PL, and wholesale systems, a 2 to 3 percent oversell rate at peak, and effectively one full-time employee doing data plumbing rather than commercial or planning work. In swim that FTE is usually a merchandiser or an operations manager whose actual job is being crowded out by spreadsheet maintenance.

The replacement pattern in this ICP band is three to five tools plus spreadsheets consolidating into one operational system. What the brand is actually buying is not software. It is the ability to answer the question a wholesale rep asks in April, whether a 400-unit reorder can ship on time, without opening four tabs and calling the warehouse.

What this means for an apparel operations team

Swim is the category where the gap between plan and execution shows up fastest, because the calendar does not forgive drift. An operations team running a swim brand in the $5M to $20M zone should treat the preseason-through-dead-weeks cycle as a single connected sequence with defined handoffs, not as four separate operational modes that different teams own in different tools.

The reason the 6 Breakpoints framework exists in the form it does is that most brands hit BP2 and BP3 in the same season, and swim brands hit them in the same month. Production drifts from the plan, inventory truth weakens, and by the time the reporting catches up the season is already over. Fixing that is a sequencing problem before it is a tooling problem, but the tooling has to support the sequence.

The practical starting point is to map the current calendar against the four phases, identify which handoffs currently happen by email or spreadsheet, and decide which of those handoffs the brand can afford to leave manual for another season. For swim, the answer is usually fewer than the team thinks.

6 Breakpoints Framework

Where is your operation on the 6 Breakpoints curve?

The assessment scores your apparel operation across all six breakpoints (product data, production, inventory truth, order flow, warehouse execution, reporting) and identifies which one is hurting you most.

Frequently asked questions

Where this fits in the Uphance platform

V
Written by
Venkat Koripalli
Founder & CEO, Uphance

Venkat is the Founder and CEO of Uphance and the author of the 6 Breakpoints of Apparel Operations framework. He writes about operational clarity for apparel brands as complexity grows across channels, warehouses, partners, and teams. His work focuses on why disconnected operations, not growth itself, create the chaos most mid-market brands feel between $5M and $100M in revenue, and on the operating-model patterns that decide whether scaling a brand strengthens execution or fractures it. He argues that the status quo is the real competitor in apparel software, and that the right move is fewer systems with deeper connection, not more dashboards.

S
Reviewed by
Shubham Singh
Solutions Consultant, Apparel Operations, Uphance

Shubham writes about evaluating ERP fit, assessing operational complexity, and how apparel brands can tell whether their current systems are helping or holding them back. As a Solutions Consultant at Uphance, he runs discovery conversations and fit assessments for apparel brands moving off patchwork stacks of PLM, PIM, inventory, and B2B tools. His articles cover ERP selection, vendor RFPs, comparison frameworks, and the operational signals that tell a brand it has outgrown spreadsheets and point solutions. He focuses on how mid-market apparel teams evaluate connected platforms against the cost of staying with what they have.

More from the blog