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.

• 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 from 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 that 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.

• Steps to process this report:

  1. In Eagle Browser, open Inventory Maintenance (IMU).
  2. Type in the SKU and press Enter.
  3. In the Stocking tab, update the Location to match the (Estimated) Corrected Location column in your report.
  4. Press Change (F5).
  5. Repeat these steps for each SKU listed.

  • MULTI-STORE WARNING: If you are multi-store you can only do one store at a time. Select a single store in Excel as you do these steps.

    File Prep (A)

    1. Enable Editing and Enable Content.
    2. Sort out any data you may want to exclude using the column filters. We highly recommend filtering out "Blanks" from Estimated Location (column F).
    3.  MULTI-STORES: you'll need to select 1 store at a time using the filters (column A). Data Import cannot handle all-store data at once.
    4. Click the button in the header called "Export for DI."
    5. The file is automatically prepped as a .txt file and needs to be saved. Save location defaults to the Desktop\MangoFiles...
    6. Close out of Excel.

    Import the Data (B)

    1. Open Eagle Browser.
    2. Locate the folder named Data Import and click on it.
    3. Select Inventory Import Designer.
    4. Under Import File Type select Comma Delimited.
    5. In the top ribbon, select Open (F3).
    6. Select the file you saved in Step A.5 above.
    7. Double check the Import File Type is still Comma Delimited.
    8. In the top ribbon, select Map Field (F6). This is where we'll begin to tell the Eagle system what each column is from the saved file.
    9. Find and select Store (immediate update), click OK.
    10. It will ask what Position. Store was column 1 in our file so enter 1, click OK. We'll repeat this for the remaining columns.
    11. In the top ribbon, select Map Field (F6).
    12. Find and select SKU, click OK. Position 2.
    13. In the top ribbon, select Map Field (F6).
    14. Find and select Location, click OK. Position 3.
    15. Under Import Options, set the Flex Name to LOCEX.
    16. Click on Store for chg and select the store you're working on.
    17. In the top ribbon, click Import.
    18. A new dialog box will appear, click Import.
    19. Once complete the box will pop up, click Cancel and close out of Data Import.

    Finalize Changes (C)

    1. In the Launch bar of Eagle Browser, type RFL and press Enter.
    2. Print Setup -> Print To -> S (spooler).
    3. Options -> Store -> Enter the store you're working on.
    4. Options -> Options -> F (update inventory file).
    5. Options -> Flex Name -> LOCEX.
    6. In the top ribbon, click Run (F4).
    7. You may see a message "No records exist for this flex name." This is okay as things can be automatically finalized for you and doesn't always require the RFL Step.
    8. You may see a message "Do you wish to exit". Click Yes.
    9. Close out of RFL. You're now complete. You can spot check IMU if you would like.

• Steps to process this report:

  1. Select the Products Menu.
  2. In the search box, type a SKU from your report and press Enter.
  3. In the Stock & Sell tab, click the View Location Codes hyperlink (left-hand side).
  4. Update Location 1 to match the (Estimated) Corrected Location column from your report.
  5. Click OK.
  6. Press Save in the upper-right.
  7. Repeat these steps for each SKU listed.

  • File Prep (A)

    1. Enable Editing and Enable Content.
    2. Sort out any data you may want to exclude using the column filters. We highly recommend filtering out "Blanks" from Estimated Location (column F).
    3. Click the button in the header called "Export for DI".
    4. The file is automatically prepped as a .txt file and needs to be saved. Save location defaults to the Desktop\MangoFiles...
    5. Close out of Excel.

    Import the Data (B)

    1. Select the Utilities menu and click Imports.
    2. Under the Import Type column, select Products.
    3. In the upper left, click Start Import.
    4. Select the Upload File icon in the upper left.
    5. Find and select the file you saved in Step A.4 above, and click open.
    6. Under Choose Delimiter, select Comma.
    7. Under Parameters, select Update Records.
    8. Turn the File Contains Headers toggle to off (gray).
    9. Make sure the Mapping Type is set to New Mapping. 
    10. Click Upload.
    11. Select the Data Mapping button in the upper right.
    12. Under the Map to Field column, set Description Map to - blank.
    13. Using the search field above, find Location 1 Name (Primary).
    14. Under the Map to Field column, set Location 1 Name (Primary) Map to - Column 3.
    15. Click Map Data & Proceed.
    16. Click Leave.
    17. Under Data Preview, select Mapped Columns and Verify that each column has the appropriate data.
    18. Click Finalize at the bottom right corner.
    19. A popup will appear; click Finalize again.
    20. Import is underway, click Ok.