The quick answer
Open Bin Putaway in the RF-SMART mobile menu. Confirm the displayed Location and From Bin, then use Load Items to choose a received item. Review the suggested-bin rows by Last Putaway, Quantity (EA), and Cap. Enter the quantity, scan or enter a destination at To Bin, and tap Submit. A green Bin transfer submitted strip is the mobile result shown here. Check the resulting NetSuite transaction and bin balances separately if you need proof that inventory moved.
This walkthrough follows a received coffee dripper in the Auckland receiving bin. The person and company names in the recording are fictional example data. The handheld interface is RF-SMART, a partner application; it is not the native NetSuite WMS Mobile screen.
Before you start
Your role needs access to the deployed RF-SMART Bin Putaway function, an active connection and permissions for its NetSuite workflow, and an item available in the displayed putaway list. The selected location and source bin must be available to the mobile workflow. The destination must pass your configured bin rules, normally within the selected location. Check item restrictions, capacity rules, and any lot, serial, status, or unit-conversion requirements in your own setup. The source shows suggested existing bins but says the operator may choose another. Its destination scan is not legible, so STOCK-02 is illustrative only in this recorded example.
Scope: This guide documents the demonstrated RF-SMART mobile interaction. It does not establish which native NetSuite record was created, whether posting completed, or the resulting quantity in either bin.
01 · Open Bin Putaway
On the RF-SMART roles menu, choose Bin Putaway. Use the named entry rather than the adjacent transfer or replenishment functions.
02 · Load items from the receiving bin
Confirm Location: Auckland and From Bin: RECV-AKL. Tap Load Items to list the items waiting in that bin. The screen also offers an Item scan field; this walkthrough uses the loaded list.
03 · Choose the item
Select COFFEE-DRIP-01, the pour-over coffee dripper with 15 EA available. The other item remains on the list; this walkthrough follows only the dripper.
04 · Compare bins and enter quantity
Read the rows below the item. This example shows two bins already holding the dripper, each with a Last Putaway date, Quantity (EA), and Cap. The narrator describes Cap as remaining capacity in this deployment; its calculation may vary in yours. Neither row is a required destination. Enter 15 in Qty and continue.
05 · Enter the destination
At To Bin, scan or enter a destination accepted by your configured rules and review the quantity before submitting. STOCK-02 is illustrative only because the source video's destination value cannot be read. The source explicitly allows a bin outside the two rows shown on the item page.
06 · Read the submitted result
Tap Submit. In the demonstrated RF-SMART screen, the mobile view returns to the receiving list, the coffee dripper is no longer displayed, and a green Bin transfer submitted strip appears. That is the result shown in the recording. There is no NetSuite transaction number, saved native record, or before-and-after bin balance in this walkthrough.
Check the result
- Mobile: Read the green submitted strip and confirm that the selected item left the receiving list.
- NetSuite: If posting proof is needed, find the resulting transaction and match the item, location, source and destination bins, and quantity.
- Inventory: Compare bin-level quantities separately. A mobile confirmation alone does not establish the posted balances.
Common questions
Must I choose one of the two bins shown on the item page?
No. The source narrator calls the rows suggestions and says other bins can be used. Your account may still have its own bin eligibility and capacity rules.
What does Cap mean in this screen?
The source narrator describes it as remaining capacity in this RF-SMART deployment. Do not assume its units, calculation, or enforcement match your installation.
Does “Bin transfer submitted” prove a NetSuite Bin Transfer saved?
It proves the partner mobile screen displayed a submitted result. The recording does not show a saved NetSuite transaction or updated balances. Verify those separately when they matter.
Why does the example use STOCK-02?
The source shows the To Bin prompt and submission, but its destination value is not legible. STOCK-02 is illustrative only in the recording and guide; it is not a transcription of the source scan.
Why did the coffee dripper disappear from the list?
It is absent from the displayed RF-SMART receiving list after submission. That visible list change does not prove a NetSuite transaction posted or bin balances changed.
Source walkthrough
The mobile sequence and screen states are based on an RF-SMART Bin Putaway demonstration. The source ends at the partner submitted message and receiving-list change.