Fix import errors

After an import, RABT lists every row it could not import, with the row number, the column and the problem. Fix the file and import it again. For sales history, orders that were already imported are skipped, so re-running is safe.

Common problems

• Required value missing — a required column is empty in this row.
• No customer with this exact name — the name does not match any customer in RABT. Customers are not created automatically: check spelling and spaces, or import or add the customer first.
• More than one customer has this exact name — rename one in RABT so each name is unique.
• No product with this SKU — import or add the product with this SKU first.
• Date must be YYYY-MM-DD — for example 2026-03-15. Excel may have changed the date format; format the column as text or as that date format before saving.
• Quantity must be above zero, up to 4 decimals.
• Unit price must be a number, up to 4 decimals — remove currency symbols and thousands separators.
• Too many decimals for this currency — round the price to the currency's decimals.
• Currency not supported — use a standard code such as AED, SAR or USD.
• Rows of this order disagree on date, customer, currency or VAT — every line of one order must share these.
• More than 200 lines in one order, or more than 500 orders in one file — split the file.

If Arabic text looks wrong

The file was not saved as UTF-8. Save it again as CSV UTF-8.

Nothing imported at all

Check that the required columns are mapped on the Map columns step.