> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duitpos.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Import History
> Review the results of past CSV bulk imports.
**Import History** shows a log of all bulk CSV imports performed on your account — products, categories, bulk pricing, and more. Use it to verify that an import completed correctly and to diagnose any rows that failed.
## What It Shows
Each row in the Import History represents one import job:
| Column | Description |
| ------------ | --------------------------------------------------------------------------------- |
| **Date** | When the import was run |
| **Type** | What was imported: Products, Categories, Bulk Pricing, Employees, etc. |
| **Filename** | The name of the CSV file that was uploaded |
| **Rows** | Total rows in the uploaded file (excluding the header row) |
| **Imported** | Rows successfully created or updated |
| **Skipped** | Rows that were skipped because the data was already up to date (no change needed) |
| **Failed** | Rows that failed validation or encountered an error |
| **Status** | Overall result: Completed, Completed with errors, or Failed |
## Import Statuses
| Status | Meaning |
| ------------------------- | -------------------------------------------------------------------------------------- |
| **Completed** | All rows were processed successfully — no failures or skips |
| **Completed with errors** | Some rows were imported but one or more failed. Review failed rows before re-importing |
| **Failed** | The import could not run at all (e.g. file format error or system error) |
| **Processing** | The import is still running — refresh the page after a few seconds |
## View Errors
Click any import row to expand the details. Failed rows show the specific validation error, for example:
* *"Product code not found"* — the product code in the file does not exist in the system.
* *"Price must be a number"* — the price column contains text or an invalid format.
* *"Category is required"* — the Category field was left blank for a product row.
Download the error report from the import detail page. It is a CSV file with the original row data and the error message added as an extra column — making it easy to find and fix the problems without having to search the original file manually.
## Re-importing
Fix the errors in your CSV file and upload again via the bulk import button on the relevant page (e.g. **Products → Import**). You only need to include the corrected rows — successfully imported rows do not need to be re-uploaded.
## Frequently Asked Questions
The importer accepts CSV files (comma-separated values) with UTF-8 encoding. Download the template from the relevant import page (e.g. Products → Import → Download Template) to ensure your file uses the correct column names and format.
Check two things: (1) In Import History, confirm the import Status is Completed and the Imported count matches the number of rows you expected. (2) Check that the imported products have **Active** set to true in your CSV. Products imported as inactive will not appear on the POS.
There is no bulk undo. If you need to reverse an import, you will need to manually edit or delete the records that were created. For large accidental imports, contact your administrator.
Import history is retained indefinitely for as long as your account is active. You can review any past import at any time.
## Related
Manage products and bulk import menu items
Import category data
Import price overrides in bulk
View sales and transaction analytics