Knowledge Base of Inventory Science

Read our comprehensive documentation on how to maximize your WithoutWire.

Explore our Knowledgebase

Expiration Dates and Shelf Life

Overview

Expiration dates provide additional options in managing inventory. WithoutWire supports various formats or parsing of expiration dates, and can be configured under System Maintenance > Configuration Settings. The following formats are:

Standard – MM/DD/YY, MM/DD/YYYY, M/D/YY, M/D/YYYY, MM-DD-YY, MM-DD-YYYY, M-D-YY, M-D-YYYY

Julian Date – A continuous count of days and fractions since Noon Universal Time on January 1, 4713 B.C.

GS1 Date – An application standard that formats dates the following, YYMMDD with a precursor [Note: either (15) or (17)]

Adding Expiration Dates into WithoutWire

  1. WebAPI and CSV imports to support expiration dates (Item and Inventory, Order, PO) are not currently supported.
  2. Base Labels and Reports work needed is not supported for Expiration Dates (at minimum human readable for product labels).
  3. Add to the Delivery Date during picking to find correct product – (Expiration Date > Delivery + Shelf Life)
  4. Lock down of auto-expiration date is not supported.
  5. Expiration Dates for Web Based Receiving.
  6. Manual Order Fulfillment Suggested FEFO.
  7. Field Service task, (Jobs, Manage Parts & Supplies)
  8. Expiration Dates for Kitting and Manufacturing

Expiration Date Tracking in WithoutWire

1) The format that is uniform for expiration dates in WithoutWire is MM/DD/YY.
2) The WithoutWire system assumes 1 expiration date per item/lot combo.
3) If you are configured to use FIFO and an item is expiration date tracked it will truly be FEFO
4) If you are using Primary Pick and an item is expiration date tracked, replenishment will be FEFO driven
5) If WithoutWire is configured for Expiration Dates as Lot Number, then all prompts will show fields as “Lot Number”.
6) Shelf Life support is only available on Rugged Devices.

Configuration Options Available for All Expiration Date Modes

ExpirationDate.AutoCreateViaShelfLife =True or False [rugged only] Used to determine the behavior during receiving process to either auto-generate the expiration date or not. If true, the date is defaulted to today’s date plus shelf life. If shelf life is not set or is 0, then the value is set to today’s date. This allows for situations where shelf life is incorrectly set. An administrator will be able to review these items which will be placed on hold automatically the next day.
If false, the Expiration Date is manually entered by the user. If Expiration Date for the given item has been previously used in inventory, then that value will be defaulted on the screen.

ExpirationDate.MFG.AutoCreateViaShelfLife =True or False [rugged only] Used to determine the behavior when a finished good or WIP item is created. This setting determines whether to auto-generate the expiration date or not. If true, the date is defaulted to today’s date plus shelf life. If shelf life is not set or is 0, then the value is set to today’s date. This allows for situations where shelf life is incorrectly set. An administrator will be able to review these items which will be placed on hold automatically the next day.
If false, the Expiration Date is manually entered by the user. If Expiration Date for the given item has been previously used in inventory, then that value will be defaulted on the screen.

ExpirationDate.IA.AutoCreateViaShelfLife =True or False [rugged only] Used to determine the behavior during a positive inventory adjustment to either auto-generate the expiration date or not. If true, the date is defaulted to today’s date plus shelf life. If shelf life is not set or is 0, then the value is set to today’s date. This allows for situations where shelf life is incorrectly set. An administrator will be able to review these items which will be placed on hold automatically the next day.
If false, the Expiration Date is manually entered by the user. If Expiration Date for the given item has been previously used in inventory, then that value will be defaulted on the screen.

ExpirationDate.AllowEditing = True or False [rugged only] Used to determine whether or not the user can modify an existing inventory item’s expiration date within various sub systems such as inventory adjustments, manufacturing, and receiving.

Force Lot and Expiration Date Picking Limits

Business Objective To create logic in the picking process to validate each lot is under the acceptable time frame for expiration. The Lot Number for all products will be the Manufactured Date(Mfg’s date- identified at point of receipt) Whether a product can be used is determined by Delivery Date, Item Shelf Life Factor, and Manufactured Date. Validation will take place when picking any lot tracked Items. Picking process will always send picker to bin that contains the oldest acceptable lot. Shelf Life Factor will be stored at the item level in WoW. Alter Picking process on the handheld. Add Minimum Acceptable Shelf Life to the Order Detail object calculated using item Shelf Life Factor and Delivery Date. Delivery Day + Item Shelf Life Factor = Minimum Acceptable Sell by Date. Alter database calls to fill new Minimum Acceptable Shelf Life in WoW object. Alter picking code to validate that Lot Number is greater than or equal to Minimum Acceptable Shelf Life. If lot does not meet criteria display message. Modify get next bin process to only retrieve bins with product having acceptable lot numbers. Create a new Shelf Life Factor entry in the WoW Item master. Extend GP Web service call for items to pull Shelf Life Factor. Create an Expired Product web page that shows all product that is less than Shelf Life for item. Item parameter will be a LIKE search. Grid will contain a checkbox column, Allow Select All/Deselect All, Reason Code dropdown list, Button for mass inventory adjustments

Modifications to use this feature:
CASE WHEN i.MinorProductClass = ‘RM’ THEN 1 ELSE 0 END AS BIT LotNumberMustBeDate