Making the Most of Your Existing Product Roundups
A curated list is mostly editorial: your picks, your order, your reasons. This guide shows how to keep all of that and refresh only the facts around each product, with a review queue that tells editors where to look. The demo runs on real prices.
A curated list is one of the most useful things a publisher makes. The picks, the order and the reasons behind them are what readers come for, and no catalog can write them. What ages is everything around the writing: the price, the stores that carry the item, the photo. This guide is about curated product lists and a simple idea for them: keep what you wrote, refresh the facts, and let a short review queue tell your editors where to look. The demo below runs on real prices last pulled November 17, 2026.
Separate what you wrote from what changes
Most lists mix two kinds of content in one block of text. Treating them separately is what makes a list easy to keep up, because only one of them needs regular attention.
Everything in the left column stays exactly as an editor wrote it. Everything in the right column can be refreshed without anyone rewriting a sentence.
You already have most of what you need
There is no new system to adopt. A list you already keep, whether a spreadsheet, a content management system or a page of links, needs one extra piece of information per product: an identifier that says which product it is. You add it once, when the pick is made. After that, the list is a set of saved picks, and the details come from the data whenever you ask for them. Turning a link into a product covers one way to find the identifier for a product you already link to.
See a list get reviewed
The demo is a sample roundup of a home cook’s favorites, as if an editor wrote it a few weeks ago. The notes are placeholders for your own. Choose when the list was written and how big a move should count, and each entry shows the lowest in-stock price and the store at that time and today. Entries that moved past your threshold, or whose lowest price is now at a different store, are marked as worth a look. Everything else reads the way it was written. The page holds a set of products that is rebuilt every night.
Notice what the review queue is not. It does not rewrite anything, and it does not decide for the editor. It turns an audit of the whole list into a short to-do, and the editor makes the call.
Three ways to refresh a list
How often to ask for fresh data depends on the kind of list. Each choice is a trade between effort and how current the page needs to be.
The data is there whenever you ask for it. When to ask, what to compare and what to do with the answer are yours to decide, which is why the same data can serve a quiet evergreen page and a busy seasonal one. Our guide on how often product pages should be updated goes through the schedule question.
Give editors a review queue, not a rewrite
The most useful rule is the simplest one: flag an entry when something an editor would care about has changed. A few rules cover most lists.
Thresholds are a judgment call. A tight rule produces more flags and a loose one produces fewer. Start loose, look at what gets flagged for a few weeks and adjust. The demo lets you see the difference between five, ten and twenty percent on the same list.
How old a list is does not tell you what changed
It is natural to refresh a list on a calendar: every month, every quarter. A calendar says a list is due, but not which entries are the reason. Checked against the same real prices, a list written 30 days ago had five of eight entries worth a look, and one written 85 days ago had six. The count moved by only one. Waiting longer did not mean far more to fix, and checking sooner did not mean less.
The practical point is that a check on the data finds the entries that moved, wherever they sit on the list, and leaves the rest alone. Which entries they are matters more than how long ago the list was written.
What the November 17, 2026 pull shows
We checked the demo’s sample list as if it had been written 60 days before November 17, 2026. At a threshold of 10%, five of the eight entries would be flagged. Four had a lowest price that moved by 10% or more, and four had a lowest price at a different store. The other three still read the way they were written.
This table is fixed to November 17, 2026. The demo above is rebuilt every night with a different set of products, so its figures will change. A handful of products is a small sample and not a measure of any market. Each figure is the lowest in-stock price across the stores that report history for that product, in US dollars.
What the API provides, and what you build
Keeping the two sides straight is what keeps the idea honest. The data supports a review queue. The queue itself, and every decision about what to flag, is part of your own process.
Getting started in three steps
Related ideas: building wishlists and collections shows a list that readers keep for themselves, and the Gift Guide API guide shows a list organized by budget.
Planning a list like this?
If you would like a second opinion on how to set this up for a list you already have, our team is glad to talk it through. Schedule a call with our team.