Location override

Normally, Price Management uses a prioritization logic that prioritizes the lowest location level first when processing price changes. For example, a store-level price change for an item takes priority in the system over a higher location level price change for the same item. The application uses the store's price change for the item.

You can use a point-in-time feature called Location Override to override any current in-effect price regardless of location hierarchy. For example, when location override is applied at a higher location level, any lower level price changes remain active but is not in-effect. After the point-in-time override, Price Management returns to using the prioritization logic and the lower level price change is used.

The Location Override attribute field displays in the Item Information section for any item added to a price change on the Create Price Changes page. The default Location Override value is not set, so it must be selected by a user during price change creation.

Note: Location Override is automatically defaulted to Yes for initial price changes, even if you select No. This allows the system to hold that initial price at the highest location and price priority over any subsequent price changes.

You can use the location override functionality for both regular and temporary price changes. When you use location override on a TPR price change, the application overrides the lower level price change until the TPR's end date. After the TPR is no longer in effect, the application prioritizes the lower level price change.