group_price limits what you may sell at, and an incremental sync never sees it change.
null. One price applies to every variant of the product.
What is each price for?
When nothing is discounted, all three are equal: that is normal, not missing data.
Which price is the floor of an order?
group_price, at the moment the order is created, not when you synced. A line price under it is refused with 422 price_below_minimum; equal passes. A line without a price sells at group_price. Selling under public_price is allowed and normal.
Carry a margin over group_price, so a price that moves before your order costs margin instead of a refusal. An order sent with a stale price is refused, never silently accepted.
Why can’t an incremental sync see a price change?
updated_after filters on the product’s last edit. A scheduled or temporary price starts and ends without any edit, so no timestamp moves, however often you poll.
Run a full price refresh at least daily, separate from your incremental sync:
- Page through the whole catalogue with no
updated_after. - Overwrite all three prices for every product you hold.
- Recompute your selling price from the new
group_price.
How do you show a “was / now” price?
Usebase_price as “was” and public_price as “now”: they are the figures mart.ps shows the public. Never present group_price as a public discount; it is your trade price. Run your own promotions on your own margin.
Common mistakes
- “
group_priceis always underpublic_price.” Not always: on some products a discount for your account replaces a shop-wide promotion and comes out higher. Compare per product. - “A gap between
base_priceandgroup_pricemeans a promotion.” It is mostly your standing discount. - “The API says when a discount ends.” It does not: there is no promotion flag or end date.
group_price, times the quantity, frozen when the order is created. Nothing is re-priced later.