Skip to main content
A rule in Suggest mode does not change prices by itself. Each time it runs, it puts a recommendation in the queue for every product whose price it wants to change: the current price, the proposed price and the full reasoning behind it. You approve a recommendation to apply the price, or reject it. Rules in Auto-apply mode use the same recommendations but decide them on their own; their results show in the queue too. See How repricing works. Open Pricing Intelligence > Repricer > Recommendation queue. To see the queue you need the Repricer Recommendations permission, under Pricing Intelligence > Repricer. Approve recommendations and Reject recommendations let you decide them. See Repricer roles.

​
The queue

The page title counts the recommendations under the selected filter, for example “Price recommendations — 12 pending”. Under it, a note reminds you that the repricer does not separate markets: “Not scoped by market: every proposal here compares markets that share the product’s currency — a German price can be set from Austrian competitors.” See Markets and data sources. The filter chips above the list choose which recommendations you see. The queue opens on Pending. The list shows 50 recommendations per page, newest first. Click Status or Expires to sort by it. The other columns cannot be sorted. Each row has two buttons on the right:
  • Show me why (the info icon) opens the recommendation’s explanation; see Show me why.
  • Approve (the check mark) applies the price straight away. It asks first only when the price was changed after the suggestion; see Prices changed after the suggestion. It appears only on pending recommendations that are not blocked.
  • Keep out of this rule (the pause icon), on a pending recommendation, opens Keep my price for that product and rule; see Keep products out of a rule.
New recommendations appear on their own while the page is open. Click Refresh to reload the list yourself.

​
Approve recommendations

1

Check the recommendation

Read the Old → New column, or open Show me why to see the competitor offers, the strategy and the constraints behind the proposed price.
2

Approve one recommendation

Click the check mark on its row, or click Approve on its Show me why page. The price is applied at once.
3

Or approve several at once

Tick the recommendations. The checkbox in the header ticks every row on the page. To take every recommendation under the current filter, across all pages, click Select all matching the filter (N); the bar then says “All N selected”. You can select up to 10,000 recommendations this way.Click Approve N, or Approve N changes above the list. The Approve N price changes dialog says “Changes will be sent to sales channels and deployed according to the sync schedule. This action cannot be undone.” Click Approve N changes to confirm, or Cancel.
Approving a recommendation sends the proposed price to Catalog, which writes it to the rule’s price level. The recommendation becomes Applied. If Catalog cannot write the price, it becomes Application failed. See Price levels. Before applying, Omnilinker checks the rule’s margin floor again, against the product’s purchase price as it is now. The purchase price may have changed since the rule ran. A recommendation whose price no longer clears the floor, or whose product has no usable purchase price, is not applied: it becomes Application failed. A blocked recommendation is skipped and stays Pending. When this happens, Omnilinker tells you:
  • “Not applied — the price no longer passes the rule’s checks (for example the margin floor at the current purchase cost). See the recommendation’s status.” when nothing you approved was applied.
  • “N of M applied. The rest were not — a blocked recommendation cannot be approved, and one whose price no longer passes the rule’s checks (for example the margin floor at the current purchase cost) is marked as failed. Check their status.” when only part was applied.
Recommendations that were not pending when you approved them are left as they are. A recommendation is not applied, and becomes Application failed, when its price level is no longer Omnilinker’s for that product: “Not applied: the price at ‹level› is set outside Omnilinker for this product”. See Who sets a level’s prices.

​
Prices changed after the suggestion

When someone, an import or another rule changed a price after the rule suggested a new one, approving would replace that change. Omnilinker then asks first, in Prices changed after the suggestion: for one recommendation “This price was changed after the suggestion (199.00 → 189.00). Approving replaces it.”, for several “2 of these prices were changed after the suggestion (e.g. …). Approving replaces them.” Click Approve anyway to approve, or cancel and look at the products first. The question is asked wherever you approve: on a row, for a selection, and in Show me why.
An applied price cannot be undone from the queue. To go back, change the price in Catalog, or let the rule propose a new price on its next run.

​
Keep products out of a rule

Tick recommendations of one rule and one price level and click Keep out of this rule in the bar, or click the pause icon on a row. Keep my price opens for those products and that rule. It keeps the products out of the rule, so it stops proposing prices for them, and cancels their pending recommendations from it. You need Keep product prices out of repricer rules or Edit rules. Selecting across pages does not work here: “Select rows on this page to keep them out of a rule.” See Keep my price.

​
Reject recommendations

1

Select the recommendations

Tick them in the list, or use Select all matching the filter (N).
2

Reject them

Click Reject N. The Reject price changes dialog opens.
3

Give a reason, if you want

Type a reason in Reason for rejection (optional), up to 512 characters. It is kept with the recommendation and shown in the audit log.
4

Confirm

Click Reject changes.
The price does not change. Only pending recommendations are rejected; others in the selection are left as they are. To reject one recommendation, open its Show me why page, click Reject, type a reason in Reason (optional) if you want, and click Reject. Blocked recommendations cannot be approved, but you can reject them from the queue to clear them. See Blocked recommendations.

​
Show me why

Click the info icon on a row to open the recommendation’s explanation. The page shows:
  • The header: the product, its status (for example PENDING APPROVAL) and how long until it expires.
  • The decision bar: Approve and Reject for a pending recommendation you can decide. For a decided one, the outcome instead: Approved, Rejected (with the reason), Applied or Application failed, and the time. The buttons you have no permission for are hidden, and the bar is hidden for a blocked or expired recommendation.
  • The result: the proposed price, an outcome such as PRICE RAISED, PRICE LOWERED or BLOCKED · MARGIN, and a sentence explaining it. When the product has a purchase price, it also shows NEW MARGIN and GROSS PROFIT / UNIT, with the previous margin and the rule’s margin floor.
  • RULE THAT FIRED: the rule’s name, status, mode, schedule and scope, with Open rule editor →.
  • The decision steps: INPUTS · CONTEXT (the competitor offers the rule saw), STRATEGY · APPLY (the raw price the strategy proposed), CONSTRAINTS (margin floor, MAP, minimum and maximum price), ROUND and the final outcome.
  • COMPETITOR OFFERS · sorted by price: up to 30 of the lowest offers the rule saw, with the merchant, when the offer was observed and how far it is from the proposed price. Offers left out by the rule or by merchant settings, and offers that could not be ordered, are struck through.
  • SNAPSHOT: the status, when the recommendation was generated and when it expires, the run and the price level.
  • NAVIGATE: Edit the rule, Dry-run history for this rule, Back to queue, and Other recs for this SKU, which opens the product in Product matching.
  • PRIOR RECOMMENDATIONS · 14d: the prices proposed for this product over the last 14 days. When the price changed often, a warning says the cadence may be too tight.
  • Show raw payload: shows the engine’s raw values for each step.

​
Expired recommendations

Once its expiry time has passed, Show me why no longer offers Approve or Reject. It says “This snapshot has expired — competitor prices are likely different now. Re-run the rule for a fresh recommendation.” Click Re-run rule to run the rule again and go back to the queue; you need the Run rule now permission, and the rule must be enabled.

​
Blocked recommendations

When a constraint stops the strategy’s price, for example because it would go below the margin floor or the MAP, the rule still adds a recommendation so you can see why. It has no proposed price and cannot be approved: the queue shows no Approve button for it, and Show me why says “The repricer blocked this proposal. Nothing will be applied unless the constraint is relaxed or a human overrides.” The sentence under the price names the reason, for example a missing purchase price. Fix the cause (the rule’s constraints, or the product’s purchase price) and let the rule run again, or reject the recommendation from the queue. A rule in Auto-apply mode does not leave blocked recommendations pending: it rejects them straight away, and the audit log shows the reason. See Constraints and guardrails.

​
Statuses

In the queue’s Status column, Application failed still appears as ApplicationFailed; Show me why shows Application failed.

​
What happens to recommendations over time

  • A new run replaces older proposals. When a rule runs again and proposes a different price for a product that still has a pending recommendation from that rule, the old one is Cancelled and a new one is added. If the proposal has not changed, the old one stays.
  • Pending recommendations expire. A recommendation expires 72 hours after it is created, unless your organization set another value in Recommendation expiry (hours) (1 to 720). A clean-up at 03:00 UTC every day marks the expired ones Expired. Until it runs, a recommendation past its expiry time stays Pending and can still be approved from the queue.
  • Old recommendations are deleted. Applied recommendations are kept for 365 days, and rejected, cancelled, expired and failed ones for 90 days, unless your organization changed Applied recommendation retention (days) (30 to 730) or Other terminal recommendation retention (days) (30 to 365).
These settings are in the Repricer group of the settings page, for people with the Repricer Settings permission. See Settings.

​
Troubleshooting

Check the filter: the queue opens on Pending. Rules in Auto-apply mode decide their recommendations themselves, so they leave no pending ones; look under All. A rule adds recommendations only for products whose price it wants to change; products with no change, or skipped for lack of data, add none.
The purchase price changed since the rule ran, so the proposed price no longer clears the margin floor, or the product has no usable purchase price any more. The recommendation is now Application failed. Check the product’s purchase price, then let the rule run again. See Purchase prices.
The recommendation is blocked by a constraint, or it is no longer pending. Open Show me why to see which.
You need Approve recommendations or Reject recommendations. The queue shows the buttons to everyone who can see it; ask your admin for the permission.

How repricing works

Suggest and Auto-apply modes, and how a rule reaches a price.

Dry runs

See what a rule would do before it proposes real prices.

Audit log

Who approved, rejected and applied what, and when.

Repricer roles

Who can see, approve and reject recommendations.