Seller guide / OnBuy
How to compete for the OnBuy Winning Offer without uncontrolled price cuts
An OnBuy repricer should not lower every Listing on every cycle. The useful question is whether the Listing is currently winning, which action is allowed inside the seller’s price range, and whether OnBuy later confirms the change.
See OnBuy repricingNeed the product workflow first? Review the OnBuy repricer page for supported capabilities and limits.
Start with Product and Listing identity
A Product provides catalogue context; a Listing is the seller-specific commercial record that carries the price. Repricing must update the exact Listing belonging to the connected shop, not an approximate product match.
Synchronise both records and retain their identifiers. This prevents a catalogue match from being mistaken for authority to change a seller Listing.
What public OnBuy information does and does not prove
OnBuy’s seller terms place responsibility for the Listing price on the seller and describe prices in the context of VAT, delivery and applicable import costs or duties. Seller profiles, reviews and badges are also visible to buyers.
Public pages do not provide a stable, complete Winning Offer scoring formula. A responsible guide therefore avoids claiming that one fixed price difference guarantees the winning position.
A two-direction repricing strategy
When a Listing is not winning and a comparable competing signal is available, a rule can calculate a lower target inside the minimum price. When the Listing is winning, a controlled strategy may test a higher value without crossing the maximum.
The goal is not continuous undercutting. It is to remain competitive while discovering whether margin can be recovered. Delays and quotas should prevent overlapping cycles from fighting each other.
Example with a safe range
A Listing has a £24.00 minimum and £31.00 maximum. If it is not winning, the rule may calculate £26.49 from the available comparison. If it is already winning, a later cycle may test £26.99. Neither action can leave the approved range.
A queued update is still not storefront proof. Record the action, wait for processing and use the available later state before labelling it confirmed.
Rollout checklist
Connect one shop and sync a controlled group of Products and Listings. Check identifiers, currencies, current values and boundaries. Run slowly enough to respect platform quotas and observe winning checks, actions and confirmations.
If another pricing tool is active, choose one owner for overlapping Listings. Competing automation can make the resulting price impossible to explain.
Primary sources
OnBuy repricing FAQ
Does OnBuy publish a fixed Winning Offer formula?
The public sources reviewed do not provide a stable, complete formula, so Autopricy does not claim one.
Why separate Product and Listing?
The Product is catalogue context; the Listing is the seller-specific record whose price can be changed.
Can the repricer raise a price after winning?
A configured strategy can test a bounded increase when supported, without crossing the seller-set maximum.
Should two repricers manage the same Listing?
No. Overlapping tools can issue conflicting actions, so one clear pricing owner is safer.
Related resources
Continue from guide to implementation
Test the workflow on a real store
Start with one supported store, a controlled product scope and visible platform results.