After the First Collection: Feedback, Reorders, Cash Flow Awareness, and Next Steps

Use the First Collection as Data, Not Drama

Your first collection is a live test: it reveals what customers actually buy, how products perform in the real world, and where operations strain. The goal after launch is not to “fix everything,” but to create a simple system that turns results into a few high-impact decisions: what to reorder, what to revise, what to discontinue, and what to build next.

What to measure (minimum viable scorecard)

• Sales velocity: units sold per week per SKU (and per size/color).
• Sell-through: % of units sold out of units received.
• Return rate: returns / shipped orders (and return reasons).
• Gross margin reality: margin after discounts, shipping subsidies, packaging, and payment fees.
• Customer signals: reviews, fit notes, repeat purchase rate, customer service tags.

Keep this scorecard in one place (a spreadsheet is enough). The key is consistency: update weekly for the first 8–12 weeks after launch, then biweekly.

Collect Feedback Systematically (Without Overwhelm)

Feedback becomes actionable when it is structured. You want three streams: (1) post-purchase survey, (2) return/exchange reason analysis, and (3) fit notes from real bodies.

1) Post-purchase survey (automated, short, timed)

When to send: 7–14 days after delivery (enough time to try on and wear once). If you sell occasionwear, adjust timing to the event window.

How to keep response rates healthy: 5–8 questions max, mostly multiple choice, one optional open text. Offer a small incentive only if needed (e.g., early access to restocks), but avoid training customers to expect discounts.

Continue in our app.

You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.

Or continue reading below...

Download the app

Example survey questions (copy/paste):

• How would you rate the overall quality? (1–5)
• How did the fit feel? (Too small / Slightly small / True / Slightly large / Too large)
• Which area was the biggest fit issue? (Shoulders / Bust / Waist / Hips / Length / Sleeve / Rise / Other)
• Did the product match the photos and description? (Yes/No + optional comment)
• What did you wear it with or where did you wear it? (Work / Weekend / Event / Other)
• What almost stopped you from buying? (Price / Sizing uncertainty / Fabric concerns / Shipping time / Didn’t know brand / Other)
• Would you buy from us again? (Yes/No/Maybe) Why?

Step-by-step setup:

1. Write the 5–8 questions and decide which answers you can quantify.
2. Set one automated send time after delivery.
3. Create a simple dashboard: count responses by SKU and by size.
4. Review weekly: look for repeated patterns, not one-off opinions.

2) Return and exchange reason analysis (make it mandatory data)

Returns are expensive, but they are also the clearest signal of friction. The goal is to capture a consistent reason code for every return/exchange, then connect it back to product and content changes.

Return reason codes (use a fixed list):

• Fit: too small
• Fit: too large
• Fit: specific area (bust/waist/hips/length/etc.)
• Quality: construction issue
• Quality: fabric feel/comfort
• Not as described (color, transparency, weight)
• Changed mind
• Damaged in transit
• Late delivery

Step-by-step:

1. Require a reason code for every return/exchange request.
2. Add a free-text field: “Tell us what didn’t work (optional).”
3. Weekly, export returns and group by SKU + reason code.
4. Flag any SKU with: (a) high return rate, or (b) one reason code dominating.

Practical example: If 60% of returns for a trouser are “Fit: too large in waist,” that’s not a marketing problem. It’s either grading, pattern, or size guidance (or all three).

3) Fit notes (turn subjective feedback into pattern actions)

Fit notes are most useful when they include body measurements and the size worn. You can collect them from: customer emails, DMs, exchanges, and a small group of volunteer customers.

Fit note template (store in a spreadsheet):

Step-by-step:

1. Standardize what you ask for when someone mentions fit (height + key measurements + size worn).
2. Log every fit comment into the same table.
3. After 20–30 entries per key style (or fewer if volume is low), look for clusters.
4. Translate clusters into pattern actions (e.g., add length, adjust sleeve cap, change waist shaping).

Turn Feedback Into Design Revisions and Clearer Size Guidance

Not all feedback should change the product. Separate changes into: (1) product revisions, (2) size guidance/content fixes, (3) quality control fixes.

A simple triage rule: fix the cheapest lever first

• If the product is fine but customers are confused: update product page copy, add a fit note, improve photos, clarify fabric weight/opacity.
• If the fit is consistently off: revise pattern/grade and update size chart.
• If the quality is inconsistent: tighten QC checkpoints and supplier instructions.

Size guidance upgrades that reduce returns

Use your data to make sizing more predictable. Aim to answer: “What size should I buy?” without forcing customers to guess.

High-impact improvements:

• Product-specific fit callouts: “Runs small in bust; if between sizes, size up.”
• Garment measurements: include key finished measurements (e.g., chest, length, inseam) for each size.
• Model info: model height + key measurements + size worn, plus a second model if possible.
• Fit intent: “Designed for a relaxed fit” vs “close fit.”
• Fabric behavior: stretch %, drape, shrink risk, thickness/opacity notes.

Step-by-step: turning return data into size guidance

1. Pick the top 1–3 SKUs with the most sizing-related returns.
2. Identify the dominant issue (e.g., “too small in hips”).
3. Add one clear sentence to the product page addressing it.
4. Add garment measurements for the relevant area (e.g., hip circumference per size).
5. Monitor return reasons for 2–4 weeks to see if the code distribution changes.

Design revision log (so changes don’t get lost)

Create a “Revision Log” per SKU so you can track what changed and why.

SKU: Dress 02
Issue: Returns - too tight in bust (42% of returns)
Evidence: 18 surveys + 9 return notes
Decision: Pattern revision
Change: +2 cm bust ease in sizes S–L; adjust dart intake
Content update: Add note 'If between sizes, size up for bust comfort'
Target date: Next production run
Owner: You

Basic Cash Flow Awareness (Timing Matters More Than Profit on Paper)

After the first collection, many brands feel “busy” but cash-tight. That’s usually a timing issue: expenses happen upfront, while income arrives later (and may be reduced by returns, fees, and taxes). Cash flow awareness means mapping when money leaves and when it returns.

Understand the cash flow timeline

• Before production: sampling, materials, deposits, packaging orders.
• During production: progress payments, freight, duties (if applicable).
• After launch: marketing spend, fulfillment costs, customer service time.
• After sales: payment processor holds, refunds, chargebacks, taxes due later.

Build a simple cash flow calendar (12-week view)

You don’t need complex accounting software to start. Use a spreadsheet with weeks across the top and categories down the side.

Step-by-step:

1. List all known upcoming payments by date (rent, software, packaging, production balance, shipping supplies).
2. Estimate weekly inflows from sales (be conservative; use recent weekly average).
3. Subtract expected outflows weekly.
4. Add a line for “tax set-aside” and “reserve set-aside.”
5. Track your lowest projected cash week (your “cash pinch point”).

Production deposits and reorder cash planning

Reorders often require a deposit (commonly 30–70%) before you receive any new revenue from that stock. Plan reorders based on cash timing, not just demand.

Practical example: If a reorder costs $8,000 and requires a 50% deposit, you need $4,000 cash now, plus enough to cover operating expenses until the stock arrives and starts selling.

Set aside taxes and reserves (so growth doesn’t create a crisis)

• Tax set-aside: move a fixed percentage of revenue (or profit, depending on your tax system) into a separate account weekly.
• Returns reserve: hold back a small % of sales as a refund buffer, especially during the first months when return rates are unknown.
• Operating reserve: aim for a baseline (e.g., 4–8 weeks of core expenses) over time; start small and build.

Simple rule you can implement immediately: every payout day, split the incoming cash into buckets: operations, taxes, reserves, and owner pay (if applicable). Automate transfers if possible.

Decision Paths: Reorder, Discontinue, or Expand Responsibly

Use a decision tree so you don’t rely on gut feel. Your first collection will have “winners,” “maybes,” and “learners.” Treat each category differently.

When to reorder (and how much)

Reorder when you have evidence of repeatable demand and the product is operationally stable (low defect/return issues).

Reorder triggers (choose 2–3):

• Sell-through > 70% within your planned selling window (e.g., 4–8 weeks).
• Consistent weekly sales velocity (not just launch spike).
• Low return rate or returns are not due to fixable product flaws.
• Waitlist/back-in-stock requests exceed a minimum threshold you set.
• Cash flow can support deposit + operating expenses until delivery.

Step-by-step reorder sizing:

1. Calculate average weekly unit sales for the SKU over the last 3–4 weeks.
2. Multiply by lead time weeks + a buffer (e.g., 20–30%).
3. Adjust by size curve based on what sold (don’t reorder the original curve blindly).
4. Subtract expected returns if return rate is meaningful.
5. Confirm cash: deposit + freight + packaging + operating runway.

Example: If a top sells 12 units/week, lead time is 6 weeks, buffer 25%: 12 × 6 = 72; 72 × 1.25 = 90 units. Then allocate sizes based on actual sales mix (e.g., S 20%, M 45%, L 25%, XL 10%).

When to discontinue (or pause) a style

Discontinue when the style ties up cash and attention without a clear path to improvement.

Discontinue triggers:

• Low sales velocity after initial launch period, even with adequate visibility.
• High return rate due to fundamental product issues that require major rework.
• Margin is too low after real costs (discounting, shipping, fees).
• Operational complexity is high (difficult fabric, high defect rate, time-consuming fulfillment).

Step-by-step decision:

1. Identify the main failure mode: demand, fit, quality, price perception, or visibility.
2. If visibility was low, test a small content/merchandising change first (photos, copy, fit note, styling).
3. If fit/quality is the issue, estimate revision cost and timeline.
4. Compare: revision cost + time vs. expected margin and demand.
5. Choose: discontinue, revise for next cycle, or keep as-is with clearer guidance.

How to expand the range responsibly

Expansion should reduce risk, not multiply it. The safest expansions reuse what already works: the same pattern block, the same fabric family, the same trims, or the same customer occasion.

Option A: Add colorways (lowest complexity if fabric is stable)

• Do it when: the style is a proven seller and returns are low.
• Watch for: color affecting opacity, dye lot consistency, and photography accuracy.
• Practical move: add 1 new colorway at a time, not 4.

Option B: Add sizes (high impact, but plan carefully)

• Do it when: you see repeated “I would buy if you had my size” messages, and you can support grading, fit testing, and inventory.
• Watch for: needing pattern adjustments beyond simple grading (proportions change).
• Practical move: expand one direction first (e.g., add XL/XXL or add XXS/XS) on your best-selling silhouette.

Option C: Add complementary products (only if it supports the hero)

• Do it when: you can clearly explain how it completes an outfit and shares the same customer use-case.
• Watch for: adding a totally new category that requires new fit expertise and new suppliers.
• Practical move: add one “supporting” item (e.g., a top that pairs with your best-selling skirt) rather than launching a full new category.

Practical Review Framework: What Worked, What Didn’t, What’s Next

Run a structured review at a fixed time (e.g., 6–8 weeks after launch, then again at 12 weeks). Keep it short, evidence-based, and tied to actions.

1) What worked (capture repeatable wins)

• Which SKUs had the best sales velocity and why (price, silhouette, fabric, photos, styling)?
• Which sizes sold fastest (update your size curve)?
• Which channels converted best (email, organic, ads, in-person events)?
• Which messages customers repeated (comfort, versatility, compliments)?

2) What didn’t work (name the failure mode)

• Which SKUs underperformed: demand issue or visibility issue?
• Top 3 return reasons overall and by SKU.
• Top 3 customer service issues (shipping, sizing confusion, quality concerns).
• Operational bottlenecks (packing time, stock accuracy, late deliveries).

3) Prioritized action list for the next collection cycle

Limit yourself to a small number of actions that move the needle. Use an impact/effort filter.

4) A lightweight weekly routine (so insights don’t pile up)

• 30 minutes weekly: update scorecard (sales, returns, cash).
• 30 minutes weekly: tag feedback into categories (fit, quality, description, shipping).
• 60 minutes biweekly: decide 1–2 changes to implement (content updates first, then product/QC).
• Monthly: review reorder/discontinue list and cash pinch point.