Custom Bags for Crowdfunding Campaigns: Timeline From Mockup to Mass Production

Why the mockup-to-mass clock starts before the campaign page

Most creators treat production as something that begins after the campaign funds. It does not. The clock starts the moment a specification is complete enough to be quoted, and everything that happens before that point — material selection, panel count, hardware references, branding method — determines how many days the later stages will consume. A creator who locks a specification eight weeks before launch enters the funding period with a known production window. A creator who locks it after funding discovers the window in public, in campaign updates, while backers count the days.

The practical consequence is that the timeline is a pre-launch asset, not a post-launch chore. Two working rounds of sampling can be completed while the campaign page is still being written, which means the reward photography shows a real unit rather than a render, and the published delivery month rests on a schedule that has already been tested once. Backers fund campaigns that look operationally credible, and an approved sample in hand is the single cheapest credibility signal available.

Below is the full path expressed as a calendar, using the numbers our production team works to on campaign programmes: a 500 pcs minimum per style and colourway, sampling at 6-10 working days, production 35-50 days, inspection at AQL 2.5 to ISO 2859-1, FOB Xiamen, and T/T 30/70 payment terms. The crowdfunding bag guide covers the same path from the design side; this article stays on the calendar.

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

Turning a render into a quote-ready specification

A mockup answers what the bag should look like. A tech pack answers what it must be made of, and only the second question produces a quotation and a schedule. The conversion is unglamorous but it is where days are won or lost: every element left undefined in the pack becomes a decision taken later, on the line, by someone who has no authority to change your delivery date. Panels, denier, coating, stitch density, hardware finish, webbing width, zip reference, branding coordinates and carton specification all need to be written down before a sampling slot can be booked.

The specification also fixes the cost drivers that a quotation is built from, and therefore the volume pricing you can plan reward tiers against. A programme coordinator will read a pack and return a unit cost, a sampling estimate and a production window; they cannot return any of the three from a mood board. If you have not written a pack before, the crowdfunding bag sample prototyping page sets out the document section by section.

• State external and internal dimensions in centimetres, with tolerances, not as a capacity claim alone.
• Name every fabric by denier, weave and coating, and give a reference swatch or supplier code where one exists.
• Pin branding placement to a measured coordinate from a stated seam, not to a photograph.
• Specify stitch type and density for load-bearing seams; this is where warranty claims originate.
• Define the packing unit: pieces per carton, carton dimensions, and whether retail packaging is inserted.
• Write the inspection standard into the pack so it can be quoted, not negotiated later.

Days -34 to -24: the sampling block, day by day

Sampling is not a waiting period, it is a sequence of gates, and knowing which day each gate falls on is what makes the calendar predictable. Below, day 0 is the day bulk production starts, so sampling sits in negative days.

The pattern worth noticing is that four of the six rows are waiting on the creator, not on production. Campaigns that lose days inside the sampling window almost always lose them in review, not in sewing — which is why a consolidated change list beats three rounds of incremental comments.

Days -34 to -18: what pushes the sampling block wider

Three things widen the block from six to ten working days to twelve to fifteen, and all three are visible in the brief before a needle moves. Recognising them on day -34 is free; recognising them on day -20 costs the campaign its published date.

• Bonded or welded construction. Every bonded seam needs its own tooling and its own test, which adds days and cannot be compressed by working longer.
• Custom hardware. A moulded pull, a bespoke buckle or a coated zip has a component lead time that sits outside the sewing schedule entirely.
• Multi-material panels. Each additional fabric is another material approval and another cutting marker before assembly can start.

If the brief contains none of those, plan six to ten working days. If it contains two of them, plan twelve to fifteen and put the difference into the published date now rather than into an update later.

Day 0: the gate that starts everything

Nothing in the bulk schedule begins until the pre-production sample is approved in writing and the specification is frozen. That approval is day 0, and every date in this article is counted from it.

Four gates, all of them administrative, and all of them in the creator’s hands. That is the argument for finishing the paperwork before the campaign closes rather than during the week after.

Days 1 to 45: the bulk window, week by week

Thirty-five to fifty days is a range, not a promise, and the width of the range is decided by how much of the run is standard. Here is what each week inside the window actually contains.

The useful reading of that table is that delays are cheap in the middle and expensive at either end. Protect week 1 and the end of week 6; the middle weeks can absorb more than creators expect.

Days 46 to 50: inspection and the release decision

Inspection happens after packing, which is why it is the last point at which anything can still be changed. The standard is AQL 2.5 under ISO 2859-1: a sample drawn to the lot size, defects classified as critical, major or minor, and accept or reject thresholds that follow the standard rather than anybody’s opinion.

1. The inspector draws the sample and classifies what is found.
2. A pass releases the shipment and the seventy per cent balance falls due.
3. A marginal result goes to rework and re-inspection, which costs three to seven days and is the single most common cause of a missed vessel.
4. A fail goes back to the line, and the schedule is renegotiated from day 0 arithmetic rather than patched.

Ask for the report template at quotation stage. A creator reading an AQL report for the first time while a vessel waits is making the expensive decision at the worst possible moment.

Days 51 onward: the leg nobody in the building controls

FOB Xiamen means the goods are yours from the point they are loaded, and the leg that follows is not a production problem. It is also the part of the calendar most campaigns model worst, because they use a transit figure copied from a freight index rather than one quoted for their lane and their season.

• Sea is the default for a 500-pcs run and the slowest to correct.
• Air buys five to ten days door to door and is priced on chargeable weight, which punishes bulky goods.
• Rail, where the lane exists, sits between the two.
• Clearance, duty and the inland leg come after the vessel or flight and are the part creators forget to add.

Add the destination-side days to the production days before you publish anything. The published date is the sum, not the production figure.

Where the money falls on the same calendar

Payment terms are a schedule, not just a price. Thirty per cent on order releases fabric, trim and print screens; seventy per cent falls due against the inspection report and packing record, before the goods are handed to the carrier.

The cash-flow consequence is that the largest single payment falls due roughly when production finishes, not when it starts. A campaign that spent its pledge money on pre-launch marketing without holding the balance back discovers this at the worst possible moment.

A 120-day reference calendar from artwork to delivery

Put the pieces together and one full run — brief to backer — looks like this. Treat it as a reference shape, then substitute your own mode and destination for the last two rows.

The last row is not padding. Every campaign that publishes a date without a buffer ends up spending it anyway, in the form of an update.

Compressing the schedule without breaking the build

There are exactly four levers that shorten this calendar, and only two of them are free. Everything else is a trade that shows up later as quality, cost or risk.

Building the calendar backwards from the month you published

The only reliable way to set a delivery date is to start from the date and work backwards, because the forward version of the plan always assumes everything goes right. Take the published month, subtract the legs in reverse order, and whatever is left is the last day the brief can be finalised.

Read the bottom row as the real deadline: the brief has to be final roughly three to four months before backers receive anything, and every day of slippage inside the campaign eats into that, not into the end date. That is why the specification is a pre-launch deliverable rather than a post-campaign one.

Where campaigns actually lose the week they did not budget for

Every delayed campaign has a story about a single dramatic event. In practice the week is lost in five unglamorous places, none of which appear in a production schedule because none of them are production events.

1. The brief that was never finalised. A specification that is 90 per cent agreed still generates questions, and each question costs a day of sampling.
2. Artwork approved in pieces. Print screens cannot be cut until the file is final, so a logo approved after the sample is a sample that waits.
3. The colourway added at stretch-goal stage. A second colourway is a second fabric buy, a second print set-up and a second trim order, and none of them were in the original calendar.
4. The courier leg on the sample. Three to five days each way, plus customs handling, and it is routinely omitted from the plan.
5. The deposit that cleared late. Fabric is released on the deposit, not on the approval, so an unpaid invoice is a stopped calendar.

Four of those five are administrative and free to fix. That is the consistent finding across campaign calendars: the time is not lost in making the bag, it is lost in deciding what the bag is.

Two calendars compared: a standard build and a complex one

The same factory, the same team and the same destination produce two very different calendars depending on how much of the build is standard. This is the comparison to run before publishing a date.

The difference is roughly three to four weeks, and it is visible in the brief on day one. Decide which column you are in before the campaign page goes live, because the published date cannot be changed cheaply afterwards.

What to publish, and what to keep unpublished

The delivery date on a campaign page is a promise with a legal and reputational edge, and the way to keep it is to publish the month rather than the day and to hold a buffer you never mention.

• Publish the month. "Ships in November" survives a six-day slip; "ships 14 November" does not.
• Hold 10-15 days of buffer inside your own plan and never put it on the page.
• Say what you are waiting on. Backers tolerate a named dependency far better than silence.
• Update early, not late. The update that lands two weeks before the date is read as competence; the one that lands on the date is read as failure.
• Do not promise a date you have not modelled backwards. The bottom row of the backwards table is the earliest honest date, not the earliest hopeful one.

Where campaigns actually lose the week they did not budget for

Every delayed campaign has a story about a single dramatic event. In practice the week is lost in five unglamorous places, none of which appear in a production schedule because none of them are production events.

1. The brief that was never finalised. A specification that is 90 per cent agreed still generates questions, and each question costs a day of sampling.
2. Artwork approved in pieces. Print screens cannot be cut until the file is final, so a logo approved after the sample is a sample that waits.
3. The colourway added at stretch-goal stage. A second colourway is a second fabric buy, a second print set-up and a second trim order, and none of them were in the original calendar.
4. The courier leg on the sample. Three to five days each way, plus customs handling, and it is routinely omitted from the plan.
5. The deposit that cleared late. Fabric is released on the deposit, not on the approval, so an unpaid invoice is a stopped calendar.

Four of those five are administrative and free to fix. That is the consistent finding across campaign calendars: the time is not lost in making the bag, it is lost in deciding what the bag is.

Two calendars compared: a standard build and a complex one

The same production team and the same destination produce two very different calendars depending on how much of the build is standard. This is the comparison to run before publishing a date.

The difference is roughly three to four weeks, and it is visible in the brief on day one. Decide which column you are in before the campaign page goes live, because the published date cannot be changed cheaply afterwards.

What to publish, and what to keep unpublished

The delivery date on a campaign page is a promise with a reputational and, in several markets, a legal edge. The way to keep it is to publish the month rather than the day, and to hold a buffer you never mention.

• Publish the month. A month survives a six-day slip; an exact date does not.
• Hold 10-15 days of buffer inside your own plan and never put it on the page.
• Say what you are waiting on. Backers tolerate a named dependency far better than silence.
• Update early, not late. The update that lands two weeks before the date is read as competence; the one that lands on the date is read as failure.
• Do not promise a date you have not modelled backwards. The bottom row of the backwards table is the earliest honest date, not the earliest hopeful one.

Where campaigns actually lose the week they did not budget for

Every delayed campaign has a story about a single dramatic event. In practice the week is lost in five unglamorous places, none of which appear in a production schedule because none of them are production events.

1. The brief that was never finalised. A specification that is 90 per cent agreed still generates questions, and each question costs a day of sampling.
2. Artwork approved in pieces. Print screens cannot be cut until the file is final, so a logo approved after the sample is a sample that waits.
3. The colourway added at stretch-goal stage. A second colourway is a second fabric buy, a second print set-up and a second trim order, and none of them were in the original calendar.
4. The courier leg on the sample. Three to five days each way, plus customs handling, and it is routinely omitted from the plan.
5. The deposit that cleared late. Fabric is released on the deposit, not on the approval, so an unpaid invoice is a stopped calendar.

Four of those five are administrative and free to fix. That is the consistent finding across campaign calendars: the time is not lost in making the bag, it is lost in deciding what the bag is.

Two calendars compared: a standard build and a complex one

The same production team and the same destination produce two very different calendars depending on how much of the build is standard. This is the comparison to run before publishing a date.

The difference is roughly three to four weeks, and it is visible in the brief on day one. Decide which column you are in before the campaign page goes live, because the published date cannot be changed cheaply afterwards.

What to publish, and what to keep unpublished

The delivery date on a campaign page is a promise with a reputational and, in several markets, a legal edge. The way to keep it is to publish the month rather than the day, and to hold a buffer you never mention.

• Publish the month. A month survives a six-day slip; an exact date does not.
• Hold 10-15 days of buffer inside your own plan and never put it on the page.
• Say what you are waiting on. Backers tolerate a named dependency far better than silence.
• Update early, not late. The update that lands two weeks before the date is read as competence; the one that lands on the date is read as failure.
• Do not promise a date you have not modelled backwards. The bottom row of the backwards table is the earliest honest date, not the earliest hopeful one.

The RFQ pack that starts the clock

The clock in this article starts on day -34, and what starts it is a complete request. Five pieces of information are enough for a cost band, and two more turn a cost band into a schedule.

• Bag type and the features you cannot drop — pockets, size, closures, laptop sleeve, ventilation.
• Quantity per colourway, not just a total, because the 500-pcs minimum applies per style and per colourway.
• Material direction — canvas, nylon, recycled PET, coated polyester, vegan leather.
• Logo method — screen print, heat transfer, embroidery, woven label, metal hardware.
• Dates — campaign close, and the delivery month you intend to publish.
• Destination and fulfilment model, so the freight and clearance days are real rather than assumed.
• Reference images, ideally three: the shape you want, the detail you like, and the colour you are aiming at.

Send those to service@junyuanbags.com or message WhatsApp +86 177 5002 0688 and the reply carries a three-tier unit cost band, the fixed lines identified separately, and the sampling window expressed as dates rather than as a range.

Frequently Asked Questions

People Also Ask