Product Table Configuration - Price Drop

[SAPSupport]

Today, our product table includes localized fields so that the product price is displayed according to the location registered in the customer's profile. There are two fields for each region: MSRP and PRICE.

MSRP: This field is filled with the current price of the product.
PRICE: This field is filled with the promotional price, if there is a promotion.

For the price drop campaigns to work correctly, is this the correct configuration? Or do we need to replicate the prices to the PRICE field? I am attaching our current product table so that you can check how the fields are being filled in.

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

You will need to maintain both the price and msrp fields for each region.

By default, product data in price drop campaigns is retrieved from the standard price fields in your product catalog. When you have other product localization regions, the option to select the localization to be used on the specific Price Drop trigger that you are setting up will be shown. This means that you will need to create one trigger for each region.

The fields included in the event data (i.e. title, (old_price), price, image, link, msrp) will also use the selected localization. Currently, this only applies to campaigns containing ESL blocks directly referring to the event payload that is coming through Interactions (External Event personalization).
 
So, if you don't use the ESL blocks directly to the event payload that is coming through interactions, you don't need to worry about it.
 
Just for your information:
https://help.emarsys.com/hc/en-us/articles/360007147957-Overview-Product-catalog-updates-trigger-FAQ
 

Questions about fields - Which fields can I use in my content blocks?

You can use the following fields within placeholders in price drop and back in stock campaigns:

• Price drop: old_price, new_price, title, image_url, link, msrp
• Back in stock: new_price, title, image_url, link, msrp

What do the fields old_price and new_price refer to?

The fields old_price and new_price are generated by Emarsys, these are not part of your product catalog.

• old_price: The product’s original price before it has dropped.
• new_price: The product’s price after it has dropped.

 
The price drop use case uses the old_price fields. The old_price is the price the product had at the previous program run. For example, if you want to display the previous price the product had in order for the contacts to see the difference in the price clearly.
 
You can refer to the following documentations for further clarification:
Product Catalog Updates - Price drop
Product Catalog Updates - Low in stock