Price diff in the online channel

Price for a product is defined in Dynamics 365 for Operations or in Dynamics AX 2012 R3 for a released product and available in all channels where the assortment and catalogs are including the product. The price is calculated by the Dynamics Retail Server or the Commerce Runtime when a product is added to a cart or when a product is displayed on a product page.

If the price in an online channel differs from the Active Price, the most probably reasons are:

• The channel isn’t synchronized with the channel database. Execute job 1100 to send the price information to the channel database for the channel. If the base price of a product has been updated, the job 1040 also needs to be executed, since it is a property of a product.
• The trade agreement expected isn’t used, or the trade agreement isn’t active for the current customer, price group or date period. Check the trade agreement parameters and check the customer used in the channel. If the visitor is an anonymous visitor, the default customer defined for the channel is used.

Product information in Storefront Dynamics is fetched from the search engine and from Episerver Commerce. If the base price is used, and it is used as the default price for sorting, it may be the database of Episerver or the search engine that is out of synch.

When product information is changed in Dynamics ERP it has to be synchronized with the channels using the distribution schedule in Dynamics ERP. When the channel has been synchronized, make sure that Storefront Integration Framework Staging job and Catalog Import Job are executed in this order, and that the search index job is executed to update the search index.

Price changes in trade agreements, price adjustments or discounts are not imported into Episerver so the stage and import jobs do not need to be executed. Trade agreements, price adjustments and discounts are handled by the price and cart services of Dynamics Retail Server and Commerce Runtime.