DL-036 · Case study
Price-history scoring of book ASINs for a bookseller
A bookseller needed to know which titles would sell at a profit before buying stock. We scored book ASINs from their price history and moved its in-house systems onto SP-API.
- Client
- Name withheld
- Location
- US South
- Industry
- Online bookseller
- Capabilities
- 03Build02Stabilize
01
Challenge
- Buying decisions for book stock rested on manual checks of each title.
- Price history existed, but nothing turned it into a buy or skip signal.
- Several internal systems still talked to Amazon through MWS.
02
Environment
- Very large book catalogue measured in ASINs, not titles on a shelf.
- Third-party price-history data for each ASIN.
- In-house bookstore systems submitting listings and prices to Amazon.
03
Intervention
- Built a scoring script that predicts profit per ASIN from price history.
- Ran scoring in batches across the catalogue rather than title by title.
- Added an inventory repricer driven by current market prices.
- Moved the in-house systems from MWS calls to SP-API feeds.
04
Outcome
- Each ASIN gets a profit score the buying team can sort and filter.
- Listing and price updates flow through SP-API after MWS was retired.
- Pricing follows the market instead of manual edits.
- 01PRICE HISTORYPer ASIN→SCORING ENGINEPredicted profit
- 02BOOK CATALOGUEASIN list→SCORING ENGINEPredicted profit
- 03SCORING ENGINEPredicted profit→BUYING TEAMRanked ASINsscores
- 04REPRICERMarket prices→SP-API FEEDSPrices / stock
- 05IN-HOUSE SYSTEMSListings→SP-API FEEDSPrices / stockwas MWS
Stack and services.
Tell us what has to work.
A senior engineer reads every brief. Describe the system, what it runs on today and what happens when it fails.
Discuss a project→