The Product Catalog
How one catalog ties vendor offers and Amazon listings together — and why everything else hangs off it.
Written lesson
The video for this lesson is in production — the written version below covers the full concept.
What it is
The Product Catalog is the hub of VendorDelta. Each catalog product collects two things: Vendor Offers — one per vendor SKU, with list price, MOQ, and units per SKU — and Amazon Listings — one per ASIN and marketplace. Offers and listings are never linked to each other directly; they meet on the product, and every offer–listing pair gets its own margin math.
The table is built for scanning thousands of products: sortable columns for Margin, Profit / mo, Best BSR, Vendors, Listings, and Status, plus optional column groups for costs, vendor comparison, replenishment, and activity. One search box covers products, SKUs, ASINs, and UPC/EAN.
Why it exists
Vendor files and Amazon data describe the same physical product in different languages — a case SKU on one side, a 3-pack ASIN on the other. The catalog holds both descriptions on one row, applies the pack math (units per SKU on the vendor side, units per listing on the Amazon side), and produces numbers you can actually compare.
Margin percent alone misleads on a big catalog — a fat margin on a product that never sells is worth less than a thin one that moves. That is why the Profit / mo column multiplies profit per unit by monthly sales velocity, so sorting the catalog surfaces where the money actually is.
How to use it
- 1
Fill it
Products arrive from vendor feeds, Amazon restock reports, or the New Catalog Product button. However they arrive, they land in the same table with the same fields.
- 2
Sort by what matters
Sort by Margin for the best deals, Profit / mo for where the money is, or Best BSR for what sells. Every analytical column is sortable.
- 3
Filter to a working set
Filter by vendor, brand, status (New, In Quote, Has Quote, Has PO), products with no offers, or archive status — then work the list.
- 4
Open the product card
Expand a row to see every vendor offer side by side with its effective cost, and every Amazon listing with sell price, fees, net, profit, margin, and ROI.
- 5
Act from the row
Add to Quote or Add to PO straight from the product card; quote and PO history stays on the card, so past negotiations are always at hand.
Common questions
How is effective cost picked?
Per offer, by strongest signal: a manual override wins, then the last PO price, then the last quote price, then the vendor’s list price — always divided by units per SKU to get a per-unit cost. Hover the price to see exactly which source is in play.
How does multipack math work?
Two independent multipliers. Units per SKU says how many sellable units are in one vendor SKU. Units per listing says how many units one Amazon sale moves. Cost divides by the first; profit math multiplies by the second — so a 12-count case and a 3-pack ASIN reconcile automatically.
What does Profit / mo actually measure?
For each listing: profit per sale × monthly sales, summed across the product’s listings and converted into your reporting currency. It is the “how much money could this product make per month” number — and it is sortable.
What do the status badges mean?
They track procurement activity: New (nothing yet), In Quote (on a draft quote), Quoted (has a vendor response), Ordered (on a PO). Filter by status to see what is stuck where.
Can I delete a product?
You archive it — the row keeps its history and disappears from the active view. Archived products come back automatically when a later feed or a moved offer adds content to them.
See it with your own data.
Upload a vendor file and watch this lesson happen to it. Free 14-day trial, no credit card.