Component lists
Each kit defines its components and quantities. The kit's availability rolls up from component availability.
Use case
The gift bundle on the website says 'In Stock'. The ribbon ran out yesterday. So did the candle. The bundle is not actually in stock. Kit and bundle tracking software is the bookkeeping that prevents that. Order3 holds bundles with their component lists, runs pack and unpack from a phone, and rolls component availability up to the bundle.
Definition
A kit or bundle is a collection of items sold or shipped as one unit. Ecommerce sellers ship gift sets and starter kits. Event production companies pack roadcases of cables, mics, and gear. 3PLs build customer kits to spec. Medical practices stock procedure trays and crash carts. The shared problem: the kit's availability depends on its components' availability, and packing or unpacking changes the count of every component. Without proper bookkeeping, oversells happen because a bundle was listed available when one component had run out, or returns get processed as a single unit when a component is actually missing.
Capabilities
Each kit defines its components and quantities. The kit's availability rolls up from component availability.
Pack a kit by scanning components into the kit record. Unpack reverses the flow. Counts update on both sides.
Sellable count for the bundle is the minimum implied by component stock. If any component runs out, the bundle goes unavailable.
Mark kits as single-use (consumed when sold) or reusable (returned and re-packed). Workflow adapts to either.
On return of a reusable kit, scan to confirm components. Missing components are flagged for replacement and logged.
Run pack and unpack from a phone or tablet at the pack station. Component counts update in real time.
How it works
Define the kit
Build the kit record: components, quantities, packaging notes, and whether it's single-use or reusable.
Pack
At the pack station, scan each component into the kit. The system checks completeness and updates component counts.
Ship or deploy
Single-use kits ship as products. Reusable kits go to events, projects, or customers and stay tracked as a unit.
Reconcile on return
Reusable kits scan back in. Missing components are logged; the kit either re-enters service or goes to repack.
Workflow artifact
A useful kit & bundle tracking workflow leaves an item, location, owner, next action, and approval trail behind it.
Order3 record
Trigger
Component lists
Each kit defines its components and quantities. The kit's availability rolls up from component availability.
Evidence
Define the kit
Build the kit record: components, quantities, packaging notes, and whether it's single-use or reusable.
Next action
Pack
At the pack station, scan each component into the kit. The system checks completeness and updates component counts.
Control
Reconcile on return
Reusable kits scan back in. Missing components are logged; the kit either re-enters service or goes to repack.
Who runs this
Ecommerce sellers offering bundles, gift sets, or starter kits where availability depends on multiple components. Event production companies packing roadcases of cables, mics, and gear that travel between venues. 3PLs running kitting services for SMB clients: branded boxes, subscription kits, marketing samples. Medical and dental practices managing procedure trays and crash carts where missing components have real consequences. Manufacturing teams building component kits for a downstream assembly line. The shared trigger: kits need their own bookkeeping or the math does not add up.
Fit checklist
Component lists
Each kit defines its components and quantities. The kit's availability rolls up from component availability.
Pack and unpack workflow
Pack a kit by scanning components into the kit record. Unpack reverses the flow. Counts update on both sides.
Bundle availability
Sellable count for the bundle is the minimum implied by component stock. If any component runs out, the bundle goes unavailable.
Reusable vs single-use kits
Mark kits as single-use (consumed when sold) or reusable (returned and re-packed). Workflow adapts to either.
How it works in Order3
Order3 holds kits as parent records with component lists. Multi-location stores both kits and components at the right location. Barcode scanning runs the pack and unpack workflow from the mobile app. Sellable bundle counts roll up from component availability automatically. If any component runs out, the bundle becomes unavailable across channels through the integrations layer. The activity log captures every pack and unpack event with user and timestamp. Reusable kits track their lifecycle: deployed, in transit, returned, repacked, available. The AI assistant can answer 'how many gift bundles can we ship today' by checking component stock.
Feature
Scan an item, confirm a quantity, and update the record from the floor. Order3 reads UPC, EAN, Code 128, Code 39, QR, and GS1 DataMatrix from an iOS or Android camera, plus Bluetooth handheld scanners that act as keyboards.
Feature
One hand on the device. One hand on the inventory. The Order3 mobile app is built for that posture: scanning, counting, photographing, and transferring from any iOS or Android phone or tablet. Pair a Bluetooth handheld scanner if you're moving thousands of units per shift; the app treats it as keyboard input and the workflow stays identical.
Feature
Multi-location tracking means you can answer 'where is it' without calling someone. One workspace holds stock across warehouses, retail shops, trucks, jobsites, stockrooms, zones, and bins. Each keeps its own balance. Transfers between locations are first-class events, not adjustments hidden inside a global total.
Feature
Most low-stock alerts are noise. This one shows up with the lead time factored in, the right owner attached, and a next action one click away. Hand off to the purchasing agent for a draft, request a transfer from another location, or dismiss with a documented reason. Dashboards that nobody opens twice were not the goal.
How to choose
Test the bundle availability logic before anything else. Selling a bundle when a component has run out is the most common (and most embarrassing) failure mode. Confirm pack and unpack run from a phone fast enough for real pack-station throughput. Check that the system handles your specific kit pattern: simple bundles, configurable kits, or fully custom assembly. Don't pick Order3 if you run a high-volume kitting operation as the core of your business with full BOM, configurable products, and multiple pack lines. A dedicated kitting WMS or a manufacturing-aware platform like Cin7 or Katana is built for that. Order3 covers SMB kitting and bundle tracking.
Related guides
Guide
Inventory management for a small business comes down to four things: knowing what you have, where it is, what changed, and what to reorder next. Most small teams do not need an ERP. They need clean item records, named locations, reorder rules where shortages hurt, and a weekly rhythm that survives a busy quarter.
Guide
Multi-location inventory has three layers: bin, location, region. Track stock at every physical place it rests, with separate quantities, separate reorder rules, and a clear record of every movement between locations. Get the location hierarchy and transfer accountability right and the rest of the system follows. Get them wrong and every report lies.
Loosely interchangeable. The convention: a bundle is usually a sales SKU bundling several products together (gift set, starter kit), and once sold, it's consumed. A kit can be reusable (event roadcase, procedure tray) and travels as a unit through cycles of deployment and return. Order3 supports both patterns on the same kit record. Mark it single-use or reusable; the workflow adapts.
Yes. Many ecommerce bundles are virtual: components live separately and get packed only when an order comes in. Order3 holds the bundle as a virtual kit with components. Sellable count rolls up from component stock. At order time, a pick list pulls each component for the order. You don't pre-pack bundles unless you want the inventory cost of doing so.
Bundle availability drops to zero (or to the new minimum implied by remaining components). Order3 flags the component shortage and the purchasing agent drafts a reorder. If you're syncing availability to a sales channel, the channel sees the bundle as unavailable until the component restocks. The point is preventing the oversell.
Yes. On return, scan the kit back in and the system prompts to confirm components. Missing or damaged components are logged and either replaced from stock or queued for reorder. The kit either re-enters service immediately or goes to a repack queue. Common pattern for events, medical procedure trays, and any reusable kit that cycles between locations.
Yes. The same component SKU can appear in multiple kit definitions. Stock decrements once when packed into whichever kit is being built. Useful for shared parts across multiple bundle SKUs and for components that show up in both standalone sales and bundle assemblies.
Defining kits is fast: usually a day for a few dozen kit definitions. The slow part is reconciling component inventory and running the pack workflow until the team is fluent. Plan a week to a month, depending on kit complexity and volume. Run parallel with whatever spreadsheet or whiteboard you're replacing for at least one cycle.
Adjacent use cases
Start with the SKUs, locations, and counts behind the problem. Bring in expert help when the workflow needs integrations, approvals, or agent policy.