ROP Protect Exceptions

The purpose of this report is to show SKUs whose Order Points are Protected, creating in-stock issues, or have mismatches with Min or Max Order Points. 

    • If a SKU's ROP Protect flag is switched to "Y" then it is excluded from Eagle's order point calculation engine. When this happens, the SKU's order point is manually maintained via the Order Point field in the Stocking tab of Inventory Maintenance.

      ROP Protect = Y should be used sparingly as the SKU's order point will no longer align with customer demand, and in some cases, will cause a SKU to run out of stock or become incompatible with a Min Order Point or Max Order Point setting.

      ROP_Protect_Y.png

    ​Types of ROP Protect Exceptions 

    • Blocking EOQ - the protected Order Point is keeping the SKU from being managed via Mango's EOQ (Min/Max) engine. 
    • Blocking MOP/Blocking Sugg MOP - the SKU's Min OP is greater than (or should be greater than) the SKU's protected Order Point.
    • Blocking Reduction - the protected Order Point is blocking the SKU's minimum order point from being managed downward.
    • ROP Too High - the SKU has an Order Point protected too high based on SKU sales. 
    • Locking OP to Zero - the SKU has an Order Point protected at zero and cannot be replenished via the regular RSO/MPO process.

    Steps to process this report:
    In most cases, setting ROP Protect to "N" in the Codes tab of Inventory Maintenance will resolve the issue. 

    Note: if the SKU is protected to a zero order point and you do not want to reorder the SKU then set the SKU's Store Closeout flag to "Y" in the Codes Tab of Inventory Maintenance. This is the preferred way of indicating a SKU is no longer part of your store assortment.  Make sure you have updated the SKU's location code to your store's dropped code, and ensure the bin tag is removed from the shelf.

    • If a SKU's Order Point Protected toggle is on (green), then it is excluded from Propello's order point calculation engine. When this happens, the SKU's order point is manually maintained via the Buying tab of Products.

      The Order Point Protected toggle should be used sparingly as the SKU's order point will no longer align with customer demand, and in some cases, will cause a SKU to run out of stock or become incompatible with a Min Order Point or Max Order Point setting.

      Propello Order Point Protected.png

    ​Types of ROP Protect Exceptions 

    • Blocking EOQ - the protected Order Point is keeping the SKU from being managed via Mango's EOQ (Min/Max) engine. 
    • Blocking MOP/Blocking Sugg MOP - the SKU's Min OP is greater than (or should be greater than) the SKU's protected Order Point.
    • Blocking Reduction - the protected Order Point is blocking the SKU's minimum order point from being managed downward.
    • ROP Too High - the SKU has an Order Point protected too high based on SKU sales. 
    • Locking OP to Zero - the SKU has an Order Point protected at zero and cannot be replenished via the regular RSO/MPO process.

    Steps to process this report:
    In most cases, setting the Order Point Protected toggle to off (gray) in the Buying tab of Products will resolve the issue. 

    Note: if the SKU is protected to a zero order point and you do not want to reorder the SKU then set the SKU's Store Closeout flag to "Yes" in the Stock & Sell Tab of Products. This is the preferred way of indicating a SKU is no longer part of your store assortment.  Make sure you have updated the SKU's location code to your store's dropped code, and ensure the bin tag is removed from the shelf.