Bundle System

Important: Pre-Bundled Inventory

If your products arrive at the warehouse already bundled (for example, shrink-wrapped kits or factory-assembled sets):

➡️ Do NOT use the Bundle Sold As type.
➡️ Instead, create the inbound order as Sold As: Individual.

Why?

• There are no individual components to receive separately
• The bundle itself is the physical unit being checked in
• Using the Bundle system would incorrectly expect child items to be received

📌 Rule of thumb:
Use Bundle only when the warehouse is assembling the bundle from individual items.

PrepFlow’s Bundle System allows you to accurately manage products that are sold as a single unit but consist of multiple individual items.
It ensures inventory stays consistent, prevents partial bundle shipments, and eliminates manual reconciliation.

Bundles are designed to be safe, predictable, and warehouse-friendly.

1. What Is a Bundle?

A bundle is a sellable product made up of multiple different items that are received separately and assembled inside the warehouse.

PrepFlow represents bundles using a parent–child structure:

• Parent Order
  • Represents the sellable bundle
  • This is the order that holds inventory and is shipped
• Child Orders
  • Represent the individual component items
  • Used only for receiving and internal tracking

📌 Important: Only the parent bundle order represents real, shippable inventory.

2. When to Use (and Not Use) Bundles

Use the Bundle System When:

• Items arrive as separate components
• The warehouse assembles the bundle
• Each component must be checked in individually

Do NOT Use the Bundle System When:

• Items arrive already bundled
• There are no individual components
• The bundle itself is what gets checked in

In those cases, simply create a normal inbound order using Sold As: Individual.

3. Creating a Bundle Inbound Order

When creating an inbound order:

1. Set Sold As to Bundle
2. Enter:
   • Units per Bundle
   • Total Units Ordered (always in individual units)
3. Add the required bundle items (child orders)

PrepFlow enforces that:

• The number of bundle items must match units_per_pack
• Each child order must have a valid quantity
• Partial or mismatched bundles cannot be created

This prevents broken or incomplete bundle definitions.

4. Receiving & Check-In Behavior

Check-Ins Happen on Child Orders

• Warehouse users check in child orders only
• Parent orders cannot be checked in directly

As child items are received, PrepFlow automatically determines how many complete bundles can be formed.

Inventory Conversion Logic

Bundles are created when all components are available.

Example:

→ Parent bundle inventory increases by 20 units
(because inventory is always tracked in individual units)

Once bundled:

• Child orders may show 0 remaining
• Parent order holds the usable inventory

💡 This is expected behavior and prevents double-counting.

5. Inventory Visibility Rules

• Parent bundle orders
  • Appear in inventory
  • Are selectable for shipments
• Child bundle orders
  • May show 0 remaining
  • Should not be used for fulfillment
  • Are hidden or filtered from shipping workflows

This ensures warehouses never ship incomplete bundles.

6. Shipping Rules for Bundles

Only Parent Orders Can Be Shipped

PrepFlow enforces that:

• Child orders cannot be added to shipments
• Shipments may only contain parent bundle orders

When a bundle is shipped:

• Inventory is deducted from the parent
• Child orders remain untouched

Status Synchronization

• When a parent bundle is fully shipped:
  • Child orders are automatically updated to outbound
• When shipments are undone:
  • Child orders return to inventory

This keeps inventory views consistent and prevents ghost stock.

7. Uncheck-Ins & Adjustments

PrepFlow safely handles uncheck-ins and corrections:

• If child inventory was already bundled:
  • PrepFlow will automatically break bundles if possible
• If bundles were already shipped:
  • Uncheck-ins are blocked to prevent corruption

This guarantees inventory integrity even during corrections.

8. Legacy Orders & Compatibility

• Older bundle-style orders (created before this system)
  • Continue to work normally
  • Are not blocked by new constraints
• New bundle rules apply only to orders created or modified using the Bundle System

No migration is required.