Skip to main content
FHAVI

Research · Operations

How to price a product when your supplier changes the price every month

Supplier costs drift. Repricing everything on every change destroys trust and feed stability. A rule for which prices move, when, and how to do it without breaking Merchant Center.

2 min read

In brief

  • Price changes should follow a written rule based on margin floor, not on each supplier message.
  • Repricing at the source and syncing the feed in the same window prevents the price-mismatch flag that a manual edit creates.
  • Raising a price is cheaper than absorbing it: the customers who leave at a 5% increase are usually the ones the margin could not afford anyway.

The rule to write down

Without a rule, every supplier message becomes a decision, and decisions made one product at a time produce a catalogue where some items subsidise others invisibly. The rule does not need to be sophisticated; it needs to be explicit enough that someone else could apply it.

  • Define a minimum contribution per order, in currency, not a percentage. Percentages drift with order value.
  • Reprice only when the projected contribution falls below that floor at the current cost per acquisition.
  • Change price in steps of the smallest amount that clears the floor — not to a round number that overshoots.
  • Review monthly, not per message. A supplier that moves weekly is a supplier problem, not a pricing problem.

Doing it without breaking the listing

  1. 1

    Change the source, not the feed

    Store price first, then let the feed sync. A feed-only edit reverts at the next sync and creates a mismatch in between.

  2. 2

    Same-day ordering

    Feed and landing page must agree by the time the crawler arrives. Update both in the same working session, never one on Monday and the other on Thursday.

  3. 3

    Watch the item status for a week

    Price-accuracy flags appear after a crawl, not immediately. A quiet week is the confirmation.

Discounts complicate this

If you run a promotion at the same time as a reprice, submit the lower obtainable price. A price rise plus an active sale is the most common way an otherwise careful reprice produces a flag.

What to tell customers

  • Nothing, for small moves. Explaining a 3% change draws attention to it.
  • For larger moves, the delivery promise and return policy matter more than the price — those are what the customer is comparing.
  • Never raise a price and quietly lengthen delivery in the same week. Two negative changes together read as decline, not adjustment.

Write the floor, change the source, sync in the same window, and review monthly. A catalogue repriced by rule stays consistent; one repriced by panic does not.

Questions

Asked about this directly

Should I absorb small supplier increases?
Only while contribution stays above your floor. Absorbing indefinitely is how a profitable catalogue becomes a busy one.
Will raising prices hurt my Shopping performance?
It can reduce clicks, and it protects margin. The comparison to make is contribution per impression, not clicks.
How often is too often?
More than monthly invites price-accuracy flags and erodes trust with returning customers. If cost moves faster than that, the product's economics are unstable and the answer is to exit it, not to reprice weekly.

Keep reading

Other pieces in the library

All research

Numbers first, promises second

Send your store and we will tell you which of these failure modes is already happening — before you pay for a fix.

Prefer email? Write to md@fhavi.com