CSV structure

Your catalog is one spreadsheet of SKUs. You export it from your store or ERP, upload it once, map the columns once, and the widget locks each product page to the real dimensions of the SKU being viewed.

Supported files

• CSV and TXT — comma or semicolon delimited. The delimiter is detected automatically from the first line.
• XLSX and XLS — standard spreadsheets.
• Up to 20 MB per upload.

The first row is the header. Each following row is one SKU.

How to form the CSV

You do not need to rename your store's columns to match ours. Export whatever headers your system already produces — article, sku, size, boxes per pack, and so on are all fine — and map them to Scalarcut fields in the next step (see Data mapping). The essential requirement is simply that the data you need is present somewhere in the file:

• a unique SKU code for every row, and
• the tile size in millimetres.

Everything else is optional and enriches the widget.

Required columns

Field	Notes
SKU code	The identifier your store already uses. Cart lines return this exact value, so it must match what your checkout recognises.
Size	One of the two formats below.

Size

Size can be supplied one of two ways:

• One combined column — for example 600×300, 600x300, or 600*300. Millimetres, centimetres, and metres are all accepted when the unit is written out (for example 60×30 cm).
• Two separate columns — a width column and a height column, each in millimetres.

A single combined column is the most common, since most ERPs and stores already keep size as one field.

Optional columns

Field	Notes
Name	Shown in the widget's material dropdown. Falls back to the SKU code when empty.
Thickness	Millimetres.
Pack qty	Tiles per box, so the order can be expressed as boxes. Defaults to 1 when absent.
Image URL	Public HTTPS URL to the product image. See below.
Material type	ceramic, porcelain, lvt, wood, or other. Unrecognised values map to other.
Collection	Groups products into the widget's collection picker.
ERP / 1C id	Your internal identifier, carried through for your own reporting.
Barcode	Carried through for your own systems.
Price	Optional list price for the on-screen estimate, display only.

Images stay on your servers

Scalarcut does not host your product images. The CSV holds a public HTTPS URL to each image, and the widget loads it from your CDN or storefront at render time — the file is referenced, never copied. This keeps licensing, caching, and storage entirely with you.

• The URL must be public HTTPS. An http:// or non-public URL is omitted with a warning, so the row still imports and the tile just renders without a photo.
• Update the image on your side and the widget picks up the change on the next load — no re-upload needed.

Prices are display-only

If you include prices, the widget shows them in the estimate for context. The final price is always applied by your checkout when the cart lines are added. The widget never charges a shopper.

A worked example

A minimal but complete file:

sku,name,width_mm,height_mm,pack_qty,texture_url,material_type,collection
CER-600-300,Porcelain Grey,600,300,8,https://cdn.example.com/cer-600-300.jpg,porcelain,Porcelain
LVT-1210-180,Herringbone Oak,1210,180,10,https://cdn.example.com/lvt-1210-180.jpg,lvt,Wood

The same catalog using a single size column instead:

sku,name,size_mm,pack_qty,texture_url
CER-600-300,Porcelain Grey,600×300,8,https://cdn.example.com/cer-600-300.jpg
LVT-1210-180,Herringbone Oak,1210×180,10,https://cdn.example.com/lvt-1210-180.jpg

For a complete worked file, download the sample catalog CSV — a small, realistic tile and flooring range across a few collections, in exactly the shape the importer expects.

What happens next

Upload the file in your Scalarcut dashboard and map the columns once. From then on the same headers are recognised automatically on every re-upload. See Data mapping for the mapping step and the day-to-day process for adding, editing, and removing products.