An expected receipt is any electronic transaction that contains information about items, quantities, and potentially containers, that is used to facilitate the receiving process at a warehouse. It is typically one of the following transactions:
- Purchase Order
- Transfer Order
- Return Authorization
- Advanced Shipping Notice (Inbound)
Inbound ASN (Advanced Shipping Notice)¶
A custom NetSuite transaction, unique to SuiteWM, that defines a specific shipment created by a vendor to be received at the warehouse. This shipment may span multiple Purchase Orders. If utilized, SuiteWM will maintain a perpetual view of all open Inbound ASNs locally. If a receipt is processed at the warehouse against a Inbound ASN , SuiteWM will create an Item Receipt(s) in NetSuite against each applicable Purchase Order to reflect the inventory received at the warehouse.
A NetSuite transaction created for a Customer to purchase goods or services from the company. SuiteWM will maintain a perpetual view of all open Sales Orders locally for attribute reference purposes (names., addresses, shipping terms, etc.).
Fulfillment Order or Item Fulfillment¶
A NetSuite transaction to created to reflect a specific shipment against a Sales Order based on inventory commitments on that Sales Order. One or many a Fulfillment Orders will be created against a Sales Order. A Fulfillment Order is only created for a single warehouse. SuiteWM will maintain a perpetual view of all open Fulfillment Orders locally and process them to allocate (at bin level), pick, pack, and ship. Once a Fulfillment Order has shipped, SuiteWM will update NetSuite with the shipment?s tracking numbers, weight, and charges (if applicable).
A NetSuite transaction to change the quantity of inventory “on hand”. SuiteWM will initiate and create ALL inventory adjustments since bin-level inventory is only being maintained within SuiteWM.
A NetSuite transaction to transfer a quantity of inventory from one Location to another. This is also used to change the Status of inventory within NetSuite since different Statuses are reflected using different Locations in NetSuite. SuiteWM will initiate and create ALL inventory transfers relating to inventory Status changes since bin-level inventory is only being maintained within SuiteWM. Transfers between different physical sites may be initiated through NetSuite using a Transfer Order (which will create a Fulfillment Order and Purchase Order for SuiteWM to process).
A NetSuite transaction to request the transfer of inventory from one Physical Location to another. This is typically used to ship inventory from one physical location to another using standard shipping and receiving functionality of NetSuite and SuiteWM. SuiteWM will retrieve the Fulfillment Order (created by the user) for the location shipping the inventory, and automatically create a Purchase Order for the expected receipt of this inventory at the receiving location. Both transactions are processed by SuiteWM against the Transfer Order.
Periodically SuiteWM will retrieve the balance on hand (BOH) for every inventory item in NetSuite and compare that BOH with the same in SuiteWM. Any variances will be alerted via a standard email/report.
Master Data Transactions¶
Periodically SuiteWM will retrieve all relevant attributes of each item defined in NetSuite that can be received or shipped at the warehouse.
Kit or Bill of Materials (BOM) Master¶
Periodically SuiteWM will retrieve all relevant attributes of each kit defined in NetSuite that can be received or shipped at the warehouse.
Rules (and List of Values)¶
Periodically SuiteWM will retrieve all relevant custom rules persisted within NetSuite and used by SuiteWM.
Custom Tables in NetSuite¶
This custom table will be maintained by SuiteWM to represent the “inventory by bin” view of all warehouse inventory. It is synchronized from a real time view of this same data maintained in SuiteWM. This data can be exposed on any form relating to Items in NetSuite.
This custom table will be maintained by SuiteWM to represent the “activity” view of all warehouse “moves” of inventory. It is synchronized from a real time view of this same data maintained in SuiteWM.
This custom table will be maintained in NetSuite to represent the employees, authentication credentials, and roles defined for SuiteWM. SuiteWM will access this data in real time to authenticate all users attempting at access the SuiteWM application
This custom table will be maintained in NetSuite to represent the all Bin Locations and attributes for each warehouse. SuiteWM will periodically synchronize this data locally.
This custom table will be maintained in NetSuite to represent an entension of Ship Method NetSuite shipping attribute to deal with shipping concepts that are not native to NetSuite but frequently required by a warehouse (or an EDI document). These include SCAC, Service Level, Mode or Transport, Freight Terms, Third Party Billing, and Accessorials. SuiteWM will periodically access this data in real time.
The relocation of inventory from an inbound staging location or fixture to a defined Bin location that has been selected based upon system settings, item attributes and bin availability
A process to evaluate a set of Fulfillment Orders and determine the best way to organize and group these orders so that they can be fulfilled in the warehouse most efficiently.
An distinct ID, typically barcoded on a label, used to represent specific collection of Inventory Item(s) and quantity(s) to be moved or stored in the warehouse.
Picking Strategy: Order Pick¶
Warehouse operator will travel through the warehouse via a bin sequence with a single pre-defined container to pick a single Fulfillment Order.
Picking Strategy : Batch Pick¶
Warehouse operator will travel through the warehouse via a bin sequence with a single pre-defined container to pick a set of Fulfillment Orders that all have the exact same characteristics (same Items and Pack Destinations)
Picking Strategy: Cluster Pick¶
Warehouse operator will travel through the warehouse via a bin sequence with a set of pre-defined containers to pick a corresponding set of Fulfillment Orders, one order per container.
Picking Strategy: Super Batch Pick¶
Warehouse operator will travel through the warehouse via a bin sequence with a set of pre-defined containers to pick a corresponding set of Batch of common Fulfillment Orders, one Batch per container (see Batch Pick method).
Picking Strategy: Consolidation Pick¶
Warehouse operator will travel through the warehouse via a bin sequence with a single pre-defined container to pick a multiple Fulfillment Orders that have all been assigned to a single consolidated shipment.
Batch Quantity Threshold¶
A limit that is used as one factor in the decision to Batch Pick or Super Batch Pick common Fulfillment Orders. For example, If a group of common orders does not meet a Batch Quantity Threshold, the Picking Method will be defined as a Super Batch Pick, rather than a Batch Pick.
PKit (Physical Kit)¶
A collection of Items that must be physically grouped ad packaged together prior to shipment of the Fulfillment Order. These items will be defined as Kit Items in NetSuite and “exploded” by SuiteWM on the Fulfillment Order.
VKit (Virtual Kit)¶
A collection of Items that must be picked for a Fulfillment Order but does not need to be physically packaged together prior to shipment. These items will be defined as Group Items in NetSuite and “exploded” by SuiteWM on the Fulfillment Order.
Fulfillment Order Profiles (Units, Lines, Affinity)¶
- Single-Item/Line Single Quantity
Common Fulfillments would be typically be Batch or Super Batch Picked based on unit quantity and threshold settings.
- Multi-Line Single-Quantity
Common Fulfillments would typically be Batch or Super Batch Picked based on unit quantity, order affinity, and threshold settings.
- Single-Line Multi-Quantity
Frequently a Cluster Pick and grouped to minimize travel.
- Multi-Line Multi-Quantity
Always a Cluster Pick unless order volume dictates an Order Pick. Grouped to minimize travel.
Identify and release one or many fulfillments that will be analyzed together when performing Wave Processing
Allocating, analyzing, batching, optionally printing, and preparing fulfillments for picking availability
Monitoring the status of fulfillment orders in suspense, being picked, packed, and/or shipped
The SuiteWM process of verifying the quantity of inventory in a single container which may contain inventory for a single Fulfillment Order (if an Order or Cluster Pick),or multiple Fulfillment Orders (if a Batch or Super Batch Pick). Once Packed, each Fulfillment Order can then be Shipped.
The process of selecting the most cost effective carrier and service level based on level of service requested by the customer. Once all containers are manifested, SuiteWM will post this data within NetSuite on the Fulfillment order (Packages Tab) as well as to the SPS Commerce Packages custom tables (if enabled in the NetSuite environment) to support the generation of EDI 856 documents out of NetSuite.
The SuiteWM process of verifying the quantity and status of inventory located in a specific bin. Counts can be “Accepted” or “Recounted” within SuiteWM. If “Accepted”, an Inventory Adjustment will be posted within NetSuite to reflect the variance detected by the count. If a Recount is requested, a operator will be requested to recount that specific Item/Bin combination.