Board Game Kitting Fulfillment for Kickstarter: Pre-Kit in China, Kit at the U.S. Warehouse, or Pick Loose SKUs?
Choose where a board game campaign should become a real kit before a cheap-looking freight plan turns a fixable China-side problem into expensive U.S. warehouse work.
The cost usually moves one handoff later than the wrong decision.
- Factory Packout Decide what physically belongs together before cartons are treated as final.
- Freight Booking Quote and booking depend on carton count, cube, pallet structure, and timing.
- U.S. Receiving The dock only sees cartons, labels, intake files, and labor requirements.
- Backer Outcome Missed add-ons, replacements, and returns appear after the physical mismatch is already old.
Lock the kitting choice only when factory packout, freight assumptions, receiving files, and the backer promise are still describing the same shipment.
If one cheap consolidated freight quote is the main reason to lock early, the team is usually moving risk, not removing it. The loss appears later as U.S. warehouse labor, replacement handling, return work, or delayed label release.
The safer process is the one that keeps mistakes visible and fixable at the cheapest controllable point in the chain, usually before the goods leave China.
Only after that should the team decide whether a repeated stable unit belongs in a China pre-kit, whether the U.S. warehouse is truly prepared to build kits, or whether add-ons and spare parts still need to stay loose. A kit SKU belongs only to a real finished unit.
The Real Pressure: The Factory Wants A Packing Answer Before The Export Is Stable
The problem usually starts in a very ordinary week. Production is nearly done. The factory wants a final answer on sealed Deluxe kits versus loose components. The freight forwarder wants to know whether the carton count and cube are stable enough to keep the booking. The U.S. warehouse wants to know whether it will receive finished kit SKUs or component SKUs. Meanwhile, late backers are still adding sleeves, mats, coins, and extra minis in BackerKit or Gamefound.
Smaller publishers and crowdfunding teams often make the next choice for a simple reason: one consolidated shipment quote looks cheaper. So the team keeps pushing toward one easy packout answer, even if some component questions, spare-part planning, or return handling should still be solved before departure.
Nothing feels broken yet. The campaign still looks close to launch. Then one answer gets locked too early. The factory seals kits from yesterday's add-on mix. The freight plan still reflects the old carton shape. The receiving file still assumes one finished Deluxe SKU. Two or three weeks later the shipment reaches the dock, and the mismatch becomes relabeling, re-kitting, delayed label release, or missed items in the first outbound wave.
Core judgment: Do not choose kitting by convenience. Choose it by what must remain easy to identify, pick, count, replace, and test.
What looks like one small packing decision at that point usually keeps moving through the rest of the shipment. It changes handoffs first, then costs, then support work after delivery. Work that could have been handled near the factory at China-side cost now lands in U.S. labor instead.
What Has To Stay Consistent From Factory Packout To U.S. Receiving
Everything here belongs to one event chain: campaign close, production finish, freight booking, U.S. receiving, then delivery. Teams usually discover the kitting choice was wrong only after the physical shipment no longer matches the promise made upstream. The cost arrives one handoff later, then one invoice later, then one support queue later.
Kitting should be read inside that same chain. If the model changes after one handoff is already treated as final, the next handoff absorbs the mistake. Booking assumptions drift. Then the receiving file drifts. Then the warehouse labor plan drifts. By the time the backer opens the wrong box, the real mistake is already old.
Kickstarter, Gamefound, and BackerKit campaigns often finalize shipping and post-campaign order data later than the live campaign because order mix, add-ons, and landed-cost assumptions can still move. The kitting choice has to respect that same timing. The first quote rarely shows what late correction costs after arrival.
- Shenzhen factory packout
- China consolidation
- Yantian export booking
- Ocean shipment
- Los Angeles receiving warehouse
- ASN / WRO intake
- Bin setup or kit build
- Kickstarter outbound wave
A China pre-kit changes the factory packing list, carton labels, master-carton cube, and what the receiving warehouse expects to scan. A U.S. warehouse kit changes bin setup, labor scheduling, and the days between receiving and label release. A loose SKU model keeps components easier to count, but it adds more pick lines during the main wave. The hidden money question is where unresolved work gets paid for: near the factory before departure, or later inside a U.S. warehouse at U.S. labor rates.
How Kitting Changes Freight And Receiving
The break usually shows up in one of three places first: the freight booking no longer matches the carton file, the receiving warehouse expects a different intake pattern than the one arriving at the dock, or the warehouse has to bill for work the original plan assumed would never happen.
Freight was booked from the old carton shape
The project was quoted from loose-component cartons, then the factory changed to sealed kits. That can change carton count, pallet count, and cube after the routing was already treated as final.
The dock sees a different shipment than the file described
The warehouse planned to receive one sealed Deluxe SKU, but the container arrives with mixed components or factory names that do not match the intake file. Receiving slows immediately.
The labor moved, but the quote did not
A late kit change turns a simple receive-and-pick plan into pallet breakdown, relabeling, re-kitting, overflow storage, or manual matching before the first label is safe to release.
The same sequence also affects landed-cost review. If carton weight or kit structure changes after DDP, importer, or shipping-fee assumptions were built, the project is no longer working from one truthful shipment file. That is when teams discover the cheapest-looking kitting choice was only cheap before the extra paperwork, labor, and delay were counted.
This hits smaller teams especially hard. Not every publisher has a self-run U.S. warehouse, slack labor, or schedule control waiting at the other end. If the campaign sends unresolved spare-part, return, or rebuild work across the ocean, the correction no longer happens where the unit was packed. It happens where labor is far more expensive.
So the real decision is not simply which model looks efficient on paper. It is whether the shipment is stable enough for any model to be treated as final at all.
Do Not Lock Kitting Before The Shipment Plan Stabilizes
The real question is not whether the model works in theory. It is whether the next owner in the chain can already treat the shipment as real. If not, locking kitting early only pushes the correction into freight, receiving, or support later.
Pause The Kitting Decision If Two Or More Are True
- Pledge exports or late add-on quantities are still changing.
- Final carton counts, carton dimensions, gross weight, net weight, or CBM are not locked.
- The freight booking was quoted before the kit model changed.
- The receiving warehouse, ASN, WRO, pallet labels, or appointment assumptions are not final.
- DDP, importer, tariff, or shipping-fee assumptions depend on carton weight that may still change.
- Spare parts or replacement stock have not been separated from sellable stock and components the warehouse may use to build kits.
Once those moving pieces settle, the labels themselves become easier to use. The team can stop arguing in abstract terms and say what will actually be packed, received, or picked.
What Each Kitting Model Actually Means
These labels get confused because different teams use the same word for different moments in the project. The factory may call something a kit because it was packed together once. The warehouse may call something a kit because it ships as one unit. The pledge manager may only be describing order logic. Those are not the same thing.
- Pre-kit in China: the factory or China-side packout team builds a real physical kit before freight leaves.
- Build at the U.S. warehouse: the warehouse receives components, bins them, and creates the finished kit after intake.
- Loose SKU pick: each component stays separate and the warehouse picks the order line by line.
A kit SKU belongs only to a finished unit. A virtual bundle is still just a rule, and spare stock should stay outside normal sellable and kit-building bins.
Pre-Kit In China, Build At The U.S. Warehouse, Or Pick Loose SKUs?
Use the table when the team is about to make a real project decision: approve factory packout, keep the freight booking as quoted, send the final receiving file, or release labels. Each row should feel like a situation the campaign is already in, not a theory exercise.
On small screens, each row becomes a card so the model, files, and risks stay readable.
| Model | What Is Happening Right Now | Do Not Use It If | Files That Must Already Agree | Who Pays First | What Backers Feel Later |
|---|---|---|---|---|---|
| China pre-kit | Factory packout is at the final stage, the Deluxe shape stopped changing, and the U.S. warehouse should not have to rebuild that pledge after intake. | Late add-ons, promo eligibility, or spare-parts planning can still change what belongs in the box. | Factory packing list, kit BOM, carton file, carton labels, reserve block, and sample proof of the finished kit. | The freight team and receiving dock pay first if the shipment still arrives under the old carton or SKU assumptions. | Wrong sealed contents, slower missing-part diagnosis, and harder damage investigations after delivery. |
| U.S. warehouse kit | The cargo can cross the ocean as components, but the final backer mix becomes trustworthy only after receiving and binning. | The receiving date is unstable, component labels are weak, or the warehouse does not have labor space to build before the main wave. | Receiving file, SKU map, live BOM version, bin locations, build instructions, reserve block, and sample-order QA list. | The warehouse pays first through delayed receiving, extra handling, relabeling, or re-kitting work that was not in the original intake plan. | Slower label release, build mistakes, and a shipping wave that starts later than the team expected. |
| Loose SKU pick | Order shapes are still messy: duplicate add-ons, uneven all-in baskets, changing stretch eligibility, or spare stock the team may need later. | The project already collapsed into one repeated base or Deluxe shape and keeping everything loose only adds human picks. | Reward-to-SKU matrix, SKU map, pick rules, add-on quantity rules, bin setup, and a clean reserve-stock block. | The outbound team pays first because every extra component becomes another chance to miss a small item during picking. | Missed add-ons, longer release windows, and more support tickets about one missing small item. |
The difference is easier to see once the same campaign stays in view. With one board game on the table, the model change stops feeling theoretical.
Example: A Dungeon Board Game With Minis, Tiles, Mats, Coins, Sleeves, Promos, And Stretch Goals
Imagine a campaign with a Core Game, Miniatures Box, Dungeon Tiles Pack, Boss Expansion, Neoprene Mat, Metal Coins, Sleeves, Promo Card Pack, Stretch Goal Box, Late Add-on Extra Mini Set, and replacement reserve.
- Base pledge: ship the Core Game as one physical unit and skip the extra kit SKU.
- Deluxe pledge: China pre-kit only if Core + Minis + Tiles are stable, repeated, and safe to lock before freight leaves.
- All-in orders and duplicate add-ons: these usually push the campaign toward U.S. kitting or loose SKU picking because the order shapes vary more.
- Promos, stretch items, and spare parts: each one needs a physical home before label release, not a promise buried in campaign notes.
The reward-to-SKU companion page covers how pledge language becomes warehouse pick lines. The question here comes later: should those lines stay loose, become a U.S. kit, or become a China pre-kit before freight moves?
In practice, each model only looks right under a narrower set of conditions than teams first expect.
When To Pre-Kit In China
Pre-kit in China when the project has already passed the point where more flexibility would help. In real projects, that usually means pledge shapes are stable, late add-ons are no longer changing the Deluxe mix, the factory is already at final packout, and the U.S. warehouse should not have to reopen that pledge after intake.
That is why pre-kitting fits base or repeatable Deluxe structures better than messy all-in orders. The gain is real: fewer U.S. pick lines, less kit labor, and a cleaner outbound pattern. It also keeps repeated corrections closer to the factory, where they are usually cheaper. The loss is real too. Once the kit is sealed, the warehouse can no longer see the component state without opening inventory that was supposed to be ready to ship.
The failure sequence is predictable. The team approves China pre-kitting. Late add-ons reopen the order shape. Freight still moves under the old carton assumptions. The U.S. side inherits the cleanup. Heavy all-in cartons make that worse because damage claims, split deliveries, and missing-item investigations get harder when the internal component state was hidden before the shipment left China.
Pre-Kit Only If These Stay True
- The pledge shape is stable before factory packout.
- The kit BOM, factory packing list, and carton file use the same component names and quantities.
- The kit can survive China-to-U.S. transit without crushing, rubbing, or hiding damage.
- Replacement reserve is separated before kit building starts.
- The U.S. warehouse can receive, scan, and bin the kit as a real inventory unit.
Many campaigns never reach that level of stability before departure. When that happens, receiving components in the U.S. and building later is often the cleaner compromise.
When To Build Kits At The U.S. Warehouse
Build kits at the U.S. warehouse when the shipment can safely cross the ocean as components, but the final backer mix becomes trustworthy only after receiving. The common version is simple: the pledge manager closes late, add-ons are uneven, and the team would rather keep options open until the cargo is already in the warehouse.
That flexibility helps only if the warehouse can absorb it and the campaign is willing to pay U.S. rates for that flexibility. Not every creator or small publisher runs a self-operated U.S. warehouse. Many are relying on a partner warehouse that charges for each extra touch and works on a crowded calendar. By the time the goods land, the warehouse should already know where each component goes, which BOM version is live, which stock is blocked for replacements, and which sample orders have to pass before the main wave starts. If those basics are missing, U.S. kitting does not feel flexible. It feels like a receiving delay that keeps generating extra labor.
U.S. Kitting Fails When The BOM Is Too Casual
A useful BOM does not say `build Deluxe kits`. It says which component SKUs, how many of each, which carton source they came from, which bin supplies them, which spare stock is off-limits, which finished kit SKU is created, and which sample orders must be test-built before the main wave starts.
And if even that still asks too much of the warehouse, the cleaner answer is usually to leave the components loose and keep the complexity visible.
When To Pick Loose SKUs Instead
Loose SKU picking is usually the least elegant model and the most honest one. It fits when the campaign still has too many order shapes to pretend they are one stable kit: duplicate add-ons, uneven all-in baskets, region-specific promos, or spare inventory the team may need later.
The reason teams keep items loose is not theoretical. The project is still changing in ways a sealed kit would hide. One backer bought a second Miniatures Box. Another removed sleeves but kept the Boss Expansion. Another needs a replacement promo pack later. Loose picking keeps those events visible instead of forcing the warehouse to reverse-engineer them from a prebuilt kit.
The tradeoff is that the main shipping wave becomes more execution-heavy. Loose SKU picking only works when pick rules, bin labels, duplicate-quantity handling, and test orders are strong enough to survive repeated human picking without missed add-ons.
Either way, the next failure point is usually receiving. The warehouse still has to see the same shipment the team believes it is sending.
What The Receiving Warehouse Must Actually Receive
The receiving warehouse does not experience the campaign as strategy. It experiences a truck appointment, pallets on the floor, labels on cartons, and an intake file that either matches or does not.
On arrival morning the dock team wants four answers quickly: what is supposed to be on the truck, whether the cartons scan into the inbound file, whether sealed kits and loose components are clearly separated, and whether anything damaged or missing changes the first outbound wave. Multi-carton all-in orders make that worse because one missing or crushed carton can turn into a partial-delivery investigation before putaway even starts.
- Final carton counts: the receiving file should match the cartons and pallets arriving from the container or LTL delivery.
- Pallet structure: sealed kits, loose SKUs, and mixed cartons should not be hidden on the same pallet without clear labels.
- ASN / WRO alignment: the inbound file should match whether the warehouse is receiving finished kit SKUs or component SKUs.
- Relabeling plan: if China cartons use factory names and the warehouse uses SKU names, the translation must be ready before unloading.
- Appointment risk: if the receiving warehouse discovers a different kit structure at the dock, putaway and outbound label release can slip.
This is why the kitting decision should be reviewed before freight leaves China when possible. By the time the shipment reaches the receiving dock, the remaining questions are no longer planning questions. They are labor, space, calendar, and exception-handling questions. For teams using a partner warehouse, they are also billable questions at U.S. labor rates.
That pressure also explains why teams create fake kit SKUs too early. Once the dock is under time pressure, a name can start standing in for a kit that never physically existed.
Only Create A Kit SKU For A Real Finished Kit
The usual failure is easy to recognize after the fact. The spreadsheet says `KIT-DELUXE-001`, but the warehouse still has to walk the aisles and pick Core Game, Miniatures Box, and Dungeon Tiles Pack separately. At that point the project does not have a real kit. It has a name that makes later counting, receiving, and replacement work harder.
- The finished kit must already exist somewhere real: the warehouse should know how many finished kits exist, where they are stored, and what component inventory was consumed to create them.
- The BOM must stop the wrong stock from disappearing: list component SKUs, quantities, carton source, bin location, finished kit SKU, sample check, and which spare components are off-limits for kit building.
Small extras are usually where that false certainty breaks first, because promos, stretch items, and replacement parts are the easiest things to promise and the easiest things to hide.
Stretch Goals, Promos, And Spare Parts Need Physical Rules
These items rarely break the project during the campaign. They break it later, when the first outbound wave starts and someone realizes the promo was promised in campaign copy, the stretch box was unlocked late, or the spare part was quietly consumed during kit building. Small items become expensive because they are easy to promise and easy to lose track of.
- Inside the Core Box: no separate pick line, but the packing proof should confirm the item is already inside the sealed game.
- Inserted at factory: confirm the factory packing proof and whether the inserted item changes weight or damage risk.
- China pre-kit: assign it to a real kit BOM and sample-check the finished kit before freight.
- U.S. kitted: receive it as a SKU, bin it, then consume it into the finished kit only after reserve is separated.
- Separate pickable SKU: use this when eligibility is pledge-specific, region-specific, or late-unlocked.
- Spare parts: keep replacement stock outside normal sellable and kit-building bins until the team knows what replacement work may need later.
The important moment is not theoretical. It is the hour before late pledges are released, the day before leftover stock goes on sale, or the week after delivery when the first missing-part tickets arrive. Separate spare inventory before any of those moments. Otherwise the campaign can accidentally sell the exact Miniatures Box, promo pack, or replacement component that support needs next.
If tickets already started, use the replacement parts and returns guide to decide whether the next move is part resend, full-game replacement, warehouse review, or hold until the team knows where the spare inventory actually is.
After that, only one question really matters: can real orders survive the model the team just approved?
Test-Kit Before Label Release
The project usually feels ready before it is actually ready. The real proof appears when the warehouse tries to pack the awkward orders first: a duplicate add-on, a promo-eligible pledge, a stretch-goal edge case, or a replacement request that pulls from spare stock. If those fail, the main wave is not ready.
- Base pledge: Core Game only.
- Deluxe pledge: Core Game + Miniatures Box + Dungeon Tiles Pack.
- All-in pledge: Deluxe plus Boss Expansion, Mat, Coins, Sleeves, Promo, and Stretch Goal Box.
- Deluxe plus duplicate paid add-on: confirm the extra Miniatures Box is added without double-building the whole kit.
- Promo-eligible order: confirm whether promo is inserted, kitted, or picked as `SKU-PROMO-001`.
- Stretch-goal order: confirm `SKU-STRETCH-001` or the no-pick note matches eligibility.
- Replacement component order: confirm spare stock is used, not sellable stock or components reserved for kit building.
- Late order change: confirm the order can move between kit model and loose SKU pick without hiding components.
For every test, record the export order ID, kit BOM version, component SKUs, carton source, bin source, finished kit SKU if any, packed weight, photo proof, and the item name the team will use when a backer reports something missing. Those notes matter later when the warehouse insists the order was packed correctly and support has to decide whether the problem is real, repeated, or coming from one weak rule.
If the internal team still cannot answer those awkward cases confidently, outside review usually starts saving time instead of adding one more layer of opinion.
Where WinsBS Fits, And Where It Does Not
WinsBS usually becomes relevant at a specific moment: the team can already feel the shipment getting harder to reverse, but it is not too late yet. Production is close enough that final packout matters. Freight is close enough that carton assumptions matter. Receiving is close enough that the warehouse is asking for the intake file. That is the window where correcting the model is still cheaper than letting the next handoff absorb it.
That timing matters even more for smaller teams that do not control their own U.S. warehouse operation. Once the problem crosses the ocean, every extra touch can turn into paid receiving labor, relabeling, re-kitting, spare-part handling, or return work.
Pledge manager: tells the team what backers bought and what changed late. It does not decide what the factory should seal or what the warehouse should receive.
Freight forwarder: can move the load from carton count, cube, pallet count, and route assumptions. It usually does not stop the project because a promo pack, kit BOM, or spare-stock rule drifted.
Domestic 3PL: can receive, bin, kit, pick, and pack once the inventory and rules are already clean. It should not have to discover what the campaign meant after the freight already arrived.
WinsBS: fits when the team still has time to reconcile those layers before the next handoff turns the mismatch into receiving labor, relabeling, re-kitting, or backer-facing exceptions.
WinsBS is lower fit once that window has already closed: inventory is imported, received cleanly, binned, kit-built, test-picked, and the only remaining need is stable domestic labor against a settled BOM. At that point the project is no longer choosing a model. It is just executing one.
Sometimes the kitting question turns out to be hiding an earlier problem in the chain: unstable files, unclear reward translation, weak origin prep, or shipping charges built from the wrong assumptions. Those cases usually need one of the adjacent pages next.
Related Reading
The team is still arguing about where this work really starts
Backer rewards still have not become warehouse picks
Use the reward-to-SKU page when pledge language still has not turned into reliable pick lines.
Freight has not left China and the file set still feels unstable
Run the pre-departure checklist for cartons, labels, receiving files, and import assumptions.
The warehouse is being blamed, but the mistake may be older
Check whether weak China-origin prep created the delay before the shipment ever reached the dock.
Backers are about to be charged from weights that may still move
Review shipping-fee timing before charging from carton or kit assumptions that are still changing.
Source And Review Note
Public Workflow References
Stonemaier's shipping and fulfillment hub and the creator-to-factory-to-fulfillment-center chain shown in Stonemaier's fulfillment infographic support the campaign-level sequence used here: creator decisions happen first, factory and freight handoffs happen next, and fulfillment-center consequences show up later.
What Those Sources Support
BackerKit shipping options and Kickstarter's pledge-manager guidance matter later in that chain: order mix, item weight, add-ons, and shipping timing can still move after the live campaign, so physical kitting should not be treated as stable earlier than those inputs really are.
WinsBS Operational Interpretation
WinsBS uses that public workflow as a narrower execution check: when should the campaign stop treating these items as separate components, and how late in the project would that choice become expensive to reverse?
FAQ
What is kitting fulfillment for Kickstarter board games?
Kitting fulfillment is the moment a campaign stops talking in pledge language and starts deciding which physical items will cross the ocean together, reach the warehouse together, and ship to the backer together. For board games, that can mean a core box, minis, tiles, promos, stretch items, sleeves, or add-ons becoming one real unit.
Should I pre-kit board game pledges in China?
Pre-kit in China when the factory is already at final packout, the pledge shape has stopped changing, and the U.S. warehouse should not have to reopen that set after intake. Do not pre-kit in China when late add-ons, promo eligibility, or spare-part needs can still change what belongs in the box.
When should a U.S. warehouse build board game kits?
A U.S. warehouse should build kits when the shipment can cross as components, but the final backer mix only becomes trustworthy after receiving. That works only when the warehouse already has a clear BOM, labeled components, bin locations, build instructions, reserve blocks, and sample-order QA before the main wave begins.
When should add-ons stay as loose SKUs?
Add-ons should stay as loose SKUs when the order shapes are still messy in real life: duplicate add-ons, uneven all-in baskets, region-specific promos, or spare inventory the team may need later. Keeping them loose is often the safer choice when a sealed kit would hide changes the team still needs to see.
How do kitting decisions affect freight and U.S. warehouse receiving?
Kitting changes the shipment before the warehouse ever starts picking. It can change carton count, cube, pallet structure, intake files, receiving appointments, and labor billing. The mistake usually appears when the warehouse expects one shipment and the truck delivers another. That is also when a cheap unified-shipment quote stops looking cheap, because the correction has already moved into U.S. labor.
Is a virtual bundle the same as a kit SKU?
No. A virtual bundle only tells the warehouse what to pick. A kit SKU should exist only after a real finished unit has already been built, counted, stored, tested, and made available as one ship-ready inventory unit.
How should stretch goals and spare parts be handled?
Stretch items and spare parts need a physical home before label release, not a note buried in campaign copy. They can live inside the core box, enter a China kit, enter a U.S. warehouse kit, or stay as separate SKUs, but replacement stock should stay outside normal sellable and kit-building bins.
Is this the same as hiring a board game 3PL?
No. A board game 3PL may receive, store, kit, pick, and pack clean inventory. The problem here starts earlier: whether the factory packout, freight plan, U.S. warehouse receiving file, kit BOM, and backer order logic still support the same kitting choice.
Can WinsBS review my kitting files before fulfillment?
Yes. WinsBS can review the file set before the wrong model gets locked in: pledge export, reward-to-SKU matrix, kit BOM, SKU map, add-on list, stretch goal list, factory packing list, carton file, receiving scan, bin setup, kit build instructions, pick rules, reserve count, and sample orders.
Methodology
Keyword basis: local 2026-04 and 2026-05-08 keyword research archives covering kitting fulfillment, warehouse kitting, pick-and-pack fulfillment, Kickstarter fulfillment, crowdfunding fulfillment, board game kitting fulfillment, add-on fulfillment, and stretch goal fulfillment.
Source basis: repository source-library notes, public tabletop workflow references, and local sibling pages for reward-to-SKU readiness, pre-departure file checks, warehouse-speed limits, shipping-fee timing, and replacement reserve handling.
Operational judgment: the article follows the same order in which these projects usually become expensive: order logic still moves, factory packout wants a final answer, freight gets booked from one carton shape, the warehouse prepares for another, and support inherits the break after delivery. The operational review layer is based on file-level checks WinsBS uses before China-origin board game freight is treated as ready for U.S. warehouse receiving. No invented rates, error percentages, transit times, or customer metrics are used.
Send Your Kitting Files For Review
Send the files when the project is about to lock the wrong thing into place: the factory is close to final packout, freight is being treated as booked, the receiving warehouse is building its intake file, or the main shipping wave is close enough that label release will turn every weak assumption into labor.
The review is not general advice. It is a stop-or-proceed decision on the current event chain: which items can safely become a China pre-kit, which should wait for U.S. warehouse build, which should stay loose, and which part of the file set still needs correction before freight, receiving, or label release keeps moving.
A file review can still keep a fixable China-side issue from turning into U.S.-side receiving labor, relabeling, re-kitting, replacement handling, or return work.
WinsBS returns the next operational state: China pre-kit, U.S. warehouse kit, loose SKU pick, partial hold, sample kit test, spare stock separation, kit BOM correction, or pick-rule correction.
Include the current freight plan, container or pallet structure, and expected receiving schedule if the shipment has already been booked. That is usually where hidden labor, relabeling, re-kitting, overflow storage, or replacement pressure first becomes visible.
Campaign Files
- Pledge-manager export
- Reward-to-SKU matrix
- Add-on list
- Stretch goal list
- Sample orders
Inventory Files
- Kit BOM
- SKU map
- Factory packing list
- Carton file
- Carton labels
- Freight plan if booked
Warehouse Files
- Receiving scan
- Warehouse bin setup
- Kit build instructions
- Pick rules
- Replacement reserve count
- Receiving appointment if scheduled
If you already have a shipment log or early exception examples, include them. They help identify whether the problem is the kit BOM, spare stock separation, receiving file, warehouse bin locations, or pick-rule release. If your team requires an NDA before sharing sensitive files, request that before sending documents.