The quick answer
Open Pick Order on the OzLINK handheld, enter the work order, then scan each required item and its source bin with the prompted quantity. After the final item, tap Finish and read Order pick complete!. Refresh the NetSuite work order and open its custom OzLINK tab. The example lists three picked components and checks Work Order Picked, while the work order remains Pending Build with Built 0.
This walkthrough follows an older partner demonstration. The people and business names in the recording are fictional example data. The handset and custom tab belong to OzLINK, so your account needs that integration and may present different fields. The current production account did not expose an OzLINK tab; the partner screens in this guide are reconstructed from the source video.
Before you start
You need access to the OzLINK Pick Order function, a work order available to that function, and components in the prompted bins. Confirm your site’s scan and quantity rules before picking. The example uses work order 1776 with three component lines. It is Pending Build at the start and still Pending Build at the end.
Scope: The recording shows the partner pick-complete message and custom work-order picked status. It does not show an assembly build, a native inventory transaction number, or before-and-after bin balances. The generic “Transaction successfully Saved” banner in the source appears without its save action, so it is not used as a result checkpoint here.
01 · Open Pick Order
Choose Pick Order from the OzLINK main menu. Enter your user ID and scan or type the work-order number. For this example, use 1776. The handheld then loads the component prompts for that order.
02 · Pick the first component
The first prompt identifies item 5001 in bin A01, quantity 3. Scan the item, then the bin. Enter 3 in Qty and tap Add Item. Check the yellow prompt before adding the line; it ties the item, bin, and required quantity together.
03 · Pick the remaining components
The next prompt is item 5002 from B24, quantity 2. Add it, then pick item 5003 from Dock, quantity 1. The narrator says a wrong item or bin scan would prompt a warning, but the source does not demonstrate that error path. Follow the actual prompt shown by your deployment instead of assuming the order or bin will always match this example.
04 · Finish the partner pick
After adding the last component, tap Finish. The OzLINK alert says Order pick complete!. This is the mobile workflow’s result. It does not mean that someone has used Create Build or finished the assembly.
05 · Check the work order
Return to the NetSuite work order, refresh, and open the custom OzLINK tab. In the source, Items Picked lists all three components with quantities 3, 2, and 1 and a designated picked bin. Work Order Picked is checked. The header still says Pending Build, and the primary information shows Built 0. That is the pre-build handoff shown here.
Check the result
- Partner pick: The handheld showed Order pick complete!.
- Custom tab: The picked list and Work Order Picked flag show the partner status recorded in this example.
- Native work order: Pending Build and Built 0 show that assembly completion is a separate step.
Common questions
Does “Order pick complete!” mean the assembly is built?
No. The source work order still reads Pending Build and Built 0 after the pick. The alert is from the partner handheld.
Where do I see what was picked?
In this deployment, refresh the work order and open its custom OzLINK tab. It lists item IDs, quantities, and a designated picked bin. Accounts without that integration will not have this tab.
What if an item or bin scan is wrong?
The source narrator says OzLINK warns the operator. The video does not show the exact warning screen or recovery steps, so follow your deployed prompt and correct the scan before adding the item.
Does the saved banner prove a native inventory transaction?
No. The source shows a generic saved banner on the refreshed work-order page without showing the action that caused it. Check the actual saved record and inventory detail separately if posting proof matters.