How to detect catalog additions and removals
Learn to detect catalog additions and removals across storefronts by matching product IDs and checking page coverage before comparing two snapshots.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a comparison to detect catalog additions and removals is
To detect catalog additions and removals, compare what a retailer lists at two points in time under the same conditions. A catalog snapshot is a dated record of the products or variants visible in a defined part of a storefront. For example, a seller might compare the US hiking shoe category this week with the same category last week. A useful comparison shows what appeared or disappeared, links to the original public evidence, and explains which pages were covered.
Assortment tracking helps you spot changes in what competitors carry and how they present it. Decide up front whether to count product families or product variants, such as each size and color, because the two views answer different questions. An added color can matter to a buyer evaluating an assortment without representing a new model. A product that leaves the hiking category may still be listed through the retailer's main site. Keep the wording of each finding as narrow as the evidence.
What it does for the business
- Brief buyers on meaningful assortment changesA buyer can distinguish a rival carrying a new model from a rival adding sizes to an existing line. Bring that distinction into a range review so the team can decide whether it needs a new supplier conversation or a closer look at its own size coverage.
- Find product ideas to investigateNew product monitoring can surface a finish, pack size, or use case worth evaluating. Compare those observations with customer requests, your margins, and supplier terms before proposing a purchase.
- Spend research time on changes that affect a decisionSeparate fresh observations from confirmed changes and put the most relevant rows at the top. A category manager preparing a buying meeting can spend time verifying a competing launch while assigning an incomplete category scan to a later follow-up.
- Give merchandising teams evidence they can reuseKeep the dates and source links with every finding so a colleague can see exactly what prompted a change to a comparison page or a product brief. A dated record also helps the team revisit decisions after the retailer moves or edits the listing.
How to build a comparison to detect catalog additions and removals, step by step
Define the storefront and counting unit
Two snapshots answer the same question only when they cover the same storefront and assortment.
What to do
- Write the decision you want the comparison to inform, such as whether to review your range before the next buying cycle. Set aside categories that cannot affect that decision.
- Record the retailer, country storefront, category or query, and the filters you will use. Include settings that change which items the page shows, such as a filter that hides unavailable sizes.
- Pick product or variant as the unit of comparison. If the decision is about size coverage, record each size and color you intend to follow and keep that rule for the next observation.
- Capture the date, time, and time zone for each snapshot. Keep a brief scope note with the baseline so someone else can repeat the check without guessing which category or filters you used.
Why
Competitor catalog changes are easy to misread when an observation comes from a different storefront. Regional catalogs can have different models, and a filtered view can hide items that are still available elsewhere on the same site. By writing down the exact scope, you preserve the conditions that make a later comparison useful.
Collect catalog rows and record page coverage
A page that opens tells you what is on that page, and a page log tells you what you covered.
What to do
- Open the public category page in the intended market. Capture the merchant's product identifier, the displayed product name, the detail link, and any variant identifiers you can verify on the detail page.
- Check pagination, the way a site splits a listing across pages. Follow the public next links or use the visible load-more control, and keep a count of pages expected and pages actually visited.
- Save the URL and observation time with each record. If you use a saved page, carry forward its original URL and capture time so a file opened today does not pass for today's storefront.
- Log blocked pages, unexplained gaps, and any stopping point imposed by the review. Treat the scope as incomplete whenever a page is skipped or a limit cuts off the listing.
Why
A retailer can reorder a category between visits. Comparing the first page on two dates can make ordinary sorting changes look like additions and removals. A page log also makes a recheck precise. You can return to the pages that failed before asking someone to collect the entire category again.
Match products by stable identifiers
A changed title belongs to the same product when its verified identity stays the same.
What to do
- Use a verified product identifier or a merchant SKU, the retailer's stock keeping unit, where available. Keep the seller with that identifier so two merchants using the same SKU format do not get joined into one record.
- Match variants within that seller and product identity. A parent product page can list several colors or sizes under the same URL, so check the variant field or identifier before consolidating rows.
- Investigate changed links or names against the product detail page. If a handle changes and the merchant identifier still points to the same product and variant, treat the records as the same listing for the comparison.
- Resolve duplicate rows introduced by overlapping pages or category placements. Leave uncertain identities pending review and carry dates and links forward with the records you accept.
Why
Product titles and URLs can change during a site refresh. Matching purely on those fields can turn a renamed item into two false changes. A consistent identifier also lets you tell an actual variant expansion from a merchandising change such as promoting the same variant to a new category tile.
Compare the two snapshots within their verified scope
A removal claim needs a complete comparison of the same scope on both dates.
What to do
- Preserve your first pass as a baseline. On the next pass, confirm that the country storefront, category, filters, and counting unit match before making a change table.
- Compare the matched records and list products or variants present on only one side. When both inventories are complete within the chosen scope, label these as additions or removals within that scope.
- Use newly observed or not observed where coverage is incomplete. If the baseline ended halfway through the category, a current item could have been in the missing half all along.
- Read the coverage log along with the change list. If a source could not be read or returned no usable records, record which source needs another check before drawing a conclusion.
Why
A product missing from today's record can reflect a gap in the collection, a move to another category, or an actual removal within the chosen scope. The comparison can resolve the scoped listing question when both inventories are complete. It takes separate evidence to establish where else the item is sold or whether the maker has stopped supplying it.
Verify the changes that could affect a buying decision
A useful change table gives the next reader enough evidence to check the finding.
What to do
- Reopen the source links for rows that could change a buying or merchandising decision. Verify the seller and product identity against the evidence from each observation.
- Keep a compact table with the change label, seller, product, variant when applicable, dates, and source links. Put the exact category or scope in the heading or near the table.
- Lead with the most useful observation and any coverage gap that could affect it. Explain whether the evidence came from a current storefront visit, saved pages, or supplied records.
- Write one next check or action alongside an important finding. If a product disappeared from the category, check the direct detail page or other relevant categories before escalating the observation.
Why
Someone acting on the result needs to know how much weight the observation can carry. A verified addition might justify a buyer reviewing a competing product detail page. A row from a partial scan might justify collecting a missing page first. Keeping those actions distinct makes the table useful even when coverage is incomplete.
Common mistakes
- Comparing different filtersA snapshot filtered to available items can hide listings that the broader category still includes.
- Counting titles as identitiesA rename can create a false addition and removal when the underlying product identifier stays the same.
- Treating the first page as the categoryA change in default sort order can move the same products in and out of the first page.
- Equating category removal with discontinuationA scoped removal says the item left that view, while confirmation of discontinuation requires separate evidence.
- Giving saved evidence today's dateUse the original capture time so the sequence reflects when the retailer's pages were actually observed.
What a good result looks like
- A dated scope that another reader can reproduce using the same storefront, category, and filters.
- A consistent counting unit with product and variant identifiers that can be traced to their sources.
- Page coverage for both snapshots, including skipped, blocked, or truncated pages.
- Change labels that reflect whether both observations were complete within scope.
- A short list of material changes with source links and a specific follow-up for each one.
And then what? Using the result
- Bring verified additions that overlap your range to the next buying review and assign an owner to assess demand and supplier terms.
- Check the detail page and other categories for important missing products before changing how you describe a competitor's offer.
- Give the merchandising team verified changes that affect its comparison pages or product briefs.
- Revisit uncovered pages and keep the dated snapshots available for the next comparison.
When to run it
- Before a seasonal assortment reviewCompare the same rival categories across observations before choosing which product lines, materials, or size ranges to investigate.
- After a retailer reorganizes a storefrontCheck which identifiers still match after names and links move. Record changed category boundaries before comparing a new view with an older snapshot.
- When deciding whether to widen a product lineTrack whether competing stores add distinct models or add variants to models they already carry. Use the distinction to frame the questions you bring to suppliers.
Questions people ask
How do you detect catalog additions and removals?
Compare two dated inventories for the same storefront, market, category, and filters, matched by seller and stable product or variant identity. Use addition and removal labels only when both snapshots are complete for that scope.
What counts as a complete catalog snapshot?
A catalog snapshot is complete when you have checked every expected page and captured every eligible item at the level you chose to count. A bounded collection may still be complete for a narrow category, provided your limits let you cover the whole category as defined.
What is the difference between a new product and a new variant?
A new variant adds a choice such as a size or color to an existing product, while a new product adds a distinct product identity. Verify the relationship on the retailer's product page or through stable identifiers before counting the change.
Does a removed listing mean a product was discontinued?
A removed listing shows that the product left the scope you checked. It may still have a live detail page, appear in another category, or be supplied to another retailer. Treat discontinuation as a separate question for the retailer or manufacturer.
Can you compare saved catalog pages?
Yes, when the saved pages preserve comparable scope, original URLs, and capture dates. Check that each saved set covers every page you need before using it for an addition or removal claim, and describe it as historical evidence in the result.
Can I still report a finding when a page is blocked?
Yes, report the rows you can verify and describe the affected scope as incomplete. Use newly observed or not observed for unmatched entries, and list the blocked page so a reader knows where to resume the check.
More jobs in Monitor
Detect catalogue additions and removals, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac