Location Assembly

What a Location Assembly is

A Location Assembly lets you take several stock items that are sitting together at one location — a warehouse bin or your own personal inventory — consume them and produce a single assembled product, with no Bill of Materials (BOM) required.

It is the tool for turning loose material into one finished thing on the spot: a kit, a made-up sub-assembly, or an assembled unit — without pre-defining a recipe. You point at what is on the shelf, choose the product to build, and the system consumes the parts and produces the output in one audited transaction.

Why use it (and why there is no BOM)

Normal manufacturing assemblies are driven by a BOM — a fixed recipe that says exactly which components, in which quantities, make a defined product. That is the right tool when you build the same thing over and over.

A lot of real work isn't like that. You are making a one-off assembly — kitting a job, bundling parts, building a made-up unit — and there is no standing recipe. Defining a BOM for every one-off would be pure overhead. Location Assembly is built for exactly this:

• No BOM, no setup. Consume whatever is at the location and produce the output now.
• Cost flows into the output. Everything you consume is rolled into the finished product's value, so it carries the total cost of the material that went into it.
• Fully traceable. Every item consumed is recorded as an audited stock movement, and the finished assembly keeps a permanent list of exactly what went in.

Choosing the output product

When you create a Location Assembly you pick the output product — any assembled product in the catalog. Two things to keep in mind:

• The output should be a different product from the items you are consuming. A product cannot be both consumed and produced in the same build (the ERP rejects a stock adjustment that lists one product twice), so you will get an error if you pick a product that is also one of the items being consumed.
• If you need a repeatable, defined product built from a fixed recipe, use Production Assembly (which is BOM-driven) instead.

How to create one

From a location (Location Inventory):

1. Open the location's stock (Locations → Warehouse Locations → open a location, or a deep link).
2. Click Actions → Create Location Assembly (only shown if you hold the Create custom assemblies permission).
3. The page switches to selection mode — tap the items you want to consume. For non-serialised stock you can set how much of each stack to use; serialised stacks are taken as whole units.
4. Choose Create assembly (in the selection bar's ⋯ More menu).

From your own stock (My Inventory):

1. Open My Inventory, tap Select items, and select the parts you are holding.
2. Choose ⋯ More → Create assembly — the output is produced straight into your own inventory (handy for building a kit from the parts you carry).

In the dialog (both paths): pick the Output product to build, set the quantity, add serial numbers if the output is serialised, optionally tick Custom value to override the cost, then confirm Assemble.

What happens to stock and cost

• Every selected item is consumed (removed from the location) through the audited stock-movement flow.
• The output product is produced at the same location.
• The output's value is set to the sum of the value of everything consumed (material cost).
• Costing is material-only — labour / overhead are not added to the assembled value.
• The build is recorded as an Assembly with a permanent list of the component items (the "what went in" trail), visible in the report below.

Seeing what was built — the Location Assembly Report

Every Location Assembly is listed in Warehouse → Reports → Location Assembly Report. For each build you see the output product, quantity, total cost, area, who built it and when, and you can expand a row to drill into every component item that went in (product, quantity, unit and total cost).

Because the report shows cost, it is gated by its own Location Assembly Report permission (which also serves as the cost-visibility gate). The same data is available to integrations at GET /rest/v2/assemblies/location-report.

Permissions

Notes & limitations

• Output must be a different product from the consumed items — a product can't be both consumed and produced in one assembly.
• For a brand-new SKU from a fixed recipe, use Production Assembly (BOM-driven) instead.
• Material-only cost — the assembled value captures the cost of the consumed stock, not labour or overhead.
• Serialised products are supported (capture the output's serial(s) in the dialog).
• Reversible — a Location Assembly can be taken apart again with Disassembly, which returns the component items to stock.