Sourcing workflow
Work through the sourcing analysis
- 01
Choose a catalog or supplier-quote workflow
A priced catalog needs a product name and listing price on each row. A supplier batch needs supplier cost and an ASIN, Walmart ID, or supported product URL.
- 02
Add optional assumptions
Catalog rows can include marketplace, category, cost, shipping, fulfillment, advertising, referral, returns, discount, and target margin. Supplier batches can include product name, URL, marketplace, and other audit assumptions.
- 03
Run the local calculation or queue a product
Priced catalog rows are calculated in the browser. Identifier-only supplier rows wait for you to open the listing and run the Page reader; the app does not fetch marketplace pages automatically.
- 04
Review decisions and exceptions
Compare profit, ROI, maximum buy price, and Buy, Review, or Avoid outcomes. Fix invalid rows or inspect items that need more listing data before making a sourcing call.
- 05
Export the result set
Download a CSV of catalog or supplier-batch audit results to keep working with the outcomes outside the current view.
Catalog files are processed on your device
The catalog workflow reads the selected CSV in the browser and calculates up to 1,000 priced items locally. The product catalog is not uploaded to the app server for processing.
Rows without a price can use the separate supplier-quote queue when they include a supported listing identifier or URL. Each queued product still needs a user-triggered visible-page read to return listing details.
Bulk screening does not replace product verification
A CSV result uses the row values and configured planning assumptions. Verify category, current marketplace fees, fulfillment classification, pack match, restrictions, supplier terms, and demand before ordering.
The catalog is a screening aid. It does not guarantee listing eligibility, sales velocity, offer stability, or realized profit.
CSV audit tips
Include supplier cost, pack size, and the listing URL for each row so the audit can match costs to the correct product.
Review the flagged rows first, because those are the products where an input is missing or needs verification.
Prepare a CSV that is easy to validate
For a priced catalog, include a product name column (`name`, `product`, or `title`) and a positive price column (`price` or `sellingPrice`). For a supplier batch, include a supplier cost (`supplierCost`, `supplierPrice`, `cost`, or `productCost`) and an ASIN, Walmart item ID, or supported product URL.
Keep the same number of fields in every row as in the header. Optional columns can supply marketplace, category, shipping, fulfillment, ads, referral, returns, discount, storage, hold months, inbound, and return-processing assumptions; verify configured defaults before interpreting rows with blank cost inputs.
- Audit the column names and a small sample row before loading a large catalog; the browser workflow supports up to 1,000 priced rows.
- Resolve row-number and column-count errors, then check exceptions and product identity before exporting.
- Identifier-only supplier rows still require you to open each listing and run the visible-page reader; the app does not fetch marketplace pages in the background.
Common questions
Frequently asked questions
How many catalog products can I audit at once?
The catalog workflow supports up to 1,000 priced items in the browser. The Pro plan is required for catalog and batch audits.
Does the CSV upload send supplier costs to a server?
No. Catalog data is processed locally in the browser and is not uploaded for the audit calculation.
Can an ID-only row be audited without opening its listing?
No. The batch workflow queues the identifier, then you open the product page and run the Page reader to collect visible listing details.
Can I export the catalog audit?
Yes. Catalog and supplier-batch results can be downloaded as CSV after the rows have been processed.
Is my CSV uploaded to a server?
No. The audit runs locally in your browser.
Ready to check a listing?
Put the assumptions to work.
Bring the visible listing facts and your own costs into a product audit before you commit to inventory.