What should I do if my product prices are not updating correctly?

If your product prices are not updating, first verify that the feed is correctly mapped to the Price or Cost field and that the product identifier matches your store’s product or variant. Check the source row used for the product and confirm that every column referenced by a condition contains the expected value; for example, a condition such as col("sale_prijs") != "" cannot select a sale price when the source column is empty. The source data used by the sync must contain the value at the time the feed runs.

If everything looks correct, review Preview Sync and then run the full feed using Start Process to apply the changes. For a controlled test, preview or run the feed for a sample SKU and compare the source values, calculated result, and Shopify Price/Compare-at price fields. If one field updates while another field using a similar rule does not, verify the source data and each field’s mapping and condition separately rather than assuming the rules received the same input.

If the price still does not update, run the Update feed again and provide a sample SKU and its expected price so the feed data and pricing rules can be checked.

If a feed was previously closed or paused, re-run the feed or reschedule its automation to reactivate syncing before checking the prices again. You do not need to delete existing products when only the price or cost needs to change; use the Update feed to update those fields directly.

For supplier prices that use both commas and decimal points, set the Price delimiter to Auto and re-import the products. If Auto parses some values incorrectly—for example, 4,39 becomes 439 or 0,84 becomes 0,00—use Liquid mapping to convert commas to decimal points:

{{ data | jmespath: "RegularPrice" | gsub: ",", "." }}

There is no built-in Find and Replace function for the Price field. The Price field can instead use Liquid mapping to replace the comma with a decimal point. Test the mapping with a few filtered products before running the full update.

For price transformations, conditions are evaluated from top to bottom and the first matching condition is used. Put the most specific, lowest-price range first and place a general any rule last. For example:

price_f < 5
*3.5

price_f >= 5 and price_f < 10
*3.0

price_f >= 10
*2.8

Use price_f or col#_f for numeric comparisons. A condition using compare_at_price checks the value already stored in Shopify; if that value is blank or zero, the condition may not apply. Use a feed column condition such as col8_f > 10 when the comparison should use the supplier file.

In some cases, support may need to adjust mapping logic (such as markups, delimiters, or specific conditions).

Updated on: 05/08/2026