Product bundles vs pick bundles — naming explained
In Dark Store Systems, “pick bundles” are zone-grouped pick-work units (OrderBundles) for handheld walks — not kit BOM execution. ProductBundles are sellable kit listings in catalog data; order lines may reference bundle IDs, but picking remains line and product-instance based. Do not assume one-SKU kit picks without verifying your product setup.
What is a pick bundle in Dark Store Systems?
A pick bundle is a zone-grouped pick-work unit — an OrderBundle on the handheld bundle station. When an order releases, the WMS splits lines by zone so each picker walks one coherent slice of the warehouse.
Pick bundles are how bundle picking organises work on the floor. They are not a single composite SKU and not kit BOM execution. Operators still confirm individual lines and product instances at the shelf.
What is a product bundle?
A product bundle (ProductBundles) is catalog data — a sellable kit listing made of component SKUs. Channels may sell it as one product, but fulfilment expands to order lines the WMS must pick.
Order lines can reference a BUNDLE_ID from the catalog. Batch pick may group lines that share that ID, but execution remains line and instance based. There is no default “pick the kit as one barcode” path unless your tenant has verified that product setup explicitly.
How do pick bundles and product bundles differ?
| Term | What it is | Where it lives | Picking behaviour |
|---|---|---|---|
| Pick bundle | Zone pick-work unit for one slice of an order walk | OrderBundles on the pick queue and handheld station |
Scanner walk: confirm lines, skip, part-pick, park to consolidation |
| Product bundle | Sellable kit listing in catalog data | ProductBundles and order line references |
Lines expand to component SKUs; pick each instance — not one-SKU kit pick by default |
Confusing the two terms is how procurement teams end up evaluating “kit picking” that is really zone splitting — or assuming composite picks that the WMS does not execute.
Does batch pick group by product bundle?
Batch pick uses OrderPickBatch jobs (pick flow 3) to group work across orders. It can group lines that share a catalog BUNDLE_ID, but that is grouping for the walk — not picking a pre-assembled kit as one physical SKU.
The live multi-order mechanism in the WMS is batch pick. Admin screens labelled “multi-order picking” are mock UI with disclaimers; evaluate batch pick and bundle pick as production paths. See also multi-order picking for the honest feature-page framing.
For the full picking-mode map, start at the warehouse picking hub.
Frequently asked questions
Can I pick a kit as a single SKU?
Not by default. ProductBundles are catalog listings; the WMS picks expanded order lines and product instances. Pick bundles (OrderBundles) are zone work units — not BOM execution. Verify your product setup with your operations team before assuming one-scan kit picks.
What is Order_BundleBuilder?
Bundle building runs when orders release from the pool: lines split into zone pick-work units (OrderBundles) for the handheld station. That is warehouse work allocation — separate from catalog ProductBundles sold on channels.
Does batch pick group by product bundle?
Batch pick can group lines that share a catalog bundle ID across orders, but picking remains line-based. It is not composite kit execution. See batch pick vs multi-order picking for what ships today.
Is bundle picking the same as kit picking?
No. Bundle picking is the live zone walk on the handheld station. Kit picking in marketing usually implies BOM or one-SKU composite picks — which Dark Store Systems does not claim without tenant-specific verification.