Build Types

Updated 1 month ago by Austin Beveridge

Wheelhouse supports various build types and usage guidelines to streamline development and management workflows. The platform leverages structured processes to manage build configurations, providing clarity on settings, roles, and data organization for developers and administrators.

Build Type Reference

Build Types in Wheelhouse: Usage Guidelines

When to use Product (configurable) vs Product (non-configurable):

• Use Product (configurable) when customers need to make selections or customize the item during ordering. Always drills into components ignoring stock because every item is configured.
• Use Product (non-configurable) for standard items that don't require any configuration or customization. May contain components but they are ignored since the item is never configured.

When to use Package vs Option:

• Use Package when you want to group multiple items together as a pre-configured bundle. Always drills into components ignoring stock.
• Use Options for individual configurable components that can be selected within a Product. Always drills into components ignoring stock.

When to use Pseudo vs Phantom:

• Use Pseudo when you need a pure container that always drills to components. Never saleable and ignores stock.
• Use Phantom when you want the flexibility to either stock the assembly or use components. Checks stock first - if not found, treats as container and drills into components.

When to use Phantom vs Make:

• Prefer Phantom assemblies when components should be stocked and tracked individually
• Use Make only when specialized manufacturing or assembly conditions are required, such as:
• Items requiring precision machining or tight tolerances
• Components needing clean room assembly
• Parts requiring specialized equipment or expertise
• Items that must be built by dedicated teams

When to use Buy vs Make:

• Use Buy for purchased components that don't require internal manufacturing
• Use Make when internal manufacturing or specialized assembly is required

Special Purpose Types:

• Stash: Used only as location placeholders in inventory management
• Public Display Group: Used for organizing product selection menus/trees
• Engineering Only: Used for documentation but ignored in inventory

Additional Guidance by Type:

Use Make when:

• The assembly requires expertise that is not shared in the main assembly line
• The assembly requires environmental conditions (such as a clean room) not shared on the main assembly line
• The assembly requires specialized equipment not available on the main assembly line
• The assembly requires testing and certification before incorporation into the main assembly

Use Phantom when:

• You want to maintain the option to either pre-build or build-to-order
• Stock levels may vary based on demand patterns
• You need flexibility in your production scheduling
• Assembly time could impact overall production flow

Use Package when:

• Multiple items are commonly sold together
• You want to streamline the ordering process
• Pricing differs when items are bundled
• You need to track components but present them as a unit

The key is choosing the build type that matches both your inventory needs and manufacturing requirements. Consider factors like:

• Whether the item needs configuration options
• If specialized manufacturing processes are required
• How inventory should be tracked
• What kind of stocking strategy you want to use

Key BOM Drilldown Behaviors:

• Continue: Always drills into components ignoring stock
• Stop: Components exist but are ignored
• Use Stock, Continue: Checks stock first, if not found drills into components
• None: Ignored for inventory purposes

How did we do?

Related Articles

• Merge Line Items at a Certain Step (Stash & Merge Functionality)
• Item Types
• Native Types