Outbound Console on the Web Console
The Pick Requests & Returns page is the control center for the picking process. It allows users to manage all order types (i.e., sales, transfers, jobs, manufacturing picks, etc.). After new pick requests are brought in either from the ERP systems, API calls, or CSV import/export, a user can see that orders and other pick requests are imported correctly by examining the Pick Requests & Returns page. This page will also show Cross-Site Moves and Consumption records.
The Outbound Console allows a user to see many pieces of information related to pick requests. Below is a list of attributes that can be seen, as well as a brief description of each.
The Unique Number (can include digits and text) used as identification for sales orders or pick requests.
Parent Order Number
If an order is waved together with other orders, this column will notate the Waveset that was used to batch pick the child order.
Notes the priority in which this order should be picked. This is a visual indicator to help identify orders for assignment to pickers.
Customer PO Number
The PO Number the customer will use when they request a sales order/pick request. This number can also be used for other reference numbers such as field service jobs or ASN imports.
The Type of pick request that will be picked. Example: Sales; Transfer; Return; Credit.
The Status used to determine if the sales order has been completed yet. See pick request status below.
The customer name, field tech, or warehouse associated with the pick request.
Represents the “Ship To” City.
Represents the “Ship To” State.
The Route number that is assigned to the pick request.
The total weight of the expected product on the pick request.
The date the pick request was loaded into the WithoutWire system.
The percentage of product on the pick request that has been picked so far.
The date/time that the pick request final documents were printed.
The date/time the pick request was exported back to the ERP or exported via API or CSV.
The expected delivery date of the pick request to the customer, manufacturing location, field tech, or warehouse site.
Indicates which method will be used when shipping (Same Day, Overnight, Freight, etc.)
This is a link that takes you to a separate page for each pick request. It has a list of the line items and their quantities. See pick request details below.
Pick Request Status
Each sales order/pick request is given a status field to allow progress on an order to be tracked. When a pick request is imported, it is assigned a status of “Unassigned.” If Auto Assign Orders is configured, then the picks will be assigned to users automatically, and the status of the pick request will be set to “Waiting to be Picked.”
Below is a list of the pick request statuses, and what they are used for.
Cubing, route planning, or containerization (if applicable) has not taken place.
This order is a child order that is pending Waveset pick completion.
This state is the only state that allows picks to be assigned to users. This state will be bypassed if Auto Assign Orders is on.
Waiting to be Picked
Order is on a user's device but is not actively being picked.
Picking in Progress
Once a user opens a pick request on the handheld and begins to Pick product, the Pick Request will change to this status. If the user makes no changes to the Pick Request, the status will not be changed and should be put back to Waiting to be Picked.
Waiting for Export
Order has been completed in WithoutWire and is pending export to an external system.
Waiting for Shipment
Once a Pick Request is picked to completion (could be shorted as well) and staged on the handheld, the Pick Request will change to this status.
Typically used for ERP integration to indicate that the pick request is in the process of updating ERP transactional records.
The pick request is completed.
The pick request is being processed for cubing, route planning, or containerization (if applicable).
Order has been deleted and will be reimported when the next integration cycle is complete.
Filtering Pick Requests
The Order Console allows users to filter pick requests based on a variety of factors. This allows a manager to easily see which picks were completed around a certain time, which picks have yet to be completed, and many other user-defined categories. Below is a list of all the details that can be used to filter pick requests.
Used to filter the Outbound Console by a date range against the Scheduled Delivery Date. This is controlled by a “Begin” delivery date and an “End” end date. Users can set either or both to only show orders before a certain date, after a certain date, or between two dates. WithoutWire has built-in calendars that can be used to visually choose a date, which can be accessed by clicking on the calendar icon next to each field.
Route (Pick Request Group)
Filter by a certain route or group. Use the dropdown box to show only one pick request group at a time. Routes can be edited by the System Maintenance/Route Maintenance.
Users can select a status to view to help gauge the number of pick requests left in each status.
If “Unassigned” is selected as the status to filter by, a user can choose which of these pick requests to assign right from the Order Console, without having to navigate to the Picking Assignments Page. Just check the box next to each pick to assign and click on the Assign button at the bottom of the page.
Users can enter text to search by as well. The text entered can be searched by one of the following. All pick requests which contain the text in the chosen field will be selected. This allows for a user to filter by all orders that start with “ORD86” or to find all POs with the item “BNL90456.”
The following can be used with text filters:
Customer PO Number
The Outbound Console allows the user to remove any unwanted information from the display grid. This can be done by selecting which columns to see when the console is filtered. Click on Select Columns to bring up a list of columns. Check the box next to a column to add it or remove it from view.
The Outbound Console allows the user to execute four different actions from within the console itself. The user can Assign Orders, Set Routes, Plan Wave Sets, and Ship orders from the console. When the user filters on “Unassigned” orders they should see three columns appear in the console. The first column can be used to select one or multiple orders and assign them to pickers. The second column will allow the user to select one or multiple orders and assign them to a specific route. The third column will allow the user to select one or multiple orders and create a wave set order to be picked. If the user filters by orders that are “Waiting to be Picked” they will only see the first two columns. When the user filters on “Picking in Progress” they will only see the first column. To execute the final action the user would filter on the “Waiting for Shipment” status. This would allow the user to select one or multiple orders and process their shipment from the system.
The Outbound Console allows users to view additional information on a separate page for each pick request by clicking the Details link in the View column of the console. The Details page contains a list of the line items and the quantities that have been ordered and picked, along with time and date stamps signifying when the user begins and finished picking each item.
From this screen the user may also do the following:
Edit the Route Number
Edit the Stop Number
Add a Tracking Number
Edit the Delivery Date
View Pick Tickets
View Final Docs
Print BOL (Bill of Lading)
Add Seal Number
Add Truck Number
Delete and Re-Import (if ERP integrated) –
This allows the user to delete the pick request and if your system is ERP integrated, then the pick request will be re-imported. If you are using CSV Import/Export or API, then you control whether the pick request is re-imported or not.
Delete W/O Re-Import (if ERP integrated) –
This allows the user to delete the pick request and set the pick request to NOT reimport from the ERP system.
Close Without Export –
This allows the user to close the pick request without exporting it back to the ERP, exported to a CSV file, or calling the API to export the pick request.
This will split the item into another singular order to pick. This is helpful with large orders that require multiple pickers.