The rule for reflecting a discounted product correctly in the feed is simple: write the undiscounted list price in the price field and the discounted price the customer will actually pay in the sale_price field, and make sure these two values are exactly the same as the prices shown on the product page. For a product that is not discounted, leave the sale_price field empty. The most common mistake is writing the discounted price directly into the price field; in that case the platform does not understand that the product is on sale, and you cannot benefit from discount displays such as a strikethrough price.
What are price and sale_price for?
price: The product's regular (list) selling price. It is required for every product.sale_price: The price during the sale period. It is sent only while there is a discount and must be lower than thepricevalue.sale_price_effective_date(optional): The start and end time of the discount. If you use this field, the platform applies the discounted price only within this range.
Google, Meta, TikTok and Pinterest feeds all use this split in a similar way. Platforms may show the discount information in ads in different forms (such as a strikethrough price or a sale label); when these displays appear depends on each platform's own rules and is not guaranteed.
The most common mistakes
Writing the discounted price into the price field
If the store platform only exports a "selling price" field, the feed most often writes this single value as price. Even if the old price is shown struck through on the product page, the discount information is lost in the feed.
Sending sale_price equal to price
Filling the sale_price field with the same value as price for undiscounted products can cause the row to be treated as invalid on some platforms. If there is no discount, do not send the field at all.
The discounted price staying in the feed after the promotion ends
If a promotion on the site ends at midnight and the price goes back, while the feed is updated the next day, the price in the feed stays lower than the one on the page in between. This is the classic cause of the price mismatch issue in Google Merchant Center. The solution is either to update the feed additionally at promotion transitions or to declare the discount range explicitly with sale_price_effective_date.
Discounts applied in the cart
Discounts such as "20 percent off in the cart", which are not visible on the product page and are applied only at the checkout step, are problematic. Platforms compare the price in the feed with the price on the product page; writing a discount into the feed that is not visible on the page can count as a mismatch. Declaring this kind of promotion on Google with the promotions feature (Merchant Promotions) is a more correct route than changing the price in the feed; check the eligibility requirements in the Merchant Center help pages.
Prices on variants
If you send sizes as separate rows, each variant has its own price and sale_price value. If all sizes have the same price there is no problem; if some sizes have a different price (e.g. a price difference on larger sizes), make sure the variant link opens the correct variant and price on the page.
Currency and format
- Write the price as a number with the ISO currency code (e.g.
1299.90 TRY). - Use a period as the decimal separator; do not use a thousands separator.
- If you sell to more than one country, make sure that for each market the currency is right and the price is also shown in that currency on the site.
Discount announcements in Turkey
In Turkey, the legislation on announcements of discounted sales includes rules on matters such as how the pre-discount price is determined. Because the price value in the feed will be the same as the "old price" on the product page, the compliance of the pre-discount price you show on the site with the legislation is directly reflected in the feed too. For details we recommend consulting your legal advisor.
How HexFeed writes the price to the feed
HexFeed takes the product's current selling price and list price from your connected platform (T-Soft, Ticimax, Shopify, ikas or XML). If the current price is lower than the list price, in Google, Meta, TikTok and Pinterest feeds it writes the list price to the price field and the current price to the sale_price field; if there is no discount, it does not write the sale_price field at all. The same rule applies in the CSV feed generated for ChatGPT.
In the panel you can also schedule feed discounts, valid in a single feed only and defined as a percentage or an amount, with a date range; the status of each discount (scheduled, live, ended, off) and which products it applies to are visible. If you use a feed discount, remember that the same discount must also be visible on the product page; otherwise the price mismatch risk described above arises. For setup see the Google Shopping with ikas and ChatGPT feed with Shopify pages; to show the discount in the image, see the image templates page.
Checklist
- For discounted products,
priceis the list price andsale_priceis the discounted price. - For undiscounted products, the
sale_pricefield is not sent at all. -
sale_priceis always lower than thepricevalue. - Both prices in the feed are the same as the prices shown on the product page.
- The feed is updated on time at promotion starts and ends (or the discount date range is declared).
- Discounts applied in the cart are not written into the feed price.
- The price format and currency are consistent.
- The pre-discount price shown on the site has been checked for compliance with the legislation.
Frequently asked questions
Is using sale_price_effective_date mandatory?
No, it is optional. If your feed is updated on time at promotion starts and ends, you may not need it. If the feed is updated infrequently, or promotion transitions fall at hours such as midnight, declaring the date range reduces the mismatch risk.
Why doesn't the strikethrough price appear in the ad?
Platforms show the discount according to their own conditions; sending sale_price does not by itself guarantee that a strikethrough price will be shown. First make sure the two prices in the feed are the same as those on the page, then check the platform's conditions for showing discounts in its help pages.
Can I send different prices to different channels?
The price in the feed must be the same as the price the user sees on the relevant product page. Sending different prices to channels while the site has a single price counts as a mismatch. A per-channel price difference should only be considered if it has a counterpart on the site as well.
What happens if the list price field is empty?
If your platform provides only a single price, the feed cannot know about the discount and sends the product as undiscounted. Make sure the list (old) price field is filled in on your store platform.
