Skip to content

Product catalogue import ​

Each organisation has one default product catalogue and may have more. Every completed import replaces the selected catalogue in full — products missing from the final applied set are deleted from that catalogue only. Always upload the complete master file for that catalogue, not just the new rows.

How products are identified ​

Within one catalogue, a product's deterministic Product ID is based on its barcode + SKU + external ID combination. Import readers trim values before applying fix-up rules, and identity canonicalisation trims the transformed values again. Letter case and leading zeroes are preserved; scan normalisation isn't applied to this identity comparison.

How scanning finds a product ​

When someone scans a code, QuantalCount normalises it and searches the Inventory's catalogue using the configured slots C1 → C2 → C3. A product is eligible for C2 only when its C1 value is empty, and for C3 only when both earlier values are empty. The first layer with candidates decides the result: one candidate is a match; several candidates are ambiguous, with no fallback to a lower layer. The same code may legally appear at different layers, where the higher layer wins.

You set this order for each catalogue on the same Import Templates page.

What you can import ​

ColumnRequiredNotes
barcode, sku, externalIdAt least oneUsed to identify products; can have fix-up rules attached
nameNoOptional product name
description
category
unit
retailPrice
remark
brand, color, size, style, spec
costPrice
custom1 … custom5Free text, kept as-is

Only the identity columns are used for matching — everything else is just information.

Setting up the template (Admin) ​

Under Design Templates → Import Templates → Product catalogue, select the catalogue and configure:

  • Whether the file has a header row
  • Column mapping — at least one identity column, or uploads will be rejected

The template editor maps source columns to product fields

Uploading without a template fails with a PRODUCT_IMPORT_PROFILE_REQUIRED error.

On-site catalogue import (Supervisor) ​

An assigned Supervisor can import from the Inventory's Catalogue panel while the Inventory is Scheduled, Approved or Active. An admin must first configure the catalogue's import template and enable Allow on-site import. The import replaces the catalogue pinned to that Inventory. Supervisor writes are rejected if another Approved, Active or Closing Inventory shares the catalogue. Counters can't use this entry.

What happens after upload ​

Uploads run in the background:

  1. The file is parsed with your template.
  2. Valid, non-conflicting new and changed products are applied. Products absent from the final applied set are removed from the selected catalogue.
  3. Matching-code conflicts within the file or against current products go to the Issues queue. Those rows aren't applied and don't protect an older product from deletion. Rows repeating the same complete barcode + SKU + external ID identity are reported and ignored instead of entering the review queue.
  4. Retrying reuses the original task's parsing snapshot. Restore starts a new full replacement from a completed import's original file and parsing settings, but captures the catalogue's current match layout. It isn't a database rollback.

Uploading on the Products page — the saved template parses the file

Plan limits ​

StarterBusinessEnterprise
Products (total across all catalogues in the organisation)1,000100,0005,000,000
Rows per product-import file10,000500,0006,000,000

QuantalCount Help Centre