Rocket Source

How to Prepare an Amazon Wholesale CSV for Product Analysis

Updated July 2026

Supplier spreadsheets are built for ordering, not Amazon research. They often contain category headings, blank rows, case-pack notes, formulas, and prices that are easy to misinterpret.

A good preparation step keeps the original supplier information intact while turning every offer into one consistent row that can be matched and compared.

Quick answer

Use one supplier offer per row and keep supplier SKU, product title, UPC or EAN, unit cost, case quantity, minimum order quantity, available quantity, supplier name, and source notes in separate columns. Remove decorative rows and merged cells, preserve identifiers as text, and never combine case cost with unit cost.

Practical checks

Before using a supplier file for product decisions, make sure these points are covered.

  • One supplier offer appears on each row.
  • Product identifiers are stored as text.
  • Unit cost and case quantity are separate.
  • MOQ and available quantity have their own fields.
  • Supplier SKU and source information are preserved.
  • The file contains no subtotal, category, or decorative rows.

1. Preserve the Raw Supplier File

Keep an untouched copy before cleaning anything. Work in a duplicate file or a separate sheet so you can trace a changed value back to the supplier's original catalog.

Do not replace supplier SKUs or product titles with Amazon data. Keep source fields and matched listing fields separate throughout the workflow.

2. Separate Identifiers, Costs, and Pack Quantities

Format UPC, EAN, ISBN, and ASIN columns as text before importing. Leading zeroes are part of a barcode and should not be removed by spreadsheet formatting.

If a case costs $48 and contains 12 units, store 48 in case cost and 12 in case quantity or calculate a clearly labeled unit cost. Never leave the meaning of the price hidden inside the product title.

  • Supplier SKU
  • Product title
  • Identifier
  • Identifier type
  • Unit or case cost
  • Case quantity
  • MOQ
  • Available quantity
  • Supplier and source notes

3. Remove Rows That Are Not Products

Delete category labels, page headings, subtotals, shipping notes, blank separators, and repeated header rows from the working copy. Preserve any important supplier terms in a separate notes sheet.

Check a sample of rows after saving as CSV. Spreadsheet formulas, currency symbols, and hidden columns can change during export.

Rocket Source upload step accepting a structured CSV or Excel supplier file
A clean CSV or XLSX file can move directly into the four-step scan setup.

4. Map the File Without Losing Source Context

Map the identifier and cost columns required for analysis, then keep supplier SKU, source title, MOQ, and notes available in results and exports.

The purpose of cleanup is not to make every supplier use the same catalog. It is to create a repeatable translation from their format into your decision process.

Apply the Same Rules Across the Full Catalog

Rocket Source matches supplier identifiers to Amazon listings, calculates profit and ROI, and helps you apply pricing, cost, and exclusion rules consistently across every row.

Compare Rocket Source plans

Related Guides and Tools

Official Resources

FAQ

Should supplier barcodes be numbers or text?

Store UPC, EAN, ISBN, and other identifiers as text. This protects leading zeroes and prevents scientific notation.

Should I upload case cost or unit cost?

Use the field that accurately matches your file and preserve case quantity separately. If you calculate unit cost, label it clearly and keep the original case cost for auditability.

Can I upload Excel instead of CSV?

Rocket Source accepts CSV and XLSX files. Use the format that best preserves the supplier data, then verify a sample after export or upload.