Case Study Template: From Sample to 3000 Custom Bags for a Campaign

What this template is for and how to use it

This is a working document rather than a story. It exists so that a creator running a 3,000-unit bag programme can record the plan, the actual dates, the costs and the decisions in one place, and then read it back before the next campaign. Most programme failures on crowdfunding bag runs are not dramatic; they are small slippages that were never written down, so nobody could see the pattern until the delivery date had already moved.

Use it in three passes. Fill the plan columns before the campaign launches, so the funding target and the published delivery month rest on a real schedule. Fill the actual columns as each checkpoint passes, which takes minutes per week. Then read the variance column at the end, because that is where the next campaign gets faster. The crowdfunding bag guide gives the same path as narrative; this page gives it as a form.

Minimum order quantity

500 pcs per style / colourway

Sampling

6-10 working days (12-15 for complex builds)

Bulk production

35-50 days after deposit + approved pre-production sample

Inspection

AQL 2.5 to ISO 2859-1

Trade term

FOB Xiamen

Payment

T/T 30/70

Production floor

4,950 m² SGS-verified, 137 staff, 7 lines, 149 machines

Monthly capacity

200,000 pcs per month

Programme contact

service@junyuanbags.com

The one-page programme brief

Start with a brief that fits on one page. If it cannot fit, the programme is not ready to quote, because the extra pages are almost always unresolved decisions rather than detail. The brief states what is being made, for whom, in what quantity, by when, to what standard and on what commercial terms. Everything downstream — quotation, sampling plan, inspection criteria — is derived from these seven lines.

Phase 1: specification and RFQ

The specification phase is where the schedule is won or lost, and it is the only phase entirely under the creator's control. A complete tech pack plus artwork plus quantity plus delivery month produces a quotation, a sampling estimate and a production window in one exchange. An incomplete one produces questions, and every question is a round trip that costs days. On a 3,000-unit programme the specification deserves more time than on a 500-unit pilot, because a specification error multiplies across six times the units.

1. Day 0: tech pack issued with dimensions, tolerances, materials, hardware references and construction notes.
2. Day 0: artwork pack issued with vector masters, a PDF proof, Pantone references and placement coordinates.
3. Day 1-3: RFQ sent to the shortlisted production partners with quantity, destination market and delivery month.
4. Day 3-7: quotations returned with unit cost at each volume tier, sampling estimate and production window.
5. Day 7-10: technical queries raised and answered; answers feed back into the pack as a new revision.
6. Day 10-14: partner selected, quotation accepted, sampling slot booked in writing.
7. Day 14: purchase order issued stating specification, quantity, price, AQL, trade term and payment terms.

The two outputs that matter from this phase are a written acceptance and a booked sampling slot. A quotation without a slot is an intention, and intentions do not hold a place on a line that runs at 200,000 pcs per month. Ask, in writing, for the sampling start date and for the production window that will follow approval. Our bag manufacturing page sets out the same sequence in more detail.

One discipline is worth adding to this phase because it saves disproportionate time later: freeze the revision. From the moment the sampling slot is booked, every change to the pack should be issued as a numbered revision with the date and the reason recorded. A programme running three revisions is normal; a programme running three revisions without numbers is how a sample gets approved against one drawing and a run gets built to another. The revision number also gives the inspector something concrete to measure against at AQL 2.5, which is the point at which ambiguity becomes expensive.

Phase 2: sampling rounds and revision control

Sampling on a 3,000-unit programme should be planned as two rounds at 6-10 working days each, with a possible third as contingency. Round one answers proportion, construction and whether the hero feature works. Round two confirms corrections and, if the build uses bulk materials, becomes the pre-production candidate. The common error is to treat round one as final, approve it under campaign-page pressure, and then discover construction problems in bulk.

• Write the revision list as a numbered document, each item tied to a clause in the tech pack.
• Photograph the sample against a scale reference so remote review is measurable rather than impressionistic.
• Load the sample with the intended contents and photograph it loaded; a bag that looks right empty can fail loaded.
• Confirm every hardware reference on the sample matches the pack, component by component.
• Give one person authority to approve, so two versions of the truth cannot circulate.
• Keep the approved sample physically, sealed and dated, as the inspection reference unit.

The approval also closes the last cheap window for change. Before approval, a design correction costs a re-sample; after approval it costs re-cut markers, reissued material orders and possibly a partially sewn run. Creators who treat approval as a formality and continue refining afterwards are the ones who end up publishing delay updates, and on a 3,000-unit programme the delay is visible to every backer at once.

Phase 3: pre-production approval and the deposit

This is the hinge of the whole programme. production 35-50 days after two conditions are met together: the 30% deposit under T/T 30/70 has landed, and the pre-production sample has been approved in writing. Neither alone starts the clock. Creators who believe production began on the day the campaign closed routinely lose two to four weeks to this misunderstanding, and on a 3,000-unit run that slippage is visible to every backer.

Phase 4: bulk production and in-line control

Thirty-five to fifty days covers material purchase and receipt, cutting, decoration, sewing across seven production lines, assembly, in-line quality control, finishing and packing. On a 3,000-unit order split across two colourways, the split matters: if both colourways share fabric and hardware they can run as one booking with a colour split, while different hardware finishes may require separate runs and therefore a longer window.

In-line control is the highest-value activity in this phase. A defect trend found on day 20 is correctable; the same trend found at inspection on day 46 means sorting or reworking finished goods and a second inspection, which typically adds 10-15 days. Ask for the defect log weekly rather than waiting for the final report, and treat any category that appears more than once as a trend worth investigating immediately. Our QA and QC page lists the defect classes normally logged.

Phase 5: inspection, balance payment and freight

Pre-shipment inspection to AQL 2.5 under ISO 2859-1 is the gate before cargo leaves. It is a sampling procedure with defined sample sizes and accept and reject numbers, not a promise of perfection. A pass releases the 70% balance; a fail triggers rework, re-presentation and a second inspection. From FOB Xiamen, ocean transit runs 18-30 days to the US West Coast and 28-38 days to Northern Europe, with air at 3-8 days if part of the run is needed early.

Two further controls make this phase predictable. First, ask for a first-off approval: the first fully decorated unit off the line, photographed and measured before the run continues. It catches decoration errors at unit one rather than at unit three thousand. Second, ask for the weekly status to state units completed against the plan, because a line that is two days behind on day 20 is a conversation you can still influence, while the same two days discovered on day 44 is a delivery update.

Structuring a 3,000-unit order across colourways

Three thousand units sounds like one order and is usually two or three. Because the minimum is 500 pcs per style and per colourway, the way the total is split determines both the price and the schedule. The safest structure for a first large run is a hero colourway at the majority volume and one secondary colourway, with both priced during the original RFQ and both using the same fabric and hardware so they can be booked as a single production run with a colour split.

The decision rule is to concentrate volume until demand is proven. A hero colourway at 2,000 units produces a better unit price, a simpler inspection and a shorter window than three colourways at 1,000 each. Colourways can be added on re-order once the pledge manager data shows which colours backers actually want, and because the artwork and tooling already exist the second run develops quickly. The low minimum production page covers how splits are negotiated.

Cost model template with volume tiers

Record the cost model at every tier you requested, not just at the tier you ordered. The point of the table is to make the next decision easy: if a stretch goal unlocks or a re-order becomes viable, you will know the price without reopening the conversation. Include the one-off lines separately, because they are the reason a re-order is cheaper than a first run.

Two observations are worth recording beside this table. First, the one-off charges are fixed, so they are a much larger share of a 500 pcs run than of a 3,000 pcs run: that is the arithmetic behind volume pricing. Second, the one-offs do not repeat on a re-order, which is why the second run of the same specification is cheaper per unit even when the quantity is identical.

Risk register: what went wrong and what it cost

Every programme has at least one incident. The value of writing them down is that the same incident rarely needs to happen twice, because the mitigation is usually a specification change or a process change that can be applied at the start of the next campaign. Record the incident, the root cause, the days lost and the mitigation that would have prevented it.

• Record the root cause, not the symptom: a substituted component is a specification failure, not a purchasing one.
• Convert every incident into days, because days are what backers notice.
• Write the prevention as a change to the pack or the process, not as a reminder to be more careful.
• Review the register before the next RFQ and apply every mitigation to the new tech pack.
• Share the register with your production partner; they can often prevent the recurrence directly.

Metrics worth recording for the next campaign

A handful of numbers make the next campaign materially easier to plan, because they replace assumptions with experience. Record them at the end, while the detail is still fresh, and store them with the tech pack rather than in an email. The six below are the ones that most affect schedule and cash.

1. Actual sampling days per round, compared with the 6-10 working day estimate.
2. Number of revision items raised per round, which predicts how many rounds the next design will need.
3. Defect rate recorded at inspection, by severity class, against the AQL 2.5 threshold.
4. Actual transit days from FOB Xiamen to your fulfilment point, by mode.
5. Landed cost per unit including freight, duty and inland delivery, not just the FOB price.
6. Attrition rate between funded backers and shippable units, which sets the next order quantity.

Fill-in template: your own campaign bag case study

Copy the block below into your own document and complete it as the programme runs. The fields are deliberately short: if an entry takes more than a sentence, it belongs in the tech pack instead. Completed properly, this becomes the briefing document for your next campaign and the fastest possible way to brief a new production partner.

• Programme name, product category and target launch month.
• Quantity ordered, by style and colourway, and the final quantity shipped.
• Tech pack revision number and the date it was frozen.
• Sampling: rounds used, working days per round, revision items per round.
• Approval: date the pre-production sample was approved in writing and the date the deposit was released.
• Bulk: start date, completion date and actual days against the 35-50 day window.
• Inspection: date, standard used, defect rate recorded, outcome.
• Freight: mode, transit days, clearance days, receipt date at fulfilment.
• Cost: FOB unit cost, one-off charges, landed cost per unit.
• Variance: planned versus actual for every date, with the cause recorded.

When your brief is complete, request a quotation and attach the tech pack and the artwork. As your production partner we will confirm the sampling plan, the production window and the inspection criteria before the first deposit is discussed. The sample prototyping page and the rewards fulfilment page cover the two ends of the same programme in more depth.

• Crowdfunding bag sample prototyping
• Bag manufacturing for campaign creators
• Kickstarter campaign bag QA and QC
• Crowdfunding rewards fulfilment
• Low minimum bag production for creators
• Custom bags for Kickstarter campaigns
• Request a quotation

Frequently Asked Questions

People Also Ask