Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: An individual item, an inner pack and shipping cartons show different units of measure.
Six cartons arrive at a warehouse. The operator scans the item and enters a quantity of six. Later, a supervisor sees an unexpected inventory balance. Were six cartons received, six individual units recorded, or six cartons captured in a task that still awaits receipt posting?
Those are different questions. NetSuite WMS connects physical warehouse activity with system records, but the connection depends on the configured process, units, inventory detail and completion stage.
This lesson follows a receiving example from the dock to the resulting inventory evidence. The goal is to help operators and supervisors explain what happened without repeating a receipt or creating an adjustment before understanding the original transaction.
NetSuite WMS extends warehouse processing through mobile workflows for receiving, storage, picking and shipping. The Warehouse Management feature is available in accounts using Advanced Inventory Management. Required SuiteApps, system rules, mobile setup and permissions must also be in place.
WMS is not the same experience as the general NetSuite mobile application. Instructions for mobile expenses or ordinary record viewing do not describe warehouse receiving.
The exact workflow depends on the location, item and configured rules. A warehouse using bins can have a different process from one configured without bins. Lot numbers, serial numbers, inventory status and receipt-posting options can introduce additional steps.
Before training, identify the specific process name, warehouse location, expected source order and intended operator role. Confirm that the device and scanning setup are approved for that process. Do not assume offline operation or compatibility with a particular scanner simply because a demonstration used one.
A useful task statement connects the physical event with the system evidence: “Receive the delivered quantity against this approved purchase order and verify its item receipt.”
This is more precise than “Scan the delivery.” Scanning may identify an order, item, quantity, serial number or bin at different points in a workflow. The sound or visual confirmation from one scan does not explain every downstream consequence.
For receiving, the source might be a purchase order, transfer order or return authorization, depending on why the goods arrived. Confirm that the order is eligible, approved where required and associated with the warehouse location selected in the app.
If the order is unavailable, investigate its status and location before creating a new one. An order intended for another warehouse or already fully received is a different problem from a failed scan.
The purchasing lesson explains why the order, receipt and vendor bill are separate records. A physical receipt also does not prove that the supplier invoice has been reviewed or paid.
Start with item identity. Compare the scan’s result with the expected item and the physical label. Where aliases or different packaging barcodes are used, confirm what the barcode represents in the configured process.
Next check quantity and unit together. “Six” without a unit is incomplete information. A purchasing unit, stocking unit and package label can represent different quantities of the same item.
For items with multiple units, the WMS receiving flow supports reviewing and selecting the relevant unit and viewing conversion information. Check the unit whenever the quantity is entered or changed. Do not assume that scanning a carton label universally sets a carton unit or increments by a full carton.
Then check the location and any required detail. In a bin-enabled process, confirm the intended destination bin. For applicable items and features, verify lot, serial or inventory-status information. A correct total quantity can still be recorded in the wrong place or with the wrong detail.
This fictional exercise assumes an item with a verified configuration of four individual units per carton. The delivery contains six complete cartons, and the approved receiving process uses that carton unit. These are teaching assumptions, not a default NetSuite conversion.
The expected physical quantity is six multiplied by four, or 24 individual units. The operator checks the purchase order, item and selected unit before confirming the quantity in the permitted test process.
If the screen expects individual units, entering six would represent six units under that setup. If the screen expects cartons with the stated conversion, six represents 24 units. The numerical entry cannot be interpreted without the unit.
After completion and the required receipt posting, the supervisor finds the resulting item receipt and checks its quantity and unit basis. They confirm the source order and inventory detail, then compare the relevant inventory position.
In an isolated teaching example with an opening on-hand quantity of 100 units and no other movements, a correctly posted receipt of 24 units would produce 124 on hand. A live warehouse may have concurrent picks, receipts, transfers or adjustments, so a raw before-and-after balance alone may not isolate the effect of this receipt.
Keep the example’s on-hand quantity separate from availability. Inventory status, commitments and other configuration can affect what the business can use or promise. The inventory quantities lesson explains on hand, committed and available quantities.
WMS receiving can use automatic receipt generation or configured manual or deferred posting. This means the visible end of a scanning sequence is not a universal guarantee that the item receipt has already posted.
An item receipt links the received goods to the appropriate source order. When posted, it records the receipt and updates the relevant stock information. Establish that record’s existence and status rather than relying solely on an operator’s recollection of a confirmation message.
For your warehouse, agree what evidence constitutes completion. It may include the finished mobile process, the resulting item receipt and an updated received quantity on the source order. The exact sequence should be documented for the configured receipt-posting method.
This distinction is especially useful when an operator reports, “It scanned, but the stock did not change.” The next question is whether the transaction was fully processed and posted, not whether the delivery should be scanned again.
When a result is uncertain, record the source order, item, entered quantity and unit, location, approximate time and operator context. Preserve any error or completion message without exposing unrelated information.
Have an authorized supervisor inspect the process status and related item receipts. Look for evidence that the goods were already recorded. Confirm whether another operator or background process is still handling the same work.
If the receipt exists, compare it with the actual delivery. Do not repeat the receipt to make a dashboard refresh. If the receipt is absent, establish whether the configured process is awaiting posting, encountered an error or never completed.
Only then choose the approved recovery route. The route may involve finishing a pending process or correcting a specific error. If a posted transaction is wrong, use the supported correction process with the appropriate approval instead of creating an unrelated inventory adjustment to conceal the discrepancy.
For a physical count disagreement, the inventory-count snapshot lesson explains another important boundary: a count comparison needs a defined inventory position and controlled variance review.
The same evidence discipline applies when goods leave the warehouse. Identify the task being performed and the transaction or status expected from it.
Picking, packing and shipping describe different physical stages. Their configured system effects also need to be understood. A picked quantity does not automatically prove that the carrier has the goods, and a shipping label alone does not establish the final inventory or fulfillment status.
Warehouse configurations can combine WMS with other supported packing and shipping capabilities. Use the approved design for the account rather than mixing instructions from different processes. A supervisor should know which application and step owns each update.
When the customer asks where an order is, trace the relevant fulfillment and shipment evidence. Avoid using a convenient warehouse screen as proof of a later event it does not record.
If the task is missing, check the operator’s role, process access, selected location and the source order’s eligibility. The administrator can review the relevant WMS permissions without giving the operator unrestricted access.
If the scan identifies the wrong item, inspect the barcode or alias configuration and the physical label. Do not keep entering quantities against a disputed identity.
If the quantity is wrong, compare the entered unit, conversion and package contents. Check whether partial cartons or mixed packaging invalidate the assumed conversion.
If the right quantity appears in the wrong bin or status, inspect inventory detail and the configured receiving or putaway flow.
If inventory seems unchanged, confirm posting and compare the correct item and location scope. Then investigate concurrent movements or display timing with the relevant owner.
For role-based exercises that connect scans with their system consequences, explore CuriousRubik NetSuite training and adoption. A strong exercise finishes when the operator can explain the resulting record, not merely repeat the scanning sequence.