Picklists itemize all items that are part of open customer orders, while currently in stock and cleared for shipping. Via optimized routes the order picker collects the listed quantity of items from the storage bins using the picklist which is offering information on the bin location, item number, required quantity and further details. In the same work process the employee transports the items to the shipping station, where picked items are allocated to the respective customer orders and shipped thereafter.

Picklists in pixi Web

Check this article to get to know how to use the Picklists section in the pixi Web application.

Picklists in pixi Shipping

Check this article to get to know how to use the Scan-In is done in the Desktop application pixi Shipping.

Note: The Picklists functionality in pixi Shipping is not developed further.
New features will only be available in the Picklists section of pixi Web application.

Configuration

pixi Control Center settings

Picklist - Show Bins from all locations

If this function is activated, all storage bins of all locations can be selected in the picklist parameters. If this function is deactivated, only the storage bins of the selected location are displayed for selection (default setting).

Picklist - Item Number Column value

Select the item number displayed in the picklist: Barcode, supplier item number or shop item number (ItemNrInt).

Picklist - Include Orders with FUT Orderlines (waiting for fulfillment)

If this setting is activated, orders that also contain orderlines in the FUT status are taken into account when generating a picklist. However, only the orderlines of the purchase order, which are in the ANG (order accepted) status, actually appear on the pick list. If this setting is disabled, all orders with orderlines in the FUT status are excluded from the picklist generation. Default value: OFF.

Picklist - Default expiration time

Picklist validity expressed in hours - default standard is 12 hours.

Picklist - Prioritize Smaller Qty Bins

Normally pixi takes storage bins into account by their order when creating the pick lists. By activating this option, storage bins are preferred, which store a smaller number of items in order to empty storage space as quickly as possible.

Picklist - Overlapping boxes

Usually, there can only be one picklist per box range. By activating this function picklists can overlap. Pay attention! Use this setting with the required care, errors can occur.

Picklist - FiFo per Location

See Prioritise Reserved Orders

Picklist - Ignore unshippable Orders for X Min.

With this setting you can define the period (in minutes!) in which unshippable, not reserved orders should be excluded from picklist creation if the same picklist profile is executed multiple times.

The setting only then takes effect, if the same picklist profile is executed several times. The first picklist creation will take more time than the following picklist creations. When creating the first picklist, all orders are considered. Not reserved, unshippable orders get marked and are excluded from picklist creation for the next X minutes. This accelerates picklist creation.

Warning: If items get put to stock in between, which makes some orders shippable, they are ignored until the time span set in this setting is over.
Orders that get shippable with putting items to stock are also considered for picklists.

If a picklist gets created manually (without profile) or a profile gets changed before picklist creation, orders are NOT ignored.

Example

Below, there is an example of how the picklist creation is affected by this setting.

• The database setting Picklist - Ignore unshippable Orders for X Min. is set to 30.
  This means that not shippable, not reserved orders are ignored for the next 30 minutes if they have been checked once.

• The picklist profile used for this example is called UPS, all orders.
  It contains all orders that have UPS set as shipping vendor. In our case, all orders listed below will be considered when the picklist profile is executed because all of them have UPS assigned as shipping vendor.

• There is no reservation on any order.

Orders in pixi:

1st execution of the UPS, all orders profile at 9:00 am:

1. Check order nr. 154: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

2. Check order nr. 246: shippable; put to picklist

3. Check order nr. 251: shippable; put to picklist

4. Check order nr. 339: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

5. Check order nr. 518: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

6. Check order nr. 686: shippable; put to picklist

In the end, the picklist creation checked 6 orders and put 3 of them to the picklist.

After the picklist was created, some new orders were imported into pixi:

2nd execution of the UPS, all orders profile at 9:20 am:
(Since the same picklist profile is executed again, orders that have been put to the list of orders to be excluded from picklist creation are ignored.)

1. No need to check order nr. 154

2. No need to check order nr. 339

3. No need to check order nr. 518

4. Check order nr. 774: shippable; put to picklist

5. Check order nr. 801: shippable; put to picklist

6. Check order nr. 812: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

So, out of 6 orders that should be checked, pixi skipped 3 of them because they were marked to be ignored.
From the remaining 3 orders 2 were put to the picklist and 1 was again marked to ignore it for the next 30 minutes.
Because of this, the time needed for creating the picklist is less than if pixi would need to check all 6 orders.

Again some new orders have been imported:

3rd execution of the UPS, all orders profile at 9:40 am:
(Since the same picklist profile is executed again, orders that have been put to the list of orders to be excluded from picklist creation are ignored.)

1. Check order nr. 154: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

2. Check order nr. 339: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

3. Check order nr. 518: not shippable; added to the list of orders to be excluded from picklist creation for the next 30 minutes

4. No need to check order nr. 812

5. Check order nr. 965: shippable; put to picklist

6. Check order nr. 1024: shippable; put to picklist

Since 30 minutes have passed since the 1st execution of the profile, order nr. 154, 339 and 518 need to be checked again. Order nr. 812 does not need to be checked, because it is ignored until 09:50 am (09:20 am + 30 minutes).
So, pixi checked 5 out of 6 orders and put 2 of them to the picklist.

Reservation function for picklist generation

The optional reservation function coming with pixi assures the customer that ordered items have been reserved. Order bookings follow the "FIFO" principle (First-In-First-Out) according to your reservation date.
See also: Reserving stock for customer orders

Using the database setting Picklist - FiFo by Location (pixi Control Center > Database settings tab > Folder Shipping), you can manipulate the order sequence when shipping customer orders. (Available from pixi LOU Update 28 and AVA Update 4)

If this option is set to OFF, the customers orders are shipped according to reservations across locations.

Example:

An item is part of 5 customer orders and available in two locations with varying order quantity. All orders have been reserved based on the order date. The item in question shows a quantity of 5 in location 001 and a quantity of 60 in location 002.

If a picklist is generated using location 001, then the available quantity of this location is being matched with all open orders according to the FiFo-Principle. Thereafter orders from other locations are removed:

So the last order at location 001 is not being processed as only the inventory of the current location is taken into account. This is based on the assumption that inventory at location 001 needs to be used to refill location 002 in case of insufficient inventory to process 002-orders according to th higher priority (earlier order date). Order 123460 can only then be shipped, when all previously reserved orders at location 002 have been processed for shipping first (123458 und 123459).

If this option is set to ON, all customer orders are processed for shipping at the current location according to sequence of reservation time; reservations from other locations are not taken into account.

Example:

Same scenario as above.

If a picklist is generated for location 001, all orders from other locations are removed right away and inventory is distributed between open customer orders according to the FiFo-Principle:

All 001-orders are processed for shipping.

Important notes:
- Always use the picklist parameter "Pick from current location" - otherwise storage bins of other location(s) are being used for reservations and thus stock is diminished for the orders at these locations.
- The display of available inventory (Res.) in pixi Customer Service still refers to the global sequence of reservation. Hence you will have to look up the Item Info in the Reservations tab to check in individual cases, if an item is indeed available or not. From pixi AVA Update 4 the inventory, according to the setting "Picklist - FiFo per location", is displayed in column "Available stock (orderline)".

Back to top