1.2.0

Mar 07, 2024

When configuring the model, you can now define the period to optimize prices to daily or monthly (up to now only weekly was possible).

PFPCS-7060

The breakdown chart now considers stores in the scope to define what should be lost business and new business.

PFPCS-7161

Range for stock coverage is defined in Optimization Engine with these values:

• Satisfied range: within +/- 2%

• Acceptable range: within +/- 10% 

PFPCS-7251

The computation of revenue/profit balance now uses the historical values to normalize.

PFPCS-7253

In the Configuration step on the Competition tab, "Current average shelf price difference to competitor" has been added.

PFPCS-7344

The latest version of Optimization Engine (v2) is now used in the Shelf Price accelerator.

PFPCS-7495

Default preferences for layout are now part of the accelerator release.

PFPCS-7605

When installing the accelerator from PlatformManager, engines configuration steps are now the first steps of the accelerator installation. This is to prevent errors when trying to run a model while the accelerator installation has not been completed.

PFPCS-7706

Glassbox logic, used in the Shelf Price Accelerator, is now packaged separately in the Optimization Common Library (OCL) - Glassbox Library and used as such within the accelerator.

PFPCS-7908

Shelf price upper threshold priority was changed to high and some internal value finder's initial settings were adjusted.

PFPCS-7969

Maximization constraints and agents were removed from the description file.

PFPCS-7970

In the Results step, the Influencers tab and charts at the Glassbox tab have been added from Optimization Common Libraries.

PFPCS-7972

In the Results step in the Overview, there is now absolute margin displayed, with the variation in parenthesis, and margin rates for the last and next periods.

PFPCS-7989

Management of quantities below zero has been improved. 

PFPCS-8020

Revenue Breakdown chart last period is based on the latest historical data according to the filter but it should not depend on the filter.

PFPCS-7241

The average competition positioning is not computed correctly.

PFPCS-7341

When a competitor alignment should be defined, the whole list of competitors is displayed (not only the one in scope) and so this is not usable for large competitors lists.

PFPCS-7466

Computation of historical competition positioning is incorrect in the Configuration step matrix. It comes from the use of a total value instead of a unit one.

PFPCS-7491

The competition matrix shows values computed from the sum of the competition prices by store/SKU/competitor from the table (instead of taking the last competition price available).

PFPCS-7673

In the Configuration and Results steps, several UI titles have been improved to provide better guidance to users. Namely, "Competitor" changed to "Competitor positioning (within scope)", "Competitor average gap" changed to "Achieved competitor average gap", "Stock Coverage" changed to "Achieved Stock Coverage" and "Current average difference to competitor (%)" was added.

PFPCS-7755

There is an issue in hierarchy definition, leading to a bad aggregation of the SP/competitor values on which the competitor target is set.

PFPCS-7756

When reaching the Configuration step for the first time (from a non-duplicated model), the checkbox "Use fallback for elasticity" is checked but the next field for entering the number of fallback periods does not appear.

PFPCS-7770

There are issues with dates and aggregation when there is more than one competitor for a product/store.

PFPCS-8033

When deploying the accelerator, deployment of the correct version of Optimization Common Libraries is not triggered.

PFPCS-8039

“Thresholds” and other criteria fields are not adjusted to their new names from OCL.

PFPCS-8049