Skip to Content
ProductTRADE Quick Start

TRADE Quick Start

Use this when you want the shortest path from product data to classification review and broader trade workflows.

1. Start with the right TRADE surface

Use /trade/upload when you want to:

  • upload a CSV or spreadsheet-derived catalog extract,
  • run preview classification before committing to a full import,
  • review a completed preview job from the same browser session, or
  • reopen a recent classification from Jobs using View Classification.

Use /trade/feeds/upload or the Upload Large Feed CTA on /trade when you have:

  • large files,
  • attribute-row feeds,
  • messy supplier exports, or
  • anything that should be normalized server-side before preview.

Use /trade for smaller ad hoc classification and landed-cost checks when you are not starting from a batch file.

Note: If server-side feed profiling is unavailable, /trade/upload falls back to the interactive wizard with a visible warning. This is graceful degradation, not an error.

2. Run preview classification first

  1. Open /trade.
  2. Choose Upload SKU Data for smaller clean files, or Upload Large Feed for large or messy feeds.
  3. Upload a representative product file.
  4. Review the preview summary before committing to a broader upload.
  5. If the job takes time, use View in Jobs to monitor progress.

Preview jobs are async. The intended operator path is:

  • same browser session: return to /trade/upload and continue review/upload,
  • different browser or expired session: reopen the job from Jobs and rerun the upload if you need a fresh review context.

3. Review and clean up the results

Day-one goal:

  • verify that your descriptions are specific enough to produce usable classification output,
  • identify obvious low-confidence or unclassified rows,
  • confirm the team reviewing the output understands what must be escalated.

4. Move into the full TRADE workflow

After preview review:

  1. Upload the broader catalog or batch file.
  2. Review HS suggestions and evidence.
  3. Check SIMA exposure and related evidence where relevant.
  4. Use obligation workflows for jurisdiction-specific requirements.
  5. Export or capture the reviewed output you need downstream.

5. What to capture every session

Keep these for support and validation:

  • preview job IDs,
  • uploaded file name,
  • row and SKU counts,
  • any low-confidence or unclassified patterns,
  • exact error payloads when uploads or previews fail.
SHIP FAQTRADE Guide