Skip to main content
Approving a price in Price Approval registers it for delivery; it doesn’t end the story. The Approved Prices detail page is where you inspect what was registered, follow each price through its lifecycle, and confirm what actually reached the systems that consume it. Open it from the Approved prices row under Outbound on the Datasets page.
This page is read-only for the price values themselves — they come from Price Approval. What you manage here is the lifecycle around them: effective dates, and visibility into delivery.

​
Current vs History

The page has two views:
  • Current — the price that is in force for each product right now: the latest registered version, its source, and its delivery state.
  • History — the full trail of registered versions for a product over time, so you can see what changed, when, and what a consumer would have received at any point.
Seeing both matters because downstream systems pull on their own schedule. The current price is what you intend; the history is what was actually handed over.

​
The price lifecycle

Each registered price carries a state so you can tell, at a glance, where it stands:
  • A price that differs from what the product already had is a real change, on its way to delivery.
  • A proposal that matched the current price is marked Not Changed — registered for completeness, but nothing for a consumer to act on.
  • Once a consumer has taken a version, that fact is recorded against it, so a later edit never rewrites history a client already received.
The point of the lifecycle is a reliable answer to “which exact price was in force, and which version did each consumer get?” — without that, an amended date or a re-run can blur what was actually delivered.

​
Amend an effective date

An effective date can be corrected after a price is registered — for example to move a change to the start of a campaign. Amending the date adjusts when the price takes effect going forward; it does not overwrite a version a consumer has already received. The earlier version stays in the History trail exactly as it was delivered, and the amendment is a new entry on top of it.

​
How consumers receive prices

Registered prices are delivered to the systems that integrate with Retailgrid — your webshop, ERP, or BI tool — through your export path and the public API. The delivery state on each row tells you whether a price is still pending, has been delivered, or was superseded. For how an integration reads and acknowledges delivered prices, see the API reference.