ERP Import Validation
ImportCheck sits in front of your ERP importer. Validate your catalog file first, fix every error, then import a clean file — eliminating failed import runs and data corruption in production.
Why validate before importing
Most ERP catalog importers stop at the first error and roll back — or worse, silently skip invalid rows. Either way, you end up with an incomplete import and no clear indication of what went wrong.
ImportCheck runs a full scan of every row and every column, producing a complete error report before you ever touch your ERP. You fix all issues in the source file, then import once with confidence.
⏱
Save time
One fix cycle instead of repeated failed import attempts.
🛡
Protect production data
Never push a corrupted catalog to your live ERP database.
📋
Audit trail
Keep the error report as proof of data quality before go-live.
ERP compatibility
ImportCheck validates against the standard column structure used by the most common ERP catalog importers. Dedicated per-ERP templates with version-specific rules are on the roadmap.
| ERP / Platform | Import format | Status |
|---|---|---|
| Sage 100 | CSV (semicolon) | Supported |
| Sage X3 | CSV (semicolon) | Supported |
| Odoo 16 / 17 | CSV (comma) | Supported |
| WooCommerce | CSV (comma) | Supported |
| Generic catalog | CSV or Excel | Supported |
| SAP Business One | Excel / CSV | Roadmap Q3 2026 |
| Microsoft Dynamics 365 | Excel | Roadmap Q4 2026 |
Recommended workflow
Export from your source
Export the catalog from your PIM, supplier system or spreadsheet in CSV or Excel format.
Upload to ImportCheck
Upload the file on your ImportCheck dashboard. The analysis runs in under 30 seconds.
Fix all errors
Download the error report. Fix each flagged row in your source file. Re-upload until the report shows 0 errors.
Import the clean file into your ERP
Use the validated, error-free file for the actual ERP import. No surprises.
Sage-specific notes
Sage 100 and Sage X3 catalog importers use semicolons as the CSV separator and require the vat_rate column to contain the tax rate as a percentage (e.g. 20, not 0.20). Make sure your export matches this convention.
Sage exports often use the Windows-1252 encoding. ImportCheck detects this automatically, but if you see garbled accented characters in the results, re-export your file in UTF-8.
Odoo-specific notes
Odoo's native product import uses comma-separated CSV with UTF-8 encoding. The column names must match exactly (case-insensitive in ImportCheck). SKUs map to Odoo's Internal Reference field. Odoo does not accept duplicate internal references, so the DUPLICATE_SKU check is especially important here.