This exception trap will report SKUs differing only by case.  Although uncommon, stores can inadvertently add multiple SKUs to their inventory file, causing confusion!  A store should determine the primary SKU and consider deleting the offending SKU(s) if there is no sales nor purchase history associated.  Typically, the primary SKU will be the one with the UPC attached.  The example below shows two identical SKUs which only vary by the upper/lower case of the letter C.

Steps to process this Report:

1. Launch Inventory Maintenance (IMU)
2. Determine the duplicate SKU to be deleted
3. Enter the SKU 
4. Verify it is the SKU you wish to delete (usually the one without historical sales, purchases and without a UPC)
5. Delete the SKU by pressing Delete (F10)

Note to multiple stores: you should process these steps only for the Exception Report's store. If the duplicate occurs in other stores then it can be processed from that store's exception report.

This is the trickiest and hardest exception trap to fix. This report is highlighting invalid SKUs where the duplicate SKU has a non-printable character meaning that the SKU in IMU looks exactly the same but if you compare records between the two you'll find they are different.

It is best that you call us and we can work you through it. 734.301.4510

This exception trap will report SKUs differing a zero or the letter O.  Although uncommon, stores can inadvertently add multiple SKUs to their inventory file, causing confusion!  A store should determine the primary SKU and consider deleting the offending SKU(s) if there is no sales nor purchase history associated.  Typically, the primary SKU will be the one with the UPC attached.  

Steps to process this Report:

1. Launch Inventory Maintenance (IMU)
2. Determine the duplicate SKU to be deleted (or if sales exist on both SKUs a RCIN may be needed)
3. Enter the SKU 
4. Verify it is the SKU you wish to delete (usually the one without historical sales, purchases and without a UPC)
5. Delete the SKU by pressing Delete (F10)

Note to multiple stores: you should process these steps only for the Exception Report's store. If the duplicate occurs in other stores then it can be processed from that store's exception report.