Skip to main content

Import tyres from a spreadsheet

Tyre inventories usually live in an Excel sheet. ICRX imports them directly: Tyres → "Import tyre inventory".

⬇ Download the ready-made template (.xlsx) — open it, paste your sets, import.

File format​

  • File type: .xlsx or .xlsm (Excel). Plain CSV is not accepted.
  • The workbook must contain a sheet named TyresDB (this matches the classic tyre-database exports most teams already keep).
  • ICRX auto-detects the header row within the first 30 rows, and finds columns by name — column order doesn't matter.

Columns​

ColumnRequiredWhat it is
SET✅The set number. Used as the set's identity — duplicates are skipped.
FL FR RL RR✅Per-corner barcodes. Each tyre needs a distinct barcode.
TYPE—Compound: anything containing "wet" → wet; "inter" → intermediate; otherwise slick.
KM—Lifetime km so far (informational — kept in the set's notes). Under 50 km the set imports as new, otherwise used. European number formats ("1.234,5") are handled.
KO—Mark with x if the sheet flagged the set as KO. ICRX never auto-retires on import — it shows a "KO" badge for you to review.
BATCH, NOTES—Preserved into the set's notes.

How the import behaves​

  1. Pick the file ("Choose a file" or drop it on the modal).
  2. Preview — every row is classified before anything is written: Ready / Skip (existing) / Invalid, with the reason spelled out per row:
    • a row with no barcode in any corner is invalid;
    • a barcode repeated across corners or already assigned to an existing tyre is invalid;
    • a set id that already exists in your inventory is skipped, never overwritten — "re-runs are safe".
  3. Import — a progress bar runs through the ready rows; any failures are listed at the end with their exact error.

:::tip Re-import any time Because existing sets are skipped, you can re-run the import with an updated sheet after every delivery — only the new sets are added. :::

After importing​

Last updated on

Was this page helpful?