Product and Listing are not the same record
Autopricy keeps catalogue context and the sellable Listing separate so price actions target the correct entity.
OnBuy repricer / winning checks
OnBuy repricing that knows when to compete—and when to stop
Autopricy connects OnBuy Product and Listing data to bounded repricing rules. It can evaluate the current winning state, lower an eligible price when competition requires it, and explore a controlled increase after winning without crossing the configured maximum.
OnBuy repricing challenges
Winning checks change what the next safe action should be
A useful OnBuy repricer should not lower every price on every cycle. It needs Product and Listing identity, winning-state checks, boundaries, rate awareness and delayed confirmation.
Winning can change the direction
A losing Listing may need a bounded decrease; a winning Listing may support a cautious increase if the configured strategy allows it.
Marketplace display can lag behind submission
Autopricy records queued work and later status rather than promising an instant storefront change.
Marketplace mechanics
How OnBuy repricing decisions are bounded
| Synchronise | Read Product and Listing records and retain exact account and listing identity. |
|---|---|
| Check | Use the available winning state and competition context for the current Listing. |
| Decide | Apply the configured decrease or raise strategy inside minimum and maximum values. |
| Confirm | Respect locks, quotas and processing delays; keep status history for later review. |
Reference: OnBuy API documentation · OnBuy seller terms
Winning Offer is not controlled by price alone
Autopricy responds to the OnBuy signals available to the integration. Stock, delivery, seller performance and marketplace rules can still affect which Offer wins.
Workflow
Roll out OnBuy repricing safely
Connect the seller account
Confirm the current OnBuy authorization and supported account context.
Sync Products and Listings
Check identifiers, current price, availability and winning state.
Set both boundaries
Configure minimum, maximum, decrease and optional raise behaviour.
Observe delayed results
Review queue, locks, quota handling and later marketplace confirmation.
Illustrative strategy
A controlled raise after winning
Example: a Listing is winning at £31.20 with a £28.00 floor and £34.00 ceiling. A configured strategy may test £31.40. If the Listing stops winning, the next eligible decision can move back inside the safe range; it cannot exceed the ceiling or assume an immediate storefront update.
Related resources
Continue with the relevant workflow
FAQ
OnBuy repricing that knows when to compete—and when to stop: common questions
Can Autopricy raise an OnBuy price after winning?
A configured strategy can explore a bounded increase when the available winning state supports it. The maximum price remains a hard limit.
Does OnBuy repricing update instantly?
Not necessarily. Marketplace queues and display processing can introduce delay, so Autopricy separates submission from later confirmation.
Does the lowest price guarantee the winning Offer?
No. Price is important, but availability, delivery, seller performance and OnBuy rules can also matter.
How does Autopricy avoid conflicting OnBuy actions?
The workflow uses locks, quota-aware scheduling and stored status history to prevent overlapping work where possible.
Test the workflow on a real store
Start with one supported store, a controlled product scope, explicit boundaries and visible platform results.
yuanyongvia@gmail.com