A kit is a product you invent on the warehouse floor: five components from three suppliers become one ASIN a competitor can't match by lowering a price. ProShip3PL receives each component, holds a documented build recipe for your kit, assembles on a staged line, places your inserts, and ships scan-verified finished kits into FBA on the standard 24–48 hour clock. Retail multipacks are a different craft — our bundling page covers those.
Sellers usually discover kitting through margin math. A single component fights twenty identical offers on price; a curated kit — the device plus the case plus the cleaning cloth plus a printed guide — creates a listing nobody else carries. The catch is operational: someone has to physically build that product, identically, hundreds of times, from parts that arrive from different suppliers on different days.
That's the work this page describes. Every kit we assemble starts as a written build recipe: component list with quantities, packaging format, insert positions, and a reference photo of one correct unit. Components check in against that list as they arrive and wait staged together, so the run starts only when everything needed is physically on hand.
Assembly runs as a line, not a free-for-all — one station opens cartons, one places components, one seats inserts, one closes and labels. The finished kit carries a single FNSKU; component barcodes are covered or enclosed so Amazon's scanner can only read the kit. A spot-open check before the run closes catches drift while it's still cheap to fix.
One boundary worth naming: multipacks and shrink-wrapped pairs of retail products are bundling, a simpler craft with its own page. Kitting is for products that only exist once components meet.
| Kit build element | How we run it |
|---|---|
| Bill of materials | Written recipe per kit, versioned when contents change |
| Component intake | Each supplier delivery counted and condition-checked separately |
| Staging | All components held together; run starts only when the set is complete |
| Assembly | Station line following the recipe and reference photo |
| Identity | One kit-level FNSKU; component barcodes hidden from the scanner |
| Verification | First-unit check, spot-opens, and scan-verify before FBA release |
A core product plus everything a first-time buyer needs — assembled in a fixed order so the hero item is what they see on opening.
Presentation-first builds: printed boxes, tissue or tray layers, cards seated exactly where the recipe says — because the unboxing is the review.
Rotating contents handled as recipe versions — each cycle dated, photographed and archived so no two cycles get mixed on the line.
Components converging from several factories and print shops, each intake counted separately, the kit built only from complete sets.
Instruction cards, warranty slips and thank-you notes treated as counted BOM lines with a defined position inside the pack.
One FNSKU per kit, applied and scan-verified; exposed component UPCs covered so the kit can't check in as a loose part. Fresh label specs live on our FNSKU labeling page.
Your BOM, packaging choice, insert positions and reference photo confirmed before any component ships.
Each supplier delivery checked in against the recipe and staged with its kit — shortages flagged the day they show.
First units checked against the photo, then the line runs; finished kits are spot-opened and scan-verified.
Completed kits case-pack into a compliant shipment and hand to the carrier on the 24–48 hour clock.
An exposed component UPC is outscanning your kit label. We rebuild the outer pack so only the kit FNSKU reads — and scan-verify every unit before it goes back.
That's assembly without a recipe. We define component positions, add internal packing where the layout needs it, and photo-document the correct build so every set opens the same way.
We stage what's here, chase the shortage list with you daily, and start the line the hour the last part clears the dock — the run plan is already written while you wait.
Kitchen-table kitting stops scaling around the first big PO. Hand us the recipe, redirect the component deliveries here, and your evenings stop being an assembly shift.
Kitting builds one product out of different components — a starter kit, a gift set, a tool plus its accessories — following a build recipe. Bundling multiplies or pairs retail items, like a 3-pack of the same soap or two complementary products shrink-wrapped together. The assembly discipline differs: kits need staged components, a fixed build order and presentation control. For retail multipacks and pairs, see our bundling service page.
The kit sells under its own ASIN and its own FNSKU — that's what makes it one sellable unit in Amazon's eyes. During assembly we make sure component barcodes are covered or enclosed so only the kit-level FNSKU is scannable from outside. An exposed component UPC is the classic kitting failure: Amazon scans the wrong code and your kit checks in as a single loose component.
Each kit gets a documented build recipe — a bill of materials listing every component, its quantity, its position in the packaging and any insert — plus a reference photo of a correctly built unit. The line assembles against that recipe, and completed kits are counted and spot-opened before the run closes. When the recipe is on file, run five hundred today and five hundred next month and they match.
The run pauses at the shortage point rather than shipping incomplete kits. You get a same-day note stating how many kits are finished, how many are blocked and exactly which component is missing, so you can push your supplier for just that part. Finished kits can ship to FBA immediately while blocked ones wait staged — a partial run beats a stockout.
Yes — rotating-content kits are a build-recipe versioning problem, and that's how we treat them. Each cycle gets its own dated recipe and reference photo; old versions stay archived so a re-run is reproducible. Send the next cycle's component list before the components land and the line switches over without confusion between the outgoing and incoming builds.
Seasonal runs are the most schedule-sensitive kitting work we do. Components can arrive weeks early and wait staged in our racks, the assembly run is booked against your launch date, and finished kits move to FBA far enough ahead of the selling window to check in. The date to protect is Amazon's receive scan — we plan the build backwards from it.
Yes, and position matters more than sellers expect. The recipe records where each insert sits — on top so it's the first thing seen, between components, or beneath a tray — because a gift kit opened by the recipient is a presentation moment, not just packaging. Print your inserts and ship them with the components; we treat them as a counted line item like any other part.
Whatever the kit's presentation calls for, supplied by you or sourced with us: printed retail boxes, mailer-style cartons, or a poly bag with suffocation warning where the kit is soft goods. The outer pack must survive FBA handling and present one scannable FNSKU. If your kit box isn't decided yet, send dimensions of the components and we'll recommend a format.
Three gates: components are counted and condition-checked at receiving, the first assembled units of a run are verified against the reference photo before the line continues, and finished kits are scan-verified so the kit FNSKU reads and no component barcode does. Anything that fails a gate is set aside and reported with photos before the run closes.
Send the form with your kit concept: how many components, where each comes from, target kit quantity and any launch date. We'll reply within one business day with per-kit pricing, a draft build recipe to confirm, and receiving instructions for each component supplier. No setup fees, no monthly minimums — you pay per assembled kit.
Describe the kit: components and where each comes from, quantity for the first run, packaging idea, launch date if there is one. Within one business day you'll have per-kit pricing and a draft build recipe to approve.
