Build a product selection your future self can reuse.

Open any promotion creation flow inside Seller Central — Money Off, Social Media Promo Codes, Buy One Get One — and the first thing Amazon asks for is a product selection. It is the list of ASINs the promotion is allowed to apply to. The interface is brusque, the configuration choices are quiet, and the implications stay invisible until something goes wrong.

This episode is a deep dive into a part of the system most operators rush through. The promotion mechanics in the next ten episodes all depend on it, and the practices below are the difference between a clean promo programme and a folder full of one-off selections nobody remembers naming.

The three selection types

Amazon gives you three ways to define which products a promotion applies to:

• Product list. An explicit list of SKUs that you upload (or paste) into a named selection. The list is stored in your account and reusable across any future promotion.
• Inventory file (ASIN list). A one-off selection built from a CSV file, useful for ad-hoc promos where the SKU set is unlikely to be reused.
• All products. Exactly what it sounds like — every active SKU in your catalogue qualifies. Necessary for certain account-wide promos, and a sharp footgun in every other situation.

For anything that even might recur — a quarterly Subscribe & Save promotion, a seasonal coupon, a hero ASIN deal cadence — invest the extra minute and build a named product list. Future promotions then take seconds instead of minutes, and the eligibility for each ASIN is a property of the list rather than something you have to re-check from memory.

Naming conventions that pay rent

A product selection's name is what you'll search for six months from now when you're spinning up a Prime Day promotion at 11pm the night before. The default names Amazon offers (the date, the ASIN count) are useless when you have twenty of them.

A naming convention that holds up over time:

{brand}__{category}__{purpose}__{vYYYYMMDD}

For example: brandA__skincare__hero-asins__v20260101. The version date at the end is what lets you confidently archive an old selection and create a new one without losing track of which promo points at which version.

Variations, parent ASINs and the trap of "include all children"

Parent ASINs with variations are where most product-selection accidents happen. A promotion applied to a parent ASIN with "include all variations" ticked will quietly cover every child — including ones that are out of stock, low-margin outlier variants, or the sample-size SKU you never intended to discount.

The default we apply: list child ASINs explicitly. The extra clicks are cheap insurance against a 30% coupon firing on the 500-millilitre family-size of a product you only ever wanted to promote in the 200-millilitre travel size.

For ASINs where you genuinely want every child included — for example a colourway parent where every variant carries the same unit economics — name the selection in a way that flags the include-all behaviour. __incl-all-variants__ in the name is enough to stop a future operator from assuming the list is curated.

Eligibility at the selection level

Amazon evaluates promotion eligibility per ASIN, not per selection. That means a selection of ten ASINs might launch a promotion that runs on six and silently skips four because they failed Buy Box, star rating, or policy checks on the day. The promotion dashboard reports success on the six and never surfaces the four it dropped.

Two habits prevent this:

• Before any promotion goes live, pull the selection's ASINs into a quick eligibility check — Buy Box ownership, star rating, inventory cover, suppression flags. Five minutes here saves an hour of forensic work later.
• For promos that depend on every ASIN running (e.g. a coordinated brand-wide deal during Prime Day), split the selection by tier — the hero ASINs in one list, the long-tail in another. If a long-tail ASIN drops out, the headline still runs.

Reusing selections across promotions

A well-named, well-curated selection is reusable across coupon promotions, Money Off, BOGO, and Social Media Promo Codes without any modification. The selection is just a list — it doesn't carry the mechanic with it. That's why naming it by intent (hero-asins, clearance, seasonal-q4) is more useful than naming it by mechanic.

Some teams maintain a small stable of evergreen selections — "hero ASINs", "subscribe & save winners", "clearance", "new launches" — and rotate the promotional mechanics on top of them throughout the year. The catalogue work happens once; the promotional calendar becomes a matter of choosing the mechanic and the dates.

What to write down

Treat each named selection as a small documented artefact. Keep a one-line note alongside the name — what it covers, when it was last refreshed, and who owns it. The note belongs somewhere the team will actually read it (your shared promo calendar, a Notion page, a pinned message). Amazon's UI gives you a name field and nothing else.