Brand PDP Group Opener

Some products don't travel alone — a "Magic Bullet blade set" or an "Ab Wheel Roller" maps to several product IDs across retailers that always need to be checked together. This extension encodes those relationships once, so opening an entire product group across four marketplaces becomes a single click instead of a manual hunt through a spreadsheet.

01 · The Problem

A Spreadsheet Is Not a Workflow

The first extension I built — the Multi-Marketplace Opener — solved opening a list of IDs. But a lot of catalog work isn't about loose lists; it's about groups:

• Products belong to families. A single retail "product" often spans multiple Amazon ASINs (variants, bundles, parent/child) plus matching Walmart, Target, and Home Depot IDs. They always need to be reviewed as a set.
• The mapping lived in a spreadsheet. Every audit started with hunting for the right rows, copying a scattered set of IDs, and pasting them somewhere to open — slow and error-prone, every single time.
• Scale made it worse. Across two brands and 126 groups, "just look it up" added up to real minutes of friction on every check.
• Cross-retailer context was lost. Comparing how a group appears on Amazon vs Walmart vs Target meant rebuilding the same ID set by hand on each platform.

02 · What I Built

A Catalog Cockpit in a Popup

The extension reads a CSV catalog at load, groups every ID by product and brand, and renders a fast, keyboard-driven interface for finding and opening them:

03 · How It Works

Architecture

A bundled CSV is the single source of truth. On load the popup parses it into an in-memory group model, then every interaction is a filter/sort/route over that model — no network, no backend.

Engineering details worth calling out

• CSV as a config layer. Keeping the catalog in a CSV means the group mapping can be updated without touching code — drop in a new export and the whole interface reflects it.
• De-duplication at parse time. The loader collapses repeated rows into unique ID sets per group and per platform, so a group with five Amazon ASINs and one Walmart ID always resolves cleanly.
• Platform-aware ID resolution. A single resolver returns the right ID list for whatever platform is active, so filters, counts, and every open mode stay consistent when you switch retailers.
• Persistent view state. Active filter, sort, brand, platform, and region all save to chrome.storage.local and restore on next open.
• Global commands. Manifest V3 commands wire copy/open to system keyboard shortcuts that fire even when the popup isn't focused.

04 · Impact

Before vs. After

05 · What I Learned

Hard-Won Lessons

• Encode the relationships, not just the data. The value wasn't the IDs — it was the grouping. Capturing that structure once is what made every later action one click.
• Separate data from code. A CSV data layer meant non-engineers could update the catalog and the tool kept working — the interface and the data evolve independently.
• Keyboard shortcuts signal "this is a daily tool." Adding global commands and F/S menu keys changed how it felt to use — from "open a popup" to "muscle memory".
• Persisted state removes re-work. Remembering filter, sort, and platform between sessions means the tool always opens exactly where the last task left off.

Part of my Chrome Extension Productivity Suite — see the companion Multi-Marketplace Opener & Scraper →