Uploading catalogs
How upload works
Upload any CSV or JSON catalog. After you choose a file, ImportPreflight shows a preview of the first rows and a column-mapping step. You map your headers to our fields for this upload.
Mapping
You must map product_name (or your equivalent). We strongly recommend description and country_of_origin (ISO-2 country codes) for solid HTS classification and UFLPA / Entity List screening. Optional fields such as supplier, manufacturer, SKU, material, and destination country improve match quality when you have them.
Mappings apply to this upload only. Saving a default mapping for your organization is planned for a later release.
File formats
The loader is chosen from the file extension. CSV and JSON are supported. For JSON, both a top-level array and an object with a products array are accepted.
SKU limits per upload
Each plan caps how many product rows you can send in one upload. If you exceed the cap, submission is rejected before storage — split the file or upgrade. See Pricing for full plan details.
| Tier | Max SKUs per upload |
|---|---|
| Free | 250 |
| Starter | 2,500 |
| Pro | 10,000 |
| Business | 50,000 |
| Enterprise | Custom (unlimited) |
There is also a 50 MB per-file size cap and monthly classification quotas per organization. If a job is rejected, check file size and remaining quota with your org admin.
Tips for better matches
Short product names and bare SKUs give the classifier little to work with. Descriptions that include material, end use, and country of origin narrow HTS and reduce false positives on regulatory screens.
Example: "Cotton T-shirt" is weaker than "Short-sleeve crew neck t-shirt, 100% cotton jersey knit, men's, HS-style goods" because the model can tie materials and use to a tighter heading.