Kickstarter Returns and Replacements: A Practical Policy for Bags

Why a bag campaign needs a written returns policy before launch

Most creators write their returns policy after the first complaint arrives, which is the worst possible moment because the answer is then negotiated under pressure with an unhappy backer and sets a precedent for the next 400. A written policy agreed before launch does three things: it tells backers what to expect, it tells your support team what to do without escalating, and it tells you how much money to hold back from the campaign funds.

Bags generate a specific claims profile that differs from electronics or apparel. A bag has no firmware, so there is no software defect class. It does have stitching, hardware, zippers, coatings and dimensional tolerances, and every one of those produces a claim that is genuinely arguable. Is a zip that catches occasionally a defect or a characteristic? Is a 3 mm panel misalignment a fault or normal tolerance? Without a written threshold your team decides each case from scratch, and inconsistent decisions are more damaging than strict ones.

There is also a cash argument. Campaign money feels like revenue but a meaningful slice of it is a liability until the fulfilment window closes. Holding a returns reserve of 4 to 7 percent of reward revenue is normal for a first bag campaign. Creators who spend 100 percent of funds on production discover that they cannot fund either a replacement run or a refund without personal money.

Finally, a written policy is what protects the team. Fulfilment on a 1,000-backer campaign is usually run by two or three people who are also doing everything else, and they will be asked to make judgement calls while tired. A one page document with thresholds removes the emotional load from those decisions and keeps the experience consistent across hundreds of conversations.

Three categories: defect, transit damage and remorse

Every claim falls into one of three buckets, and the policy must treat them differently. A manufacturing defect is a fault present when the bag left the line: a skipped stitch, a misaligned strap, a zip that separates, a coating that delaminates. A transit damage claim is a bag that was fine at dispatch and arrived crushed, stained or torn. Remorse is a backer who received exactly what was promised and no longer wants it.

The instinct of most first-time creators is to treat all three the same, usually by being generous. Generosity is expensive and, worse, it is unpredictable. A clean policy says that defects and transit damage are replaced at your cost, and remorse is handled at the backer's cost or not at all. That is not harsh; it is what lets you fund the replacements you genuinely owe.

Crowdfunding sits in an unusual legal position here. A backer is not a retail consumer buying from stock, and many jurisdictions treat a pledge as a pre-order rather than a distance sale, which changes whether a statutory cooling-off period applies. That said, the practical answer is the same: publish a policy that is at least as fair as the retail norm in your largest market, because arguing jurisdiction with an upset backer costs more than the replacement.

The categories also determine who you chase for money afterwards. A defect claim is a conversation with your production partner about process. A transit damage claim with an intact carton is a conversation with your carrier, and a pattern of them is a conversation with whoever specified the packaging. A remorse claim is a cost of doing business and nobody owes you anything. Sorting claims on day one is what makes those recoveries possible.

What a defensible replacement window looks like

The two numbers to publish are the claim window and the resolution window. The claim window is how long a backer has to report a problem after delivery. Thirty days is the common retail norm and is a reasonable default for bags, because latent defects in stitching and hardware almost always appear inside a month of daily use. Extending to 60 days is generous and cheap if your reserve supports it.

The resolution window is how long you have to fix it once the claim is accepted, and it is the number creators forget to publish. It matters more, because an unanswered promise is what generates public complaints. Set a realistic target: 48 hours to acknowledge, 10 working days to resolve when the replacement is in stock regionally, and 30 days when it must come from origin.

Be explicit about the seasonal exception. A backer who pledges in March, receives in September and reports a fault in December is outside any sane window, and the policy should say so. Equally, a backer who never received the parcel because the address was wrong needs a different path, usually re-shipment at their cost once the original parcel is returned or declared lost by the carrier.

One nuance matters for international shipments: the clock should start on confirmed delivery, not on dispatch. A parcel that takes 30 days to arrive in a distant market would otherwise consume the entire claim window in transit, which is both unfair and a guaranteed source of disputes. If your tracking cannot confirm delivery, start the clock on the carrier's delivery scan or on a stated default period after dispatch.

Evidence: what to ask for, and what not to ask for

Ask for three things and nothing more: the order or pledge number, two photographs (one showing the whole bag, one close-up of the fault), and a one line description. That is enough to classify 90 percent of claims. Asking for more creates friction that reads as defensiveness and pushes backers toward public complaint channels.

Do not ask for a video, do not ask the backer to return the item before you assess it, and do not ask for proof of purchase beyond the pledge number. The first two are the most common sources of escalation we see. If a claim is ambiguous, request one additional photograph of a specific detail rather than a new category of evidence.

Classify claims within 24 hours of arrival. Speed of classification matters more than speed of resolution, because an accepted claim with a three week wait produces far less anger than an unclassified claim with no response. A simple shared inbox with three labels and one owner is enough for campaigns under 2,000 backers, and it prevents the common failure of two people independently promising different remedies to the same backer.

There is one exception worth building in: for transit damage claims, ask whether the outer carton was damaged and request a photograph of it if so. That single question determines whether your claim is against the carrier or against your own packing specification, and it takes the backer about 20 seconds. If outer carton damage shows up repeatedly in one destination, the real fix is upstream in the packaging specification rather than in the returns process.

Who pays freight, in each of the four scenarios

Freight allocation is where returns budgets leak, because return shipping on a bulky item can exceed the item cost. A backpack returned internationally at retail rates costs 18 to 45 USD. The bag itself may cost 14 USD to make. Paying both ways on every claim will consume a 5 percent reserve in about 60 claims per 1,000 backers.

One scenario deserves its own note: the wrong item shipped row. Even at a 0.3 percent rate this is the claim class that generates the most public damage, because the backer feels cheated rather than unlucky. Always pay both legs, always send the correct item before waiting for the wrong one to come back, and always add a handwritten note or a small extra item. The incremental cost is trivial against the reputational value.

The pattern in that table is deliberate. Never ask a backer to return a defective bag internationally. The return cost exceeds the salvage value in almost every case. Ask instead for the bag to be donated locally with a photograph, or for a specific component to be cut off and discarded so the item cannot be resold as new. This is cheaper, faster and better for sentiment.

The replacement inventory problem nobody budgets for

Here is the structural problem specific to made-to-order goods. You produced 1,000 bags against 1,000 pledges plus a small buffer. Six months later you have 40 valid defect claims and no inventory. Ordering 40 replacement bags is not possible under a 500 pcs per style and colourway minimum, and re-running the line for 40 units would cost more than the original run.

The only workable answer is to build the replacement pool into the original order. On a 1,000-unit campaign, ordering 1,040 rather than 1,000 costs the marginal unit price on 40 units, typically 12 to 26 USD each, and creates a pool that can answer claims in 48 hours for years. Ordering nothing and hoping for a 2 percent defect rate means every claim becomes a refund.

The second-best answer, if the campaign has already closed without a pool, is to over-order on the next run and answer late claims from it. Our production team regularly sees creators place a re-order at 500 pcs purely to clear a backlog of 60 claims, and while that ties up cash, it converts an unresolvable liability into sellable inventory. Stretch-goal and re-order planning therefore belongs with the MOQ decision, not after it.

That pool should be held as loose shells plus the common add-ons, not pre-kitted parcels, and it should live in the largest destination market rather than at origin if you can arrange it. A regional pool turns a 30 day resolution into a 3 day one, and the difference in backer sentiment is worth far more than the small carrying cost.

Costing a returns reserve per 100 backers

A reserve is a forecast, not a guess, and it can be built from three rates multiplied together. Take the expected defect claim rate, the expected transit damage rate, and the average cost to resolve each. For bags shipped internationally on a first campaign, defect claims typically land between 1.5 and 4 percent and transit damage between 0.8 and 2.5 percent, depending heavily on packaging quality and destination mix.

Expressed as a percentage of reward revenue that lands around 4 to 7 percent for a typical bag campaign, and higher for structured or oversized items that damage more easily in transit. The spread is wide because packaging quality moves the transit damage number by a factor of three. Spending 0.60 USD more per unit on carton grade and void fill routinely removes more cost than it adds. That trade-off is set out in the rewards fulfilment plan, which treats packaging, freight and returns as one system rather than three separate costs.

Quality control upstream is the other lever. Every defect claim you prevent is worth roughly 20 to 40 USD in avoided resolution cost, which is why inspecting to AQL 2.5 to ISO 2859-1 before dispatch is the cheapest insurance in the whole programme. If you are unsure what that inspection actually covers, read the pre-shipment check list before you finalise the reserve.

Writing the policy onto the campaign page

The policy belongs on the campaign page, in the FAQ section, in plain language, before launch. Four sentences are enough: what counts as a defect, how long backers have to report it, what you will do, and how to contact you. Anything longer will not be read, and anything vaguer will be interpreted in the backer's favour.

Avoid two phrases that cause trouble. "Satisfaction guaranteed" reads as an unlimited remorse policy and will be quoted back at you. "No returns on crowdfunding rewards" reads as abandonment and generates comments that outrank your own page in search. Say instead that defects and transit damage are replaced at no cost, and that change of mind is handled case by case.

One more element belongs on the page: the address accuracy clause. State that backers are responsible for supplying a correct and complete address, that changes are accepted until a named cut-off date, and that re-shipment after a failed delivery is at the backer's cost. This is the largest preventable cost in crowdfunding fulfilment after defects, and one sentence on the campaign page plus three reminder emails removes most of it.

Repeat the policy at three further touchpoints: in the survey, in the dispatch notification, and in the parcel itself on a small card. Repetition is not redundant here, because the backer who reads the card in the box is the one who will report a real defect rather than silently leaving a one star comment.

Keep the language identical wherever the policy appears. If the campaign page says 30 days and the parcel card says 60, the backer will reasonably assume the longer figure applies and you will have conceded it by inconsistency. Store the approved wording in one file and paste it rather than rewriting it at each touchpoint, because paraphrasing is exactly how the two versions drift apart.

Handling the backer who never answers the survey

Between 3 and 11 percent of backers never complete the reward survey, and they are a distinct operational class rather than a returns problem. The correct sequence is three reminder emails at increasing intervals, then a final notice stating a default configuration, then dispatch of that default. Do not hold the shipment for them.

The default should be the most common configuration, not the cheapest. Shipping the early-bird bag to somebody who pledged at deluxe tier generates a legitimate complaint that you will lose. Shipping the deluxe configuration to somebody who pledged at standard is a small unrecovered cost and no complaint at all.

Set the final notice date clearly and keep the proof. When a backer resurfaces four months later asking where their reward is, the answer is a shipment photograph and the date of the third reminder. This is the single most common dispute in crowdfunding support queues and it is almost entirely preventable with a documented sequence.

Hold back roughly 2 percent of the run for this group when you set the order quantity. Non-responders skew toward the higher tiers more often than creators expect, so sizing the default at the median configuration rather than the mode tends to produce fewer complaints. Any unclaimed default stock becomes the start of your warranty pool rather than wasted inventory.

There is a second group worth separating from non-responders: backers who respond with an impossible combination, such as a colourway that was never offered on their tier. Treat these as survey errors rather than as choices. One clarifying email with two offered options resolves nearly all of them, and it is faster than any default rule.

Refunds without wrecking the campaign cash position

Kickstarter processes pledges at campaign close and holds a platform fee plus payment processing, so the money a creator receives is already net of roughly 8 to 12 percent. A refund issued from that money is a full pledge returned out of reduced funds, and the platform fee is generally not recovered. Refunding is therefore more expensive than it looks.

Practical rules follow from that. Never issue refunds before fulfilment is complete, unless the campaign is being cancelled. Never refund a backer who has a valid defect claim when a replacement is available, because a replacement costs 18 to 34 USD and a refund costs the full pledge. And never promise refunds publicly as a general remedy, because the promise is read as a policy.

Track refund exposure as a live number rather than a surprise. Build a simple sheet with four columns: pledges received, platform and processing deduction, committed production spend, and open claims liability. Updating it weekly during fulfilment takes 15 minutes and tells you weeks in advance whether the reserve is sufficient, which is the difference between an orderly resolution and a cash crisis discovered in month nine.

If you must refund in volume, sequence it: replace what can be replaced, refund what cannot, and communicate the two paths separately. Backers accept a delay far better than they accept silence, and the campaigns that survive a quality problem are almost always the ones that published a dated plan within 72 hours of recognising it.

Set a policy on refund timing as well as refund eligibility. Issuing refunds in a single batch on a known date is easier to reconcile, easier to communicate and easier to fund than a trickle of individual requests handled ad hoc. It also lets you tell the remaining backers precisely what has been refunded and how many pledges are still being fulfilled.

Warranty claims after the fulfilment window closes

A bag sold as a reward often becomes a retail product later, and warranty claims then arrive outside the reward window. Decide the warranty before you sell the leftover stock: 12 months against manufacturing defects is the norm for bags in most markets, and it should exclude wear, abrasion, overloading and misuse.

The important distinction is between a defect and wear. A strap that pulls out of its bar-tack at month four is a defect. A strap whose webbing has frayed where it rubs a shoulder is wear. Publish that distinction with photographs if possible, because it is the most argued category in bag warranty claims and photographs settle it faster than prose.

Fund the warranty from the leftover inventory rather than from cash. If you ordered a 4 percent buffer and used 2 percent during fulfilment, the remaining 2 percent is your warranty stock, and it is already paid for. This is the strongest argument for building the buffer into the first run rather than ordering exact quantities.

Decide also who answers warranty claims after the campaign, and put a name and an email in the parcel card. A warranty that nobody staffs is worse than no warranty, because it converts a resolved purchase into an unresolved grievance. Most small brands find that a single monitored inbox with a 48 hour auto-reply satisfies the obligation at almost no cost.

Decide whether the warranty covers the original backer only or transfers with the product. For most small brands the practical answer is that it covers the product, because verifying who bought it secondhand costs more than the claim. State whichever rule you choose on the parcel card so that both the original backer and any future buyer know where they stand.

A returns policy template you can adapt

What follows is the structure we recommend to creators, with the numbers that suit a first bag campaign. Adjust the windows to your market and your reserve, but keep the categories and the freight allocation intact, because those are the parts that control cost.

Claim window

30 days from delivery, 60 for latent seam failure

Acknowledge

Within 48 hours, automated confirmation acceptable

Resolve defect claim

10 working days from regional stock, 30 from origin

Replacement pool

3 to 4 percent of run, held loose, regionally if possible

Inspection standard

AQL 2.5 to ISO 2859-1 before dispatch

Returns reserve

4 to 7 percent of reward revenue

Remorse

Case by case, backer pays return freight

Warranty on retail stock

12 months against manufacturing defects

Publish those eight numbers and your support burden drops sharply, because most backers are not trying to extract value. They are trying to find out whether anybody is still there. A policy that answers that question in one screen does more for campaign reputation than any amount of individual goodwill.

Review the template after your first 100 claims rather than treating it as fixed. Claim rates, resolution costs and refusal rates are all forecasts until you have real data, and the first hundred claims will tell you which of your assumptions was optimistic. Adjust the reserve first, then the windows, and only then the policy wording.

Frequently Asked Questions

People Also Ask