You can export your customers as an XLSX file. This functionality can for example be used to compile the respective customer data for a customer management system or other external systems.
Skip to:
How to export customers
The customer export consists of three phases:
- The XLSX file is being prepared and a text is informing you that the download will start in a few moments.
- After the file has been prepared, the download automatically starts if allowed by your browser. Otherwise you first need to allow the download in a pop-up window. In some browsers, you can keep track of the download at the bottom of the browser window in a status bar (e.g. in Chrome). In other browsers, the download will only be processed in the background (e.g. in Safari and Firefox).
- After the download is finished, you can open the XLSX file. It depends on your browser how to open the file. Some browsers will display a pop-up asking you if you would like to open the file (e.g. Firefox), others will add the XLSX file to a Download icon in the upper right corner (e.g. Safari), and yet others show the downloaded file in the bottom bar of the browser (e.g. Chrome).
That's how you start the export:
- In the sidebar of your cockpit, select Customers.
- In the upper right corner, select Export all customers to start the customer export. Keep in mind that the export will always include all customers of your cockpit!
You are forwarded to a new browser tab for the customer export.Note
Do not close the new tab until the XLSX file download is finished. Depending on how many customers are exported, the preparation and download of the XLSX file might take a short while. But don't worry, you can continue working in your cockpit in the other tab.
You've exported your customers and can further process the XLSX file now.
We recommend saving the XLSX file in a dedicated folder to make it easier for you to find the customer export data later on. If you would like to export your customers again, you can do so at any time. The name of the XLSX file includes the date of the export to make it easier for you to manage the different customer export files.
The structure of the XLSX file
Let's have a look at the general structure of the XLSX file. The file includes one row per customer.
The following columns are included in the XLSX file:
| Name | Description |
| The customer's email address. | |
| phone | The customer's phone number. |
| billing_address_first_name |
The customer’s first name for the billing address. This first name will also be shown on the Customer details card in your cockpit. |
| billing_address_last_name |
The customer’s last name for the billing address. This last name will also be shown on the Customer details card in your cockpit. |
| billing_address_company | The name of the company for the billing address. |
| billing_address_street | The street name for the billing address. |
| billing_address_house_number | The house number for the billing address. |
| billing_address_address_extension | Any additional address information will be displayed here. For example, if the address is a post office box. |
| billing_address_postal_code | The postcode/zip code for the billing address. |
| billing_address_dependent_locality |
The dependent locality provides additional information about the location, like e.g. the name of a village or suburb. This helps defining the location more precisely. This is only relevant for UK customers. |
| billing_address_city | The city for the billing address. |
| billing_address_country | The country for the billing address. This information is provided in the 2-letter ISO format, for example, EN, DE, FR, etc. |
| billing_address_state |
The state/province for the billing address. This is only relevant for US customers. |
| shipping_address_first_name |
The customer’s first name for the shipping address. |
| shipping_address_last_name |
The customer’s last name for the shipping address. |
| shipping_address_company |
The name of the company for the shipping address. |
| shipping_address_street |
The street name for the shipping address. |
| shipping_address_house_number |
The house number for the shipping address. |
| shipping_address_address_extension |
Any additional address information will be displayed here. For example, if the address is a post office box. |
| shipping_address_postal_code |
The postcode/zip code for the shipping address. |
| shipping_address_dependent_locality |
The dependent locality provides additional information about the location, like e.g. the name of a village or suburb. This helps defining the location more precisely. This is only relevant for UK customers. |
| shipping_address_city |
The city for the shipping address. |
| shipping_address_country |
The country for the shipping address. This information is provided in the 2-letter ISO format, for example, EN, DE, FR, etc. |
| shipping_address_state |
The state/province for the shipping address. This is only relevant for US customers. |
| customer_number |
The customer number. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored. |
| customer_origin |
The customer origin indicates how the customer was added. If this states STOREFRONT, the customer has created a customer account on your website or registered at the checkout. GUEST means that this is a customer who does not have a customer account yet and has completed the checkout as a guest. COCKPIT means the customer was added manually in the cockpit or created via a customer import. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored and the origin will be set to COCKPIT. |
| creation_date |
The date on which the customer was added. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored. |
| customer_comment |
This is an internal comment about the respective customer e.g. regarding the reliability, that you have entered. The internal comment is only visible to you. |
| grand_total_amount |
The total order amount. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored. |
| total_orders |
The total number of orders. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored. |
| last_order_date |
The date of the last order. The content of this field is generated automatically. So if you use this table to import customer data into your cockpit, this column will be ignored. |