Skip to content

Import contacts, products, orders and tickets

Last updated November 1, 2026

Before you start

  • You need a CSV or Excel (.xlsx) file with the column names in the first row. Bangla text is fine.
  • Choose Import on the page you are filling: Contacts, Products, Orders or Tickets. You need the permission to import there (for example Import and export on Products and Orders).
  • Choose Download template in the first step to get a file with the column names we read, plus example rows.
  • One file can have up to 5,000 rows and 10 MB. Your team can change these limits.

Steps

  1. Choose Import, then drop your file or choose it from your computer.
  2. Match your columns. We match each column of your file to a field. A chip shows how sure we are: Exact and Alias are names we know, Close is a similar spelling, AI is a suggestion. For the AI suggestion we only look at the column names of the columns we could not place and up to three sample values in each, never the whole file. Change any match with the dropdown. Fields you must match are highlighted.
  3. Review. We check every row before anything is saved. Rows with a problem are listed with the reason. Click a cell to fix it, or leave the row out. Nothing is written yet.
  4. Choose what happens to duplicates. Pick Skip (leave the existing record as it is), Update existing (fill in what the file has) or Create new (add another record next to it; not available for contacts, because a phone belongs to one contact).
  5. Choose Import. A progress bar shows how it is going. You can close the panel; the import keeps running.
  6. When it ends you see how many were created, updated, skipped and failed. Choose Download errors to get a file with only the rows that did not import and the reason for each. Fix it and import it again.

How duplicates are found

  • Contacts: your own ID column, then phone, then email.
  • Products: your own ID column, then SKU, then handle.
  • Orders: your own ID column, then order number.
  • Tickets: your own ID column. Importing the same file again with the same IDs never creates the same ticket twice.

Products with variants

Use one row per variant, like a Shopify product export. Rows with the same Handle are one product. Put the option names (for example Size) and values (M, L) in the option columns, with a price, SKU and stock on each row. The first row of a product holds its title, description and category. We create every combination of the option values, so a combination you left out starts at the product price with no stock.

Orders

Rows with the same order number are the lines of one order. Prices always come from your catalog and delivery fees from your zones, never from the file. Each item is matched by SKU, then by product name (use Name / Variant for a variant). An item that matches nothing fails that order with a clear reason, and the other orders still import.

Undo

For 7 days after an import finishes, open Import history and choose Undo.

  • Records the import created are removed. Products are archived, orders are cancelled and contacts are removed.
  • Records the import updated get their old values back.
  • A record that has moved on since (a contact who has ordered, an order that is already booked) stays, and the summary tells you how many.

Good to know

  • Every record is made by the same rules as when you add it by hand, so limits, stock checks and the audit trail all apply.
  • Starting the same import twice runs it once.
  • Importing tickets does not ring the bell for each row.

Still need help?

Tell us what you are trying to do and a person will reply by email.

Contact us