Import rows are refused

The check runs every row without writing anything, so a refused row costs nothing. Read the reason under Row by row, fix the file or press Change the mapping, and check again. You can also import the rest and come back for the refused ones.

Likely causes, in order

1. "... is not one of the choices for ... It can be: ...". A dropdown value in the file is not on your list. Change the file to one of the choices, or have an admin add the choice first. See A dropdown value will not save.
2. "No product with the SKU or name ... is here." A booking line names an item that is not in Inventory. Add the item, or fix the name or SKU. An import never makes a product from a line. For old orders, tick These are past bookings to keep it as a line without a product. See Import past bookings.
3. "Measure its distance before adding items." A delivery booking has no miles from the warehouse. Map a column to Miles from the warehouse, or import old orders as past bookings.
4. "More than one ... is called ...". Two records share that name. Give the email or the SKU in the file instead.
5. "A booking needs its client." Map a column to the client's name, email or contact, and fill it in.
6. "A booking needs at least one line." Map a column to Item, one row per line.
7. "The client ... is not here, and this import does not make contacts." Switch on Make the clients named in the file, or add the client first.
8. "Already here as ...". That booking came in before from the same place. An import does not change a booking that is already here; open it to change it.
9. "A ... needs a last name." Map a column to Last name, or to Name to split a whole name.

Good to know

• Rows marked Will be left are not errors: they match a record already here and Update records already here is off.
• A choice from a fixed set (a payment method, for example) matches in any capitals or spacing.
• See Import your data.