Two lightweight decisions cover most of catalog triage: "interesting, come back to this" and "never buying this." Save for later handles the first; do-not-buy handles the second. Both stick to the row permanently, so a decision made today still stands next month.
Save for later
Save for later parks a product on the catalog's saved list without changing anything else about it.
- Where. Open the product and choose Save for later in the ⋯ menu beside Review match. Remove from saved, in the same menu, takes it off the list.
- Finding saved products. Select Saved in the status filter above the table to see only your saved products, with a live count.
- Good for. Rows that need a supplier question answered, deals you'd take at a slightly better price, and "second pass" candidates you don't want to lose in a 3,000-row catalog.
Do-not-buy
Marking a row do-not-buy records that you've looked at it and decided against it. When you reject a match you can attach a reason:
- Wrong pack quantity
- Wrong brand
- Wrong size / variant
- Margin too thin
- Too much competition
- Amazon on the listing
- IP / brand risk
- Listing out of stock
- Other, or reject without a reason
The reason takes seconds to set and pays off later: when the same supplier sends next month's price list, you (or a teammate) can see why a row was passed on, instead of re-researching it from scratch.
They persist everywhere
Saved and do-not-buy status is stored with the row in your workspace, not in your browser:
- Across sessions. Log out, switch machines, come back next week: your saved products and rejections are still there, for everyone in your workspace.
- In exports. These decisions carry into your CSV and Excel exports, so a buying team working from the spreadsheet knows exactly which rows were parked and which were ruled out.
- After a refresh. Refreshing Amazon data updates pricing and rank but never touches your decisions.
Working a big catalog down to a buy list
A workflow that scales to thousands of rows:
- Set your rules first. Apply your minimum ROI (return on investment) and any competition rules (see Filters, rules, and shareable views) so you're only triaging rows that could clear your bar.
- Make one decision per row. Matches with good numbers go straight onto the purchase order (PO). Clear losers get marked do-not-buy with a reason. Anything in between gets saved for later.
- Work the saved list. Switch to the Saved filter and resolve each row: verify the ones that are a Maybe, get supplier answers where needed, then either add to the PO or mark do-not-buy.
- Finish with a clean split. Every reviewed row ends up in exactly one bucket: on the order, or ruled out with a reason. Nothing left in limbo.
