USE CASE

Buy Box Tracker: Amazon Offers Data That Feeds Your Repricer

The Amazon offers API returns one row per seller offer on a listing, with the price, the shipping cost, the condition, an FBA flag and a true/false Buy Box column. It runs daily or on demand, and the rows reach your repricer or your own rules through the REST API or a CSV file.

PAIN POINTS

Why Marketplace Repricers Lose The Buy Box

  1. 01

    You Can't See Who Takes the Buy Box

    On competitive ASINs, the Buy Box moves between sellers often. Seller reports show your own share, not which competitor won it, when or at what price.

  2. 02

    Marketplace APIs Show Part of the Picture

    Your repricer is fed by marketplace APIs built around your own listings. Detail on competing sellers is limited, and there is no history of who held the Buy Box.

  3. 03

    Cross-Marketplace Listings Drift

    Same SKU on Amazon, eBay, Walmart — each marketplace's pricing engine moves independently. Manual reconciliation is impossible at scale.

  4. 04

    FBA Stock Drift Affects Buy Box Eligibility

    FBA inventory levels affect Buy Box win-rates. Without stock signal monitoring, you set prices on partial information.

  5. 05

    Account Health Degrades Silently

    Marketplaces flag restricted-brand violations weeks after they occur. Without seller-side monitoring, your account suspends without warning.

EUR 0.15

Per 1,000 listing pages collected — no plan, no seat licence, no quota

35

Ready-made marketplace and retailer endpoints, callable straight from your repricer

5

Free requests on every new account — pull one of your own ASINs before you commit

HOW IT WORKS

How Marketplace Repricing Works With Scrapewise

01

List Your ASINs

ASINs, GTINs, SKUs, or marketplace URLs you want covered.

02

Scrapewise Refreshes on Your Schedule

Buy Box, prices, sellers and stock signals extracted on the schedule you set.

03

Feed Your Repricer

Pull structured data through the REST API or a CSV export and use it in your repricer rules or your own pricing logic.

One ASIN, Four Offers, One Price Worth Reacting To

A repricer that chases the lowest number on the page will cut your margin against an offer that was never competing with you. This is the same ASIN read properly — B07ZL47PXP, where you sit at $45.99.

  1. Read Every Offer, Not the Headline Price

    The ASIN page shows one price at the top and a stack of offers underneath. Four sellers are live: NorthTech at $43.49 FBA, you at $45.99 FBA, ValuePort at $41.20 FBM with six-day handling, and ReStock at $34.00 used. A single-price scrape returns $43.49 and loses the other three, including the one holding the Buy Box.

  2. Discard the Offers You Do Not Compete With

    ValuePort is cheaper and irrelevant — six-day merchant fulfilment is not Buy Box eligible against Prime-speed offers, so it wins nothing. ReStock is used condition, a different product as far as the Buy Box is concerned. Repricing against either is a margin cut that buys no additional sales.

  3. Act on the One Offer That Holds It

    NorthTech at $43.49, FBA, new, in stock — that is the offer holding the Buy Box and the only number your rule should read. The row you receive carries the winner, their price, their fulfilment type and the timestamp, so the repricer decides on the same evidence you would have used by hand.

What Decides the Buy Box Besides Price

Sellers reprice against the lowest offer because it is the only field they have. Price is one input among several, and the others are readable from the listing — which is why a lower price frequently loses.

Fulfilment and Delivery Speed

FBA and Prime-speed merchant fulfilment compete on one tier; slow merchant fulfilment competes on another. A cheaper offer with six-day handling is not in your race at all. Reading fulfilment type alongside price is what separates a real competitor from a number that only looks like one.

  • fulfilment
  • ships_in_days
  • is_prime
  • seller_name

Condition

Used, renewed and open-box offers sit on a separate Buy Box from new. They regularly sit at the bottom of the offer stack and regularly get scraped as "the lowest price". A repricer fed that number cuts a new-condition price to chase a refurbished one.

  • condition
  • condition_note
  • is_new
  • offer_id

Stock and Eligibility

An offer that has run out does not hold the Buy Box regardless of its price, and your own FBA stock position affects whether you can hold it. Stock signal read from the listing tells you when a competitor's price stopped mattering — often the cheapest explanation for a Buy Box you suddenly won or lost.

  • in_stock
  • stock_signal
  • buy_box_winner
  • checked_at

History

A single snapshot cannot tell you whether a competitor is testing a price for an afternoon or has repositioned permanently. Only the second is worth matching. Every run retained means a Buy Box loss can be traced to the offer and the hour it changed, rather than guessed at from a seller report a week later.

  • price
  • previous_price
  • buy_box_winner
  • won_at

What You Send, What You Receive

You supply the ASINs and the cadence. You receive the full offer stack per listing, with the Buy Box winner identified.

You give
  • ASINs, SKUs or listing URLsrequired

    The listings you want covered. ASINs, GTINs, your own SKUs, or raw marketplace URLs.

    B07ZL47PXP, B0B5HBT3T6, B09NMLZ2GH
  • Marketplacesrequired

    Amazon, for the offer rows with the Buy Box column. Other marketplaces can be read as normal product pages with the AI scraper, without a Buy Box column.

    amazon.comamazon.deamazon.co.uk
  • Offer scopeoptional
    • New condition, Buy-Box-eligible only

    On by default. Used, renewed and slow-fulfilment offers are captured and labelled, but excluded from the competing-price field your repricer reads.

  • Refresh scheduleoptional
    • Daily
    • Every few days
    • On demand

    How often each listing is re-read. A full-access API key also lets you start runs from your own code.

You get

One row per competing offer, 11 columns each

  • asin
  • marketplace
  • listing_url
  • seller_name
  • offer_price
  • currency
  • fulfilment
  • condition
  • in_stock
  • is_buy_box_winner
  • checked_at

Delivered by REST API or CSV export. Offers from the same ASIN stay on separate rows, so you can see who you are actually losing the Buy Box to.

The Offer Row You Actually Receive

One row per offer per run, not one row per ASIN. This is B07ZL47PXP as it lands in your repricer.

asinseller_nameoffer_pricefulfilmentconditionin_stockis_buy_box_winner
B07ZL47PXPNorthTech$43.49FBAnewyesyes
B07ZL47PXPyou$45.99FBAnewyesno
B07ZL47PXPValuePort$41.20FBM — 6 daynewyesno
B07ZL47PXPReStock$34.00FBMused — like newyesno
BUILD VS BUY

Marketplace API, or an Independent Data Layer

Feature
Marketplace API Alone
Scrapewise
Competing offers
Limited detail on sellers other than you
The full offer stack read from the listing, seller by seller
Buy Box winner
Your own share, not who took it or at what price
Winner identified per run, with their price and fulfilment type
Other marketplaces
A separate integration and a separate schema per marketplace
Amazon for the Buy Box rows; Walmart has its own product data API; other shops as normal product pages, without a Buy Box column
History
Whatever window the API retains
Every run kept, so a Buy Box loss is traceable to an offer
Effect on your seller account
n/a
Runs on our infrastructure — never from your seller account or its IP
What you compare on cost
Integration work, plus the margin lost repricing on partial data
EUR 0.15 per 1,000 delivered pages, 5 free requests to test
BENEFITS

Repricing Data You Control

Buy Box Data On Your Schedule

Buy Box Data On Your Schedule

Seller and price data from the listing itself, for the ASINs that matter.

Seller-Level Offers on Amazon

Seller-Level Offers on Amazon

One row per seller offer on an Amazon listing: seller name, price, shipping, condition and FBA flag.

Repricer-Ready Output

Repricer-Ready Output

Pull Buy Box and seller data through the REST API into your own pricing engine, or export CSV for your repricer rules.

THE SHORT ANSWER

Buy Box Tracker: The Short Answers

What is a Buy Box tracker?

What is a Buy Box tracker?

A Buy Box tracker is a list of who holds the Buy Box on each of your ASINs, saved run by run. Here that is the Amazon offers API on a schedule. One call per listing costs €0.00015, so 200 ASINs checked daily are 6,000 calls a month, €0.90.

What does the Amazon offers data hold?

What does the Amazon offers data hold?

One row per seller offer: the seller name and ID, the item price, the shipping cost, the condition, whether Amazon fulfils it (FBA) and whether that offer holds the Buy Box. One call returns about 10 offers plus the total offer count for the listing.

How does it feed my repricer?

How does it feed my repricer?

Every run saves the offer rows in your Scrapewise account. They reach your repricer or your own pricing rules through the REST API or a CSV file. Scrapewise is the data feed: it changes no price itself.

Who Won the Buy Box Yesterday? Your Repricer Should Know.

Stop running marketplace pricing on marketplace API data alone. Scrapewise gives marketplace sellers independent Buy Box and seller data.

FAQ

Frequently Asked Questions

Common questions about marketplace repricing with Scrapewise.

Repricers automate price changes. Scrapewise is the independent data layer beneath, with seller-level + listing-level data your repricer can use to make better decisions.