Upload a CSV file with hundreds of smartphone and PC spare parts to populate the warehouse in minutes: column mapping, SKU/EAN duplicate detection and a row-by-row error report.
When opening a new repair shop, taking over another shop's warehouse, or receiving an updated price list from a spare parts wholesaler, entering every single product by hand is simply not realistic. Bulk import lets you upload a CSV file with hundreds or thousands of smartphone spare parts, PC spare parts and accessories in a single operation, populating the spare parts warehouse in minutes instead of days of manual work.
Why it matters for a repair shop
A repair lab typically works with hundreds of different codes: displays for dozens of smartphone models, batteries of different capacities, charging connectors, protective glass, keyboards and laptop SSDs. Building this spare parts warehouse from scratch, product by product, would take days and carry a high risk of typos on prices and codes. Bulk import solves exactly this: someone opening a new shop can start from the main supplier's price list, someone with an existing spreadsheet archive can bring it into Fixh IT without losing data, and someone who periodically receives an updated catalog from a repair components wholesaler can reload it to align prices and new references without manually touching existing records.
How it works in practice
The file to upload must be CSV or TXT format, with a 20 MB maximum size per upload. After selecting the file, the system automatically reads the first row as column headers and shows a preview of the first data rows, together with an automatically suggested mapping between the file columns (e.g. "Product name", "Price", "EAN") and the Fixh IT catalog fields. You can manually correct the suggested mapping before proceeding, so even a file with non-standard headers is imported correctly.
Once the mapping is confirmed, you choose whether the system should update products already in the catalog or simply skip them: duplicate detection happens automatically by matching the SKU or EAN code in the file against those already in the product records, so the same spare part uploaded twice never creates a duplicate record. Processing then happens in batches (200 rows at a time by default), a mechanism designed to reliably handle even very large files without timeouts, showing progress in real time.
At the end, or even during processing, a summary shows how many rows were imported as new products, how many were used to update existing products, how many were skipped because they already existed, and how many were flagged as errors, for example a missing product name. Each error row lists the row number and the reason, and you can download a CSV error report to fix the original file and re-upload only the problem rows, without repeating the whole import from scratch.
Quick guide
- Prepare a CSV file with the spare parts to import: at least the product name, ideally also category, SKU, EAN, purchase price and sale price.
- Go to Warehouse > Import and upload the file (up to 20 MB, .csv or .txt format).
- Check the preview of the first rows and verify the automatic column mapping, fixing it if needed.
- Choose whether to update products already in the catalog or leave them unchanged.
- Confirm and start processing: the file is handled in batches with real-time progress.
- At the end, check the summary of imported, updated, skipped, and error rows.
- Download the CSV error report, fix the original file and re-upload only those rows if needed.
Real use cases
An owner opens a second repair shop and wants to start with the same spare parts warehouse as the main shop: they export the existing catalog to CSV and import it into the new shop, instead of manually recreating hundreds of identical product records.
A repair shop receives its repair components wholesaler's quarterly updated price list in CSV format, with new prices on displays and batteries: they upload it choosing "update existing products", so purchase and sale prices align automatically without manually editing dozens of records.
A technician managing the warehouse from an old spreadsheet decides to digitize everything into Fixh IT: they prepare a file with the required columns, upload it, review the errors flagged on a few rows with non-numeric prices, fix them, and re-upload just those few rows to complete the import.
Tips and best practices
Before importing a large file, try a small sample of 10-20 rows to verify the column mapping is correct and prices are read as numbers, not text. Always fill in SKU or EAN when available: they are the key that lets the system recognize an already-existing part and avoid duplicates on future re-imports. Keep a single consistent stock-per-shop column if you manage multiple shops, so the import distributes quantities correctly.
Common mistakes to avoid
Do not upload files with a missing product name on some rows: those are the only rows the import always discards, regardless of mapping. Avoid leaving "update existing products" off if your goal is to fix prices on a catalog already loaded previously, otherwise rows matching existing products are simply skipped. Do not ignore the error report: even an import with hundreds of correct rows can hide a few discarded rows that, left uncorrected, leave the spare parts warehouse incomplete.
Frequently asked questions
What format must the import file be? A CSV or TXT file with column headers on the first row, up to a maximum of 20 MB.
What happens if I import a part that already exists in the catalog? The system recognizes it via SKU or EAN and, if you enabled updating existing products, updates its data instead of creating a duplicate; otherwise the row is skipped.
Can I correct the automatically suggested column mapping? Yes, before confirming the import you can manually change which catalog field each file column maps to.
What do I do if some rows come out as errors? The system flags them individually with the row number and reason, downloadable as a CSV report: you can fix them in the original file and re-upload only those rows.
Can very large files cause problems or timeouts? No, processing happens in batches of rows at a time specifically to reliably handle even files with thousands of products.
Does the import also update stock for existing products? Import manages product data (name, category, prices, codes); stock is then loaded via a purchase order or a warehouse adjustment.
