ParcelPilot
Help

CSV Importer

Use CSV Importer on the Items page when you need to add new local Item master records from a spreadsheet.

This is separate from ecommerce Pull Products and separate from the existing Item Master CSV update flow. It is create-only: rows for SKUs that already exist are rejected and should be handled by the update/export workflow instead.

What this creates

  • Item master records for the selected tenant/client scope.
  • Basic product fields such as SKU, name, barcode, customer identifiers, VAT code, weights, dimensions, planning fields, and customs product data.
  • Item attributes such as customer SKU/name fields, dimensions, case pack details, Amazon ASIN, HS code, and country of manufacture.

What this does not create

  • Ecommerce product or variant identities.
  • Item external mappings.
  • Inventory units, stock balances, reservations, stock movements, warehouses, or locations.
  • Warehouse notification emails.

Workflow

  1. Go to Items.
  2. Click Download CSV Template.
  3. Fill in the CSV. Use Client ID only when an internal user needs to create rows for more than one client; otherwise choose a Default Client during upload.
  4. Click CSV Importer, choose the Default Client and CSV file, then click Preview Import.
  5. Review the Import Preview inside the modal. It shows the file name, rows checked, items ready to create, and rows with errors.
  6. If at least one row is valid, click Create 1 Item or Create N Items in the same modal.

Uploading the CSV only validates it. Items are created only when you confirm the preview.

If no rows are valid, the create action is not available. Fix the CSV and preview it again.

Validation rules

  • SKU and Name are required.
  • SKUs must be unique across the tenant. A SKU already used by another client in the same tenant is rejected.
  • Client ID is optional when a Default Client is selected. Internal users may use Client ID for mixed-client imports inside their permitted scope.
  • Client is only a display-name check when Client ID is present. It is not used as the identity for the target client.
  • Client users are locked to their own client.
  • Rows with populated ecommerce identity columns, inventory quantity columns, location columns, or internal IDs are rejected.
  • Valid rows can still be created when other rows fail validation. Failed rows are skipped and included in the error report.

Related guides