Operator Guide: Virtual Bundles
This guide explains how warehouse operators handle Virtual Bundles during daily operations: recognize bundle lines, scan and pick items, verify shipments, and resolve common issues.
Overview
- A Virtual Bundle is a sales bundle: multiple products sold under a single SKU/barcode.
- When an order contains a bundle, the system automatically expands it into individual product lines and deducts inventory by those expanded items.
- An OrderBundle snapshot is created at order creation to freeze the bundle configuration at that time. Later changes by Admin do not affect existing orders.
- Operators do not maintain bundles (no create/edit). Focus on fulfilling expanded product lines.
Scope and Merchant Selection
⚠️ Operators belong to an Organization and must select a Merchant before working with data.
Tips:
- Use the Merchant selector at the top to switch to the correct Merchant.
- After switching, orders and inventory reload according to the selected Merchant.
Where you see Bundles
- Order details / Picking tasks: bundle lines are displayed as a “Bundle → Expanded items” block.
- Picking & parcel: work against the expanded items (scan/confirm, verify quantities, follow location hints).
- Shipping check: verification is based on expanded items.
UI and Indicators
In order or picking views, bundles typically show:
- Bundle name and bundle SKU
- Ordered bundle quantity (how many sets)
- A list of component items with “per set quantity” and “total required quantity”
- Expanded item rows tagged as “from bundle” for clarity
Common fields:
- Bundle SKU, bundle barcode (if scanning by bundle is supported)
- Per-set usage and aggregated totals
- Location, available stock, allocated quantity, out-of-stock warnings
Scanning and Quantity Handling
Two practical modes (depending on page design and permissions):
- Scan the bundle barcode (if supported)
- Scanning a bundle barcode automatically increments the “completed quantity” of each component item according to the bundle configuration.
- Example: bundle contains A×2 and B×1; scanning 2 bundles → A completes 4, B completes 2.
- Scan expanded item barcodes (always applicable)
- Scan and confirm each expanded item directly.
- The system aggregates completion under the corresponding bundle block to ensure totals are met.
Recommendations:
- If your floor process primarily picks individual items, use item-level scanning.
- If your bundles are pre-labeled and processed by set, bundle scanning can speed things up.
Picking Workflow (Example)
- Open the order or picking task; ensure the Merchant is correct.
- Locate bundle sections and review component items and required quantities.
- Follow location guidance on the floor; scan or input completion for each item.
- If bundle scanning is available, scan the bundle barcode to auto-increment component completions.
- Handle shortages: mark out-of-stock/partial completion and follow your escalation (substitute, backorder, split shipment, etc.).
- When all component items are completed, the bundle block turns “Completed”.
Shipping and Verification
- Shipping checks are based on the expanded items to ensure quantities and moves are correct.
- If documents need to show bundle info, print/exports retain bundle name and configuration from the snapshot.
Bundle Snapshot (Operator Perspective)
- At order creation, an OrderBundle snapshot records the bundle definition at that time.
- Even if Admin edits the bundle later, existing orders are unaffected. Your work remains aligned with the snapshot.
- You may see snapshot-related indicators to make it clear which definition your task follows.
FAQ
Q: Scanning the bundle does nothing?
- Check if the page supports “bundle scanning”. If not, scan component items instead.
- Ensure you’re scanning the bundle barcode (not a component barcode).
- Verify the current Merchant is correct (barcodes/configuration may differ across Merchants).
Q: A component item is out of stock. What should I do?
- Mark shortage or partial completion, then follow your internal process (replenish, substitute, split, etc.).
- The bundle’s overall completion reflects the component statuses.
Q: Admin updated a bundle. Do I need to adjust?
- No. Existing orders follow their snapshot. Your task remains unchanged.
Q: Can I create/edit bundles in the Operator app?
- No. Bundle maintenance is handled by Admin. Operators focus on execution.
Differences vs Admin
| Aspect | Admin | Operator |
|---|---|---|
| Create/Edit Bundles | ✅ Yes | ❌ No |
| Views | Detailed setup and composition | Focus on expanded items in orders |
| Inventory Impact | Through expanded items | Work against expanded items |
| Snapshot | Created by the system | Execute based on snapshot |
Related Docs
- Admin: Bundles Overview
- Admin: Bundles List
- Admin: Bundles Show
- Operator: Product Management
Note
- After docs change, if the menu or content doesn’t show, ask a developer to restart the frontend dev server (we do not auto-restart).