Outbound Overview
  • 3 Minutes to read
  • PDF

Outbound Overview

  • PDF

Outbound Overview

 

 

Picking is the main process that allows inventory to be removed from a warehouse. Pick requests include transactions such as sales orders, site transfers, manufacturing pick requests, and replenishment picks to primary pick locations. These pick requests flow directly to and from your ERP system, CSV import/exports, or API calls.

 

If you are using ERP Integration, Integration runs on a scheduled basis, picking up sales orders that have been added to your ERP, and importing them. Once an order is imported, anyone with access can pick against it.

 

Access to a pick requires:

 

User is authenticated.

 

User has the correct role permissions for picking.

 

User is in the assignment pool either manually assigned, or automatically depending on the configuration settings of your system.

 

If nobody has started picking product against the pick request, and edits are made to it in the ERP system or the pick request is re-imported through CSV or API calls, then integration will update the order for picking as well. Of course, if someone is already picking against it, or the pick request is closed, no updates will be made.  If picking is already in progress, then the pick request must be either partially staged, unpicked, or the pick request must be deleted from the outbound Web Console.

 

 

 

Picking Devices

 

There are two major options for picking and they can be used together or separately to move products around or out of a warehouse. They are listed below with a brief description of their functionality.

 

Web Console

 

Pick Requests & Returns –

This page is the control center for all outbound activities. All the relevant details for an order can be seen here, including customer information, and date information, as well as specific lines on each order. The functionality for filtering, sorting, and grouping orders is very powerful and can be used to manage orders effectively by almost any parameter. This is also the screen where Orders can be assigned to handheld users, so they can be received on their device.

 

 

Manual Order Fulfillment –

 

This allows a Web Console user to pick an order via the web, instead of through a handheld device. This is typically used when there is an issue with handheld picking, or in other special cases, since the user picking is most likely not at a picking staging or shipping location while using this feature. Because of this, only a subset of the full picking features is available when using this method.

 

 

 

iOS or Android Device

 

The iOS or Android devices allow a user in the warehouse to accomplish picking. Scanning is required for picking to occur.   There are four ways to scan barcodes using these devices:

 

Bluetooth integrated Barcode scanners such as Socket Mobile

 

Built-in camera

 

Warehouse purpose-made device such as Zebra and Honeywell 

 

Data is manually keyed in

 

 

 

Picking Flow


The chart above is a general order in which the parts of picking take place in WithoutWire. Below is the basic flow of events in picking, and a basic description of each. Of course, this flow can happen independently for each pick request.

 

The process is flexible in that it allows for stopping and starting at any point. This means that a user can pick half of the product for a line, or half of the lines on a pick request, and exit out of the picking module and come back to it later to finish it up.

 

 

 

Sales Order/Pick Request is Created

 

A pick request can be created in various ways:

 

Import from an external source such as an ERP system.

 

Auto-created based on min/max levels in primary Bin locations, manufacturing locations, or offsite locations.

 

Site transfers generated via intelligent Bin transfers such as with field service techs moving inventory.

 

 

 

Integration Imports Orders/Pick Requests

 

This usually does not require any user interaction in the case of ERP or API integration.  CSV Imports of pick requests are done manually.

 

 

 

Web User Assigns Pick to User

 

Your system is set up to either auto-assign incoming pick requests to all users with picker roles set, or a user with web access can assign pick requests from the Web Console. They then choose a user or users that will be assigned to the order. Unless they are using Manual Order Fulfillment. In that case the order is not assigned and is picked on the Web.

 

 

 

iOS and Android User Picks

 

The assigned user picks against the assigned pick request when the product is ready to be picked for the customer or destination site.

 

 

 

 

Staging the Pick

 

The user may stage order in a designated staging location based on Customer or Route.

 

 

 

Shipping the Order

 

The user may choose to ship the pick request directly from the Web Console.