Vendor Feeds
How a vendor price file — in whatever format it arrives — becomes comparable offers in your Product Catalog.
In this lesson
What it is
Vendor Feeds is the bridge between the price lists vendors actually send and the standardized Product Catalog you make decisions in. You upload the file exactly as it arrives, map its columns once, and VendorDelta matches every row against your catalog and Amazon.
Each row lands in a review bucket — matched, needs a decision, or new to your catalog — so filling the catalog is a guided pass over what the matcher could not settle on its own, not a spreadsheet-cleaning project.
Why it exists
Your catalog is the source of truth: every product you might buy or sell, with one standard set of fields, so offers are actually comparable. Vendors do not send you that — they send price lists, each in its own format, with its own names for the same columns.
Feeds stay separate from the catalog so their mess never touches your master data. The feed holds what the vendor said; the catalog holds what you know.
How to use it
- 1
Upload the file as-is
Vendor Feeds → New Upload: pick the vendor and drop the file. No cleanup — logo rows, notes, and custom column names are expected.
- 2
Confirm the column mapping
VendorDelta auto-detects which column is the SKU, the price, the UPC, the title. Remap anything it got wrong and point at the real header row.
- 3
Let matching run
Every row is matched against your catalog and Amazon listings — one vendor SKU can map to several listings (think multipacks).
- 4
Work the review buckets
Create a product, attach the offer to an existing one, or skip the row — one decision each, with bulk actions for the long tail. Rejections are remembered.
- 5
Upload the next feed
A newer file from the same vendor updates the offers you already have; an overlapping file from another vendor attaches competing offers to the same products.
Common questions
Do I need to clean the file before uploading?
No. Upload it exactly as the vendor sent it — logo rows, notes, and custom column names included. During mapping you point at the real header row, and VendorDelta ignores the rest.
What happens when a row does not match anything?
It lands in a review bucket where you decide once: create a new catalog product, attach the offer to an existing one, or skip it. Skipped rows are remembered, so the same rejection does not come back on the next upload.
What changes on the second upload from the same vendor?
Rows that map to offers you already have become updates — new price, same product. Your matching work from the first upload carries over, and you review only what is new.
Can one vendor SKU feed several Amazon listings?
Yes. A single case SKU can supply the 1-pack, 2-pack, and 6-pack listings of the same product — VendorDelta keeps one offer and applies the pack math per listing.
See it with your own data.
Upload a vendor file and watch this lesson happen to it. Free 14-day trial, no credit card.