Price Not Updating on the Marketplace: Causes and Fixes

If your price is not updating on a marketplace, the cause is almost always one of six things: an unmatched listing, a rejected price row, a promotion lock, your own floor price rule, the wrong price field, or two systems overwriting each other. Below they run from most to least common.

A price fault is quieter than a stock fault: the order arrives, the parcel ships and the loss only shows up in the payout report. So you need to know, not assume, whether a price reached the channel.

Narrow the scope first

How many products and channels are affected tells you most of what you need, as in stock not updating on the marketplace.

• One product, one channel: matching, a rejection specific to that listing, or a promotion lock.
• One product, every channel: the problem is in the product record or a rule attached to it.
• Every product, one channel: that channel's connection, authorization or channel-level price setting.
• Every product, every channel: the price source is not being read; do not search on the channel side.

Once you know the scope, work through this order:

1. Is the product matched on that channel, down to the variant?
2. Was the last price update accepted, and if rejected, why?
3. Is the product in an active promotion on that channel?
4. Did a floor price or repricing rule stop the update?
5. Is the right field being sent: list price or sale price, with or without VAT?
6. Is another system also writing the price for this product and channel?

Matching and rejected rows

An unmatched product has no target, so nothing goes out even if its price is entered correctly. For products with colour and size variants, the parent may be matched while some variants are not; then some sizes change price and others do not. The keys to matching are covered in SKU and barcode product matching.

If matching is sound, the next suspect is a rejected row. Marketplaces do not accept price updates under every condition. Common reasons for rejection:

• The listing is inactive or awaiting approval. That side is covered in listing not approved on the marketplace.
• The sale price was sent higher than the list price.
• The price falls outside the range the marketplace accepts. Some marketplaces review or reject sharp price changes made in a short period; limits differ by marketplace, so check the current seller agreement.
• The decimal separator or currency format is wrong.

If you cannot see rejected rows, everything below is guesswork. A sound setup shows whether each update was accepted and, if not, why.

A promotion may be locking the price

When you put a product into a marketplace promotion, the marketplace manages its price under its own rules for that period. In many promotion types the price cannot be changed until the event ends, or only downward changes are accepted. The integration keeps sending, the marketplace keeps rejecting, and you see the new price in your panel while the customer sees the old one.

Check: is the product in an active promotion on that channel, and when does it end? If the price does not return to yours afterwards, send the update again once the event is over.

With November and year-end events coming up, fix promotion prices in advance and keep excluded items on a separate list; see stock and pricing during marketplace sales events.

Your own rule may have stopped the update

Sometimes the price does not move because of a rule you set. Usually the rule is working correctly and has protected you from a loss.

If a floor price is defined, the system will not send a new price that falls below it. If repricing is on, the price calculated against competitors is held between floor and ceiling, and a value you entered by hand may be overridden. In both cases the "requested price" you see in your panel differs from the price that goes to the channel.

Check: what are the floor and ceiling values for that product on that channel, is repricing on, and did the last update hit a rule? How to calculate a floor price is explained in floor price rules that prevent selling at a loss, and the repricing logic in price sync, repricing and the Buy Box.

Wrong field, wrong source: list price, VAT and currency

If the price is accepted but the channel shows an unexpected number, the wrong field is probably being sent:

• List price versus sale price. Most marketplaces hold two fields: a struck-through list price and the actual sale price. If you change the sale price but send the list price, the customer sees no change.
• VAT included or excluded. A price held without VAT in your ERP will look too low if it reaches a channel that expects VAT-inclusive prices without conversion.
• Currency and exchange rate. On cross-border channels the price is sent in foreign currency. If the rate is not updated or the wrong rate table is read, the price does not change or changes unexpectedly. See multi-currency pricing and FX management for detail.
• Wrong source. The price changed in the ERP but the integration reads the e-commerce platform, or the reverse.

Check: for that channel, which field is read, from which source, with or without VAT? Writing it down once prevents repeat problems.

Two systems may be writing the same price

The most confusing case: the price updates, then reverts minutes later. Two places are writing the same product and channel price. Someone edits it in the marketplace panel and the integration writes its value back, or an old tool left running during a migration overwrites the new one.

The fix is a rule, not code: every product and channel price needs one owner. If the integration manages it, nobody edits it by hand in the marketplace panel; if it is managed by hand, the integration does not touch that product's price on that channel.

How it works with Bulutegra

Bulutegra manages price from a single price matrix: list, sale and floor price are held separately for each channel, and changes are sent to the channel. Each product and channel carries an ownership flag that shows clearly whether Bulutegra or an external system manages it, which prevents two systems from overwriting the same price.

Rejected rows appear in the panel with their reason, and missing or unmatched items are collected in the quality tab. Channel monitoring runs continuously and a channel that goes quiet raises an alert. For repricing there is a Buy Box suggestion for Trendyol and floor and ceiling rules for Walmart, while the campaign calculator lets you see a discount's effect on price and margin before you join a promotion. In shadow mode during setup, the system only reads for one to two weeks, so you can compare your current prices with Bulutegra's side by side.

See all modules, including price sync, in Solutions, or request a demo with your own channels.