Catalogue import (CSV)
The CSV columns Ateliq reads for products and for each store's range, the allowed values, jewellery columns, barcodes, attributes, limits and the check-then-apply flow.
You can bring your catalogue in as a CSV file, from the Catalogue tab (Import CSV). Every import is checked first: Check file shows the errors, warnings and examples of what would be created and updated, and nothing is written until you press Apply. Apply is disabled while the file has errors.
To keep the catalogue in step automatically instead, connect a source. See Catalogue sources.
The product file
Export CSV gives you the full set of columns, in this order:
sku, name, brand, category, type, colour,
metal, audience, sizes, occasions, tags,
images, list_price, currency, status,
metal_type, fineness, net_weight_g,
gross_weight_g, making_type, making_value,
stones_value, stones, hallmark, pricing,
width_mm, length_mm, attributes, barcodes,
size chart
Headers are matched without regard to case, spaces, underscores or hyphens. A column Ateliq doesn't use gives a warning ("Column 'X' isn't used"), not an error.
| Column | Required | Values |
|---|---|---|
sku | Always | Your product code, up to 64 characters. Also read from item code. |
name | New products | Up to 140 characters. |
brand | No | Up to 140 characters. |
category | New products | fashion or jewellery. |
type | New products | The kind of piece, which decides where it is tried on. See Try-on. |
colour | No | Also read from color. |
metal | No | Free text, such as "18k yellow gold". |
audience | No | women, men, unisex (the default) or kids. |
sizes | No | Separated by |, such as S|M|L. Also read from size. |
occasions | No | Separated by |. |
tags | No | Separated by |. The tag no-try-on keeps a product off try-on. |
images | No | Image addresses, separated by |. |
list_price | New products | A number, 0 or more. Also read from price and mrp. |
currency | New products | A three-letter code, such as INR or USD. |
status | No | active (the default) or hidden. |
width_mm, length_mm | No | 1 to 600. The real size of hand pieces, so they are drawn at about real size. |
attributes | No | Up to 40 facet:value pairs from the fixed vocabulary, separated by |. See below. |
barcodes | No | Up to 60, separated by ;. See below. |
size chart | No | The id of a size chart. See Size charts. |
Updates. For an existing product, only the columns in the file are updated, and a blank cell leaves the stored value as it is. The same SKU twice in one file is an error.
Jewellery columns
For jewellery only. Once any jewellery detail is given, metal_type, fineness and net_weight_g are required.
| Column | Values |
|---|---|
metal_type | gold, silver or platinum. |
fineness | A whole number from 100 to 999, such as 916 for 22K or 750 for 18K. Also read from purity. |
net_weight_g | Over 0 and up to 5,000, with up to three decimals. Also read from weight and net weight. |
gross_weight_g | At least the net weight. |
making_type | percent, per-gram or flat. |
making_value | 0 to 100 for percent; otherwise the amount. Also read from making charge. |
stones_value | The stones' value. Also read from stone price. |
stones | Up to 12, separated by |, each kind:count:carats, such as diamond:12:0.45. Kinds: diamond, polki, kundan, ruby, emerald, sapphire, pearl, cz, other. |
hallmark | BIS, BIS:<label> or other:<label>. |
pricing | fixed (the default) or metal-rate. Metal-rate pricing needs making charges. |
A stone of kind other needs a label, which a file can't carry: add or change those stones in the product editor.
Attributes
Attributes come from a fixed vocabulary, so the stylist, the agents and your reports all use the same words.
- Fashion: garment, silhouette, neckline, sleeve, length, fabric, craft, pattern, colour.
- Jewellery: piece, metal colour, stone, craft, motif, style.
- Both: occasion.
Write each as facet:value, such as neckline:v-neck|fabric:silk. Facets that take one value accept only one. The Cataloguer agent can suggest attributes from your photos for a person to accept.
Barcodes
Each barcode is code or code:size. A GTIN (EAN-8, UPC-A, EAN-13, GTIN-14, or an expanded UPC-E) must have a valid check digit. Anything else is treated as your own store code: 1 to 32 characters from A to Z, 0 to 9 and . _ / -. A barcode's size must be one of the product's sizes, and the same code can't be on two products. Shoppers and staff scan these at the screens.
The store range file
From the Assortment tab, import each store's range with these columns:
| Column | Values |
|---|---|
sku | The product. |
carried | true/false, yes/no, y/n or 1/0. |
price | The store's own price. |
stock | S:2|M:3, or one number. Also read from qty and quantity. |
location | Where the piece is in the store. |
visible | true/false, yes/no, y/n or 1/0. |
You can also give stock one row per size, with the columns sku, size, qty. Store managers can change only stock, visibility and location.
Limits
- Files up to 5 MB and 50,000 rows.
- The check lists up to 500 errors, each with its row number.
- Exports start with a UTF-8 byte-order mark, so spreadsheets read accents and symbols correctly, and are protected against spreadsheet formula injection.
Something missing or unclear? Write to pb@ateliq.co and we will answer and fix this page. Last reviewed 12 November 2026.