This report is tucked in the back of your Count Sheets because it's best processed on the sales rather than in the back office. There is a full SKU listing in your MEGA Report. This report assumes your store generally follows Mango's Recommended Location Code scheme.

There are several Location Code Exception traps contained within this report. The column Error Type will indicate the trap type explained below. The Estimated Corrected Location column attempts to show the most likely location code for the product in your store. Generally, it will suggest the most common location in your store for the SKU's Product Group. 

You can find a full, multi-store listing in the MEGA Report located in your Data Import directory. Steps to download your report can be found here.

Exception Traps:

1) ‘oh’, not zero trap

This trap looks for an O (letter "O") in place of a 0 (zero) in the location code. This is a common mistake that keeps SKUs with these errant locations form sorting and filtering as expected. For stores with first-digit numeric RSO filters, a leading “oh” will prevent SKUs from showing up on your order! The trap will also look for the “)” (right parenthesis), which is the shift-zero key which is another common error.
Note: for obvious reasons, it is a bad practice to incorporate location code schemes with the letter O.  

2) Lowercase trap

Case matters in your location code schemes.  For example, a location of 01R10 will not filter or sort the same as 01r10.  Here Mango will look for lowercase location codes and suggest the uppercase replacement. 

3) Single Location

Mango will display SKUs having unique locations in your store.  That is, there is no other SKU with a location code matching the listed SKU.  A lot of times this will pick up SKUs with errant locations and sometimes this will pick up on SKUs where the unique location code is desired.  We continue to put additional intelligence into this section to reduce false-positive reporting (where there is a desired unique location).  Some stores will location code individual bins (a store’s plumbing brass rack for example) to make locating product easy in SKU-dense sections.  

4) Blank Location

Most stores are very location code sensitive and a SKU with a blank location code is against policy.

5) NEW Persistent

If a SKU has a NEW location code for over 3 months, it will be listed here. These SKUs are newly added but have not yet been assigned a proper location code.
 

6) All Numeric

For stores utilizing non-numeric location codes, a common mistake when locating entire sections is to accidentally scan a SKU for in the sticky location code and errantly locate the entire section with a numeric partial SKU. This trap will pull these SKUs out and list them here.

7)  Closed Out

This trap seeks out SKUs which have been closed out (Store Closeout flag set to "Y") and have a quantity-on-hand (QOH) of zero.  Although these SKUs have been successfully closed out, they still maintain an active location and may exhibit a persistent empty hook/bin condition.  Note: active codes start with a numeral (0 - 9) where inactive codes generally start with an alpha character (DR, ZZ, etc.). 

Most stores change a closed-out SKU's Location Code to DRXX where XX is the year of the SKU's closeout.  For example, if SKU 1404540 is closed out in 2019, it's Location Code would be DR19.  Before the location is changed, it should be physically checked to make sure the bin tag is removed from the shelf.

​