Apply a Different Service Cost to One Assembly Build in NetSuite

The quick answer

For an ordinary assembly with an eligible service component, keep its Purchase Price fixed and change the component Quantity on the individual Assembly Build. With a fixed rate of 100.00, an intended allocation of 110.00 uses 1.10 service units: 110 / 100 = 1.10. Keep the finished Quantity to Build at 1.

This walkthrough checks the saved build and confirms that the shared Purchase Price and BOM default remain unchanged. Projected Value is a pre-save estimate, not proof of posted cost. No payroll, vendor invoice or time entry is created.

Before you start

Use an ordinary, non-WIP, average-cost assembly with a service component and an appropriate expense account for your manufacturing design. This example uses a Service for Resale item, plain quantities with no units conversion, and an open October 2026 period. It excludes standard costing, routings, yield adjustments, round-up rules, bins, lots and serial numbers.

The inventory cost inputs below are illustrative current costs at Eastgate Workshop. Account configuration, costing method and timing can change actual results. Test the workflow in your account and inspect actual costing and posting separately.

1. Read the fixed Purchase Price

Open Assembly Labor Unit, then Purchasing. Its Purchase Price is 100.00. Here that is a controlled allocation rate; the quantity does not represent labor hours.

Service Purchase Price is 100.00. — Keep Purchase Price 100.00 fixed. The example changes a build quantity, not this shared rate.

2. Check the BOM default

Open Kit Rev A, the effective revision for Equipment Kit BOM. It lists one Housing, one Fitting and one Assembly Labor Unit for a finished PK-10 Equipment Kit.

BOM Quantity and Quantity are one for all three components. — The last row is Assembly Labor Unit, with BOM Quantity 1. Enlarge for the component names and revision context.

3. Build one kit

Open Transactions > Manufacturing > Build Assemblies. Choose PK-10 Equipment Kit at Eastgate Workshop. Confirm Equipment Kit BOM and Kit Rev A, then enter Quantity to Build 1.

The illustrative inventory costs are 70.00 for Housing and 30.00 for Fitting. With service quantity 1 at Purchase Price 100.00, Projected Value is 200.00.

Initial Projected Value 200.00. — The pre-save estimate starts at 200.00:100.00 of inventory components plus 100.00 of service allocation.

Assembly Labor Unit defaults to component quantity 1. — The service component defaults to 1. Enlarge to see Housing and Fitting also at 1.

4. Override only the service quantity

For the intended service allocation of 110.00, calculate 110 / 100 = 1.10. On Components, change Assembly Labor Unit Quantity from 1 to 1.10, then leave the cell. Keep the two inventory component quantities at 1.

Assembly Labor Unit component Quantity is 1.10. — Only the service component quantity changes.1.10 is an abstract cost multiplier in this example.

Recheck Quantity to Build 1 and Projected Value 210.00 before saving. The service contribution is now 110.00 instead of 100.00. Click Save.

Updated Projected Value 210.00. — The pre-save estimate rises by 10.00. This field does not verify the actual posted GL amount.

5. Reopen the build and reconcile the shared defaults

Reopen ASSYB316. Confirm its Quantity to Build is 1 and its saved service component quantity is 1.10. The service multiplier has not increased the number of finished kits.

Saved assembly Quantity to Build 1. — The saved transaction builds one finished kit.

Saved service component 1.10 with inventory components 1 each. — ASSYB316 retains the service override. Enlarge to check the record identity and component lines together.

Revisit Assembly Labor Unit > Purchasing. Purchase Price should still be 100.00. Then return to Kit Rev A: the default service BOM Quantity should still be 1. The transaction override belongs to this build.

Shared service Purchase Price remains 100.00 after the build. — The saved build did not revise the shared Purchase Price.

Shared revision still shows service BOM Quantity 1. — The last component row still defaults to 1. A later build starts from the applicable BOM revision, not this override.

Common questions

Why change quantity instead of entering an amount?

The build component line accepts a quantity. With a fixed service Purchase Price, changing that quantity changes the estimated component contribution. Divide the intended amount by the configured rate; do not change the assembly output quantity to achieve the allocation.

Does 1.10 mean 1.10 labor hours?

No. It is an abstract multiplier in this example. Hours would require a deliberate hourly-rate and unit design. This workflow does not capture time worked, payroll or a vendor charge.

Does a build override change the item or BOM?

Changing a component quantity on one build does not revise the shared item Purchase Price or BOM default. Reopen all three records to verify the distinction and account for any custom scripts or workflows.

Does Projected Value 210.00 prove the posted cost?

No. It is the form's estimate under the displayed quantities and configured costs. Review actual GL Impact and the account's costing results separately.

When should I use a different approach?

Use the account's appropriate costing process when costs must follow standard costs, WIP, routing operations, actual time or vendor charges. Units conversion, yield, scrap and round-up rules can also make an abstract quantity multiplier unsuitable. This lesson covers only the narrow standalone average-cost example.

Sources

Original question and accepted quantity workaround.
Oracle: Building Assembly Items, including transaction-specific component quantities and Projected Value.
Oracle: Updating Costs for Manufacturing Charges, for eligible Purchase or Resale item types. That bulk-update process is outside this walkthrough.