The quick answer
Complete the primary assembly at the last WIP operation, then use your installed Co/By Completion extension to enter the actual quantity of each secondary output. Save the run and check its linked work orders, issues, completions, and total cost. Standard NetSuite work-order completion receives the assembly on that work order; the extra outputs and run summary shown here come from Bryant Park Consulting’s configured solution.
The screenshots use sample data. Person and company names are fictional. Your account’s extension settings and item tracking determine which fields and inventory detail you must complete.
Before you start
This example starts with WIP work order WO-644. It plans 100 liters of Garden Pasta Sauce, Bulk. Component issues and earlier routing operations are already recorded; operation 60 is the last operation. The run will yield 102 liters of sauce, 18 kilograms of tomato seeds, and 9 kilograms of tomato pulp.
You need Work Orders, Manufacturing Work in Process, and Manufacturing Routing for this routed example, plus permission to enter a Work Order Completion. Check the effective BOM and routing, location, transaction date, open posting period, prior component issues, and how much of the planned 100 liters can still be completed. The account must permit the demonstrated 102-liter over-completion. If components have already been issued, confirm the completion's Backflush setting so they are not issued twice. The primary and secondary items need the appropriate lot, bin, or status setup for their locations.
Bryant Park Consulting’s Co/By Completion solution must also be installed and configured for the secondary items, with the relevant forms, scripts, output mappings, and permissions enabled. The Enter Completion (Co/By) action and Co/By Completion Run record are extension screens. They will not appear in an account with only standard NetSuite manufacturing.
01. Check the WIP work order
Open WO-644 and check its In Process status, primary assembly, planned quantity of 100, and the earlier issues and operations. The work order shows both the standard Enter Completion action and the extension’s Enter Completion (Co/By) action. The demonstrated sequence starts the final primary completion from the standard action, then opens the extension run after that completion is saved.
02. Complete the primary assembly
Click Enter Completion. In this example operation 60 is the routing's final operation. Select it for both Starting Operation and Ending Operation. Enter 102 as Completed Quantity; the form’s Quantity to Build follows it. Check that your account permits completing 102 against the planned 100. The primary item is lot tracked in the demonstrated setup, so complete its required inventory detail in your account, with detail quantities adding up to 102, before saving. That detail dialog is outside this recording.
Save the primary completion. In this configured workflow, the save opens a Co/By Completion Run carrying the 102-liter primary output forward.
03. Record the secondary yields
Read the Co-By WO Completion Line table before typing. Its sauce row shows 100 planned and 102 completed. The secondary rows show tomato seeds planned at 20 kilograms and tomato pulp planned at 10 kilograms. Enter 18 for seeds and 9 for pulp in New Completed Qty. The inventory-detail indicators sit beside these rows. Supply the required lot, bin, or status detail in the installed solution before saving; the source does not show the secondary detail dialog or establish its exact fields.
04. Check the completed run
Save the run and wait for its configured processing. On the completed record, check the three output quantities. The extension's Work Orders tab links the primary work order and the two secondary work orders; the example shows WO-644-A for seeds and WO-644-B for pulp.
Open the extension's Co/By Completion Run Summary. It links generated work orders, work-order issues, and completions. The example totals 1,598.37: 1,561.62 in component cost and 36.75 in operations cost. Those figures are the demonstrated run’s totals, not a general cost-allocation formula. Follow the linked transactions and check their inventory detail, GL impact, and the extension’s allocation settings in your own account. Check Work Order Close and any residual WIP or variance separately when they apply.
Check the result
- The primary completion records 102 liters at final operation 60.
- The completed run records 18 kilograms of seeds and 9 kilograms of pulp.
- The run links its output work orders, issues, and completions, and the example’s total value is 1,598.37.
Common questions
Can standard NetSuite Work Order Completion receive several different finished items?
A native completion receives the assembly item on its work order. This example’s distinct seed and pulp outputs use an installed Co/By extension and its configured secondary work orders and transactions.
Where do I enter the actual co-product and by-product quantities?
In this solution, enter them in New Completed Qty on the Co/By Completion Run. Check the item and its required inventory detail before saving. Another account’s custom form or extension may differ.
Must actual secondary yield match the planned quantity?
Not in this configured solution. This run planned 20 kilograms of seeds and 10 kilograms of pulp, then recorded 18 and 9. The source also says a secondary output may have zero actual yield. It does not show whether zero creates no transaction, leaves a zero-quantity line, or leaves an unfinished secondary work order; check the installed solution's behavior.
Does the 1,598.37 total tell me each product’s cost?
No. It is the total displayed for this run. The source does not expose the extension’s allocation formula or full GL postings. Open the linked transactions and inspect the configuration and GL impact before using per-output cost figures.