ParcelPilot
Help

Items — Product Types And Components

Use this guide when you need to explain what kind of item a SKU is and how ParcelPilot will treat its stock and fulfilment behavior.

ParcelPilot calls the list of components required to build one finished product Assembly Components. In manufacturing this is often called a Bill of Materials (BOM).

The four current product types

1. Standard product

A normal stocked SKU.

Behavior:

  1. can be receipted directly
  2. has direct inventory units
  3. is picked and shipped as itself
  4. has no component-driven assembly behavior

2. Assemble-to-stock product

A finished SKU with Assembly Components that the warehouse builds before orders arrive.

Behavior:

  1. has Assembly Components
  2. has actual finished stock after Assembly completion
  3. can show Available to Build from current component stock
  4. is assembled before customer orders arrive
  5. is picked as the finished SKU
  6. does not explode into child components during fulfilment

3. Fixed build-to-order / fulfilment-expanding bundle

A fixed component bundle whose warehouse behavior stays component-driven.

Behavior:

  1. has a fixed component list
  2. does not create finished stock in advance
  3. does not have a separate finished-stock inventory bucket
  4. can show buildable availability from components
  5. expands into component demand during fulfilment
  6. is picked as components, not as the parent SKU

4. Configurable bundle

A bundle-style parent item where the operational meaning remains order-driven rather than prebuilt finished stock.

Behavior:

  1. has bundle configuration
  2. is not an assemble-to-stock finished-goods workflow
  3. remains part of fulfilment-expansion behavior rather than Assembly stock mutation
  4. should not be treated as prebuilt finished stock unless a later product phase explicitly adds that model

How to tell them apart on the item

Standard product

  • Product Type = Standard Product
  • normal stocked SKU with no recipe

Assemble-to-stock product

  • Product Type = Assemble to Stock
  • the Assembly section appears
  • Assembly Component rows define the Assembly Components
  • measured components show a measurement-aware quantity label, while count components still use a plain quantity label
  • the Minimum practical quantity field is advisory guidance for operational picking or consuming, not a required multiple for measured components
  • Additional Charges with charge type Assembly sets the default assembly unit rate for new Assembly jobs
  • optional Assembly Settings such as default batch size and instructions remain operational only

Fixed build-to-order bundle

  • Product Type = Explode on Fulfilment
  • the Bundle Components section appears
  • component rows define the stocked SKUs picked when the parent is ordered

Configurable bundle

  • Product Type = Configurable Bundle
  • the Bundle Components section appears

Key operational difference

The biggest distinction is between assemble-to-stock and fulfilment-expanding bundles.

Assemble-to-stock

  • components are received first
  • warehouse completes an Assembly
  • finished stock is created
  • orders pick the finished SKU
  • the finished goods must not be receipted again after Assembly completion
  • Assembly pricing comes from the item's Additional Charges entry with charge type Assembly
  • optional finished-stock receiving on the Assembly can bill by individual items, cartons, or pallets without creating a Receipt
  • if carton receiving is used, the finished item's current Units per case is the master data ParcelPilot uses until final completion, and the completed Assembly then freezes the case-pack and billed quantity used for historical billing

Fulfilment-expanding bundle

  • no finished stock is created in advance
  • order fulfilment expands demand into component lines
  • reservation, picking, and deduction happen on the components
  • component items mean "what gets picked", not "what gets built into finished stock"

Repacking pricing

Repacking uses the same single-source pricing pattern.

If an item has Repacking enabled:

  1. the item form shows Enable Repacking as a separate capability toggle
  2. the Repacking Configuration section keeps the operational conversion settings
  3. the item's Additional Charges entry with charge type Repacking provides the default repacking rate for new Repacking jobs
  4. legacy reboxing values may still exist for compatibility, but they are not the pricing source for new transactions

Where Available to Build fits

Available to Build is a component-based planning number.

It can be useful for:

  1. assemble-to-stock products, where it tells the warehouse how many finished units could be built now
  2. virtual fixed bundles, where it tells the system how many parent bundles could be fulfilled from component stock

It does not mean the finished stock already exists.

Related guides