Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

It's possible to set a price lock period on offers to control price of the items before promotion starts. Default period is equal to 30 days before promotion starts, but user can provide custom dates. It is possible to add price lock only on promotion price offer.

Image Added
Image Added

Items added to price locked offer are not locked until promotion is approved. When approving promotion with previously setup price locks, warning is displayed, that lock from for price locks will be adjusted to now. Changing promotion valid from date may cause delete of price lock on offer, when promotion is valid from before the locked from date. 

Image Added

Image Added

Price locked offers are visible in 'Items with price lock' grid in read-only mode with possibility to navigate to promotion or offer.

Image Added

If an item has not been added to offer group, due to the fact that it has price lock, the information is displayed over selection of items in the offer. To see more details, user can click View items button, were exact count of items not added to offer is displayed and can be exported to Excel file.

Image Added

Improvement

AreaDescription
Adding item in promotions

Item search (RTC-43529)

User can scroll, add columns or remove them from item search. Modal contains model related columns: 'model number' and 'External model no.'

Items with price lock

Grid improvements (RTC-43198)

Store group reference' column is split into 'store group code' and 'store group name' columns. 'Item text' column is in locked section of the grid. Store related columns in locked section are smaller. Button with delete is not displayed when creating a price lock.

Promotion API

Concurrent request (RTC-43777)

If there is an attempt by the API to modify a resource by multiple requests at the same time, 409 code is visible for the user. A description of this code is in the swagger: '409 - conflict, resource desired to update has been modified by the concurrent request. In such scenario it is advised to fetch the desired resource once again, compare it with the request data and try to update the resource once again'.

Validation for 'validTo' field (RTC-43719)

There is a validation when creating new promotion with ValidFrom to in the past. When such request is sent, ValidFrom remains unchanged and promotion is updated, 200 status code is returned.

...