See what each field/column from our “Customers” template means including possible allowed values and examples.
Fields marked as “Export Only” cannot be imported/set in Shopify but can be exported with Matrixify export.
Customers
When importing a file, to tell the app that you are importing Customers, you need to ensure that the sheet/tab name is set to “Customer” or “Customers”.
For example:
Even if the sheet/tab name is not set correctly, you will be able to manually change and set the entity you are importing after uploading file in the app.
See more on the Matrixify app import process and import user interface.
| Column | Description / Example Value |
|---|---|
| ID | ID is automatically generated number by Shopify to identify the item.It is filled in by an Export.Can be used for Import to identify and update existing Customers.When creating new Customers, leave this value empty. |
Allowed Values Number Example
44920047631 |
| Email | Customer primary e-mail address.
If the store is configured to require Customer login, then this will be the username.
Email must be unique in this Store, which means that each e-mail can be used only once in this column across the Store. When customer puts an order and has e-mail filled, that e-mail is used to identify to which customer the order will be assigned.
Email can be empty if First Name is filled.
Email is used as the secondary way to identify customers and to check if they already exist. In the import results the Email field can also be called “Handle” (as for all other items secondary identifiers).
Allowed Values
Email Address
Example
you@somemain.com |
| Command | When importing Customer row – tell the app, what to do with it:
• NEW: will try to create a new Customer with the provided details. If such Customer will already exist (with the same ID or same Email), then the result will be Failed.
• MERGE: will try to find existing Customer, and update it with data from the row. If such Customer will not be found, then it will create new.
• UPDATE: the app will search for an existing Customer and update it. If an customer cannot be found then it will fail to import.
• REPLACE: WARNING! Use this Command value to fully replace the whole customer, not individual fields. Using this Command value, the app will delete the customer from the store completely and create a new one only from data in the file, resulting in losing all data that is not included in the import file.If such Customer with provided ID or Email exists, then the app will delete it. After that, it will create a new one. If an existing Customer will not be found, then still the app will create a new one. The difference from UPDATE is that it will not keep any of columns, which were not included in the import file since the Customer will be deleted and re-created.
• DELETE: the app will delete the existing Customer, which is found by ID or Email. If such Customer will not be found, then the result will be Failed. This DELETE command is very handy for deleting Customers in bulk.
• IGNORE: the app will ignore this Customer and will skip it.
If no Command is specified, then the app will assume the MERGE command.
Allowed Values
NEW MERGE UPDATE REPLACE DELETE IGNORE
Example
MERGE |
| First Name | The first name of the Customer.
First Name can be empty if Email is filled.
If Address First Name is not filled for the address, then Matrixify will use the value of this column for the address.
Allowed Valuesd
Text
Example
John |
| Last Name | The last name of the Customer.
If Address Last Name is not filled for the address, then Matrixify will use the value of this column for the address.
Allowed Values
Text
Example
Smith |
| Phone | Phone number must be complete – with the country code and must be valid for the respective country.
The phone number must be unique – Shopify allows one phone number to belong to only one Customer. Shopify uses the phone number to identify to which customer to assign the order – in case the customer doesn’t have the e-mail.
When importing Customers, if ID and/or Email columns are empty or not in the import file, then the Matrixify app will identify existing customers by the Phone number.
You can prefix phone numbers with ‘ (apostrophe) to allow Excel to show the + (plus) sign. But the + (plus sign) is not required.
You should set the phone number in the following format: +1 234567890. Make sure to include the country code (in this case, +1). It is not mandatory to use a space or dash to separate the country or regional codes from the rest of the phone number, but it can help Shopify API to better detect country code used in the phone number.
If Address Phone is not filled for the address, then Matrixify will use the value of this column for the address.
Allowed Values
Phone Number
Example
'+15417543000 |
| Language | Customers’ language locale. The customer will receive notifications in this language.
You can set any value in this field, but if it is not a valid 2-character ISO language code, then in Shopify the Language will show as the default value.
Importing or having this column empty means that Customers Language is set to the default value.
The language needs to be set up in Admin -> Settings -> Languages section to be able to assign it to the Customer.
Allowed Values
2-character ISO language code
Example
en |
| State
Export Only | The Customer status – one of those:
• disabled: customers are disabled by default until they are invited.
• invited: the customer has been emailed an invite to create an account.
• enabled: the customer accepted the email invite and created an account.
• declined: the customer declined the email invite to create an account. If Customer has declined your invitation, you cannot generate new Account Activation URL.
The state is always “calculated” from the actions that are done with this Customer. When you import it, it will always be “disabled” at the beginning.
If you send the invitation (or import the “Send Account Activation Email” column as TRUE), then the State will be “invited”.
Allowed Values
disabled invited enabled declined
Example
disabled |
| Email Marketing: Status | Whether Customer accepted that he can be sent marketing e-mails.
Allowed Valuesinvalid – The customer’s email address marketing state is invalid.not_subscribed – The customer hasn’t subscribed to Email marketing. The value can only be set when creating a new Customer. To unsubscribe a Customer which has a different Email Marketing Status, use value unsubscribed.pending – The customer is in the process of subscribing to Email marketing.redacted– The customer’s personal data is erased. This value is internally-set and read-only.subscribed – The customer is subscribed to Email marketing.unsubscribed – The customer isn’t currently subscribed to Email marketing but was previously subscribed.
Example
subscribed |
| Email Marketing: Level | The Email marketing subscription opt-in level, as described by the M3AAWG best practices guidelines, that the customer gave when they consented to receive marketing material by email.
When creating new customer, if no Marketing Level is specified app will assume it as single_opt_in which is also the default value in Shopify.
Allowed Values
confirmed_opt_in– After providing their information, the customer receives a confirmation and is required to perform a intermediate step before receiving marketing information.
single_opt_in– After providing their information, the customer receives marketing information without any intermediate steps.
unknown– The customer receives marketing information but how they were opted in is unknown.
Example
single_opt_in |
| Email Marketing: Updated At | The date and time when the customer consented or objected to receiving marketing material by email.
Can be imported.
Allowed Values
Date & Time
Example
2018-12-17 18:20:07 +0200 |
| SMS Marketing: Status | Whether Customer accepted that he can be sent marketing SMS.Current SMS marketing state for the customer.Updating customer SMS Marketing Status:
• SMS Marketing Status can only be updated if the current SMS Marketing Status is not_subscribed .
• Customer cannot update to redacted SMS Marketing Status.
• Customer can only be updated to pending SMS Marketing Status in combination with confirmed_opt_in SMS Marketing Level.
Creating customer:
• Customer cannot be created with redacted SMS Marketing Status.
• Customer can be created withpending SMS Marketing Status only in combination with confirmed_opt_in SMS Marketing Level.
• Creating customers with not_subscribed SMS Marketing Status will always set SMS Marketing Level to single_opt_in no matter what is specified in the import file.
• Other SMS Marketing Status and Level combinations should work when creating customer.
Allowed Valuesnot_subscribed – The customer hasn’t subscribed to SMS marketing.pending – The customer is in the process of subscribing to SMS marketing.redacted– The customer’s personal data is erased. This value is internally-set and read-only.subscribed – The customer is subscribed to SMS marketing.unsubscribed – The customer isn’t currently subscribed to SMS marketing but was previously subscribed.
Example
subscribed |
| SMS Marketing: Level | The SMS marketing subscription opt-in level, as described by the M3AAWG best practices guidelines, that the customer gave when they consented to receive marketing material by SMS.
Allowed Values confirmed_opt_in– After providing their information, the customer receives a confirmation and is required to perform a intermediate step before receiving marketing information. single_opt_in– After providing their information, the customer receives marketing information without any intermediate steps. unknown– The customer receives marketing information but how they were opted in is unknown. Example
single_opt_in
**** |
| SMS Marketing: Updated At | The date and time when the customer consented or objected to receiving marketing material by sms.
Can be imported.
Allowed Values
Date & Time
Example
2018-12-17 18:20:07 +0200 |
| SMS Marketing: Source
Export Only | The source that collected the customer’s consent to receive marketing materials by SMS.
Allowed ValuesOTHER – The customer consent was collected outside of Shopify.SHOPIFY – The customer consent was collected by Shopify.
Example
SHOPIFY |
| Created At
Export Only | It will be set automatically when Customer is created. Allowed Values Date & Time Example
2018-12-17 18:20:07 +0200 |
| Updated At
Export Only | It will be automatically updated, whenever the Customer data is changed. Allowed Values Date & Time Example
2018-12-17 18:20:07 +0200 |
| Note | Whatever is written on the Customer card, accessible from Shopify Admin.
Allowed Values
Text
Example
Your notes go here. |
| Verified Email
Export Only | Tells, whether Customer e-mail is validated.
Is set to TRUE, when Customer received the confirmation e-mail and pressed the confirmation link.
This value can also be imported, when creating new Customer.
By default, the value will be FALSE.
Allowed Values
TRUE FALSE
Example
TRUE |
| Tax Exempt | Whether the customer is exempt from paying taxes on their order.
If TRUE, then taxes won’t be applied to an order at checkout.
If FALSE, then taxes will be applied at checkout.
Allowed Values
TRUE FALSE
Example
TRUE |
| Tags | Tags allow you to add additional elements or “properties” to your Customer, which you can use for filtering, for developing some additional logic for those Customers in your Store Theme.
See this tutorial on how to bulk manage your Tags.
Allowed Values
Comma Seperated List
Example
Friend, Migrated |
| Tags Command | Tell the app, what to do with Tags:
• MERGE: will add Tags to existing tags. It means that you don’t need to list all the tags in the import file, you can import those which you want to add. If some of the tags you are importing already exist, then the app will ignore it.
• DELETE: will delete the Tags that are listed in the import file. If the listed tag will not exist, then the app will ignore it.
• REPLACE: will replace all existing tags with the tags from the import file. Use this method to maximize the import speed, because if you will use MERGE, it means that the app will need first to load existing tags which takes additional time.
You can also have Tags listed in multiple rows within the item and with different Tags Commands.
They will be executed in the same order within the item as you have them listed in the file.
If Tags Command is not set, the app will assume the MERGE command by default.
See this tutorial on how to bulk manage your Tags.
Allowed Values
MERGE DELETE REPLACE
Example
REPLACE |
| Total Spent
Export Only | The total amount of money this Customer has spent, calculated from actual Orders in the Store. It is exported even when “First and Last Order” checkbox is not checked because the data is available always. Example
48234.93 |
| Total Orders
Export Only | The total number of orders this Customer has purchased. It is exported even when “First and Last Order” checkbox is not checked because the data is available always. Example
5 |
| Send Account Activation Email | This column can only be imported.
If you will set this to “TRUE”, then as soon as Customer will be imported, she will receive a default invitation e-mail from Shopify to activate the account – the same one as she would get if you press the “Send account invite” in the Admin from Customer page.
When migrating Customers, you might want Shopify to send out invitations to activate migrated accounts in bulk. Then set this to TRUE when importing. This can be used as smooth migration experience for Customers if you don’t want to send your own mass-mailing with Account Activation URL links.
When the value is left empty, it is considered to be FALSE, so invitations will not be sent.
You can send those activations also to your existing Shopify Customers, just do the export, and then import back as an update, with this value set to TRUE.
Allowed Values
TRUE FALSE
Example
TRUE |
| Send Welcome Email | This column has been removed and is no longer supported by Shopify. Shopify no longer allows triggering welcome email to Customers. |
| Password | This column has been removed and is no longer supported by Shopify. Shopify no longer allows setting and assigning a password to a customer. |
| Multipass Identifier | Available only for Shopify Plus stores.
Allows setting the identifier of the Multipass login.
Read more information about Multipass.
Allowed Values
Text
Example
bob123 |
Those columns are only exported.
| Column | Description / Example Value |
|---|---|
| First Order: ID |
Export Only | ID of the first Order of this Customer. Example
2387462873468 |
| First Order: Name
Export Only | Name of the first Order of this Customer. Example
#12345 |
| First Order: Processed At
Export Only | Date and time of the first Order of this Customer. For imported Orders, this will be the processed date, not the date when the Order was imported. Date and time will be in the format which is recognized as Excel time. Example
2018-12-17 18:20:07 +0200 |
| First Order: Price Total
Export Only | The total price of the first Order of this Customer. This is not the actually paid amount, it is the Total of the Order itself. Example
999.99 |
| Last Order: ID
Export Only | ID of the last Order of this Customer. If Customer has only one order, then this will be the same as the first Order. Example
2387462873468 |
| Last Order: Name
Export Only | Name of the first Order of this Customer. If Customer has only one order, then this will be the same as the first Order. Example
#12345 |
| Last Order: Processed At
Export Only | Date and time of the first Order of this Customer. For imported Orders, this will be the processed date, not the date when the Order was imported. Date and time will be in the format which is recognized as Excel time. If Customer has only one order, then this will be the same as the first Order. Example
2018-12-17 18:20:07 +0200 |
| Last Order: Price Total
Export Only | The total price of the first Order of this Customer. This is not the actually paid amount, it is the Total of the Order itself. If Customer has only one order, then this will be the same as the first Order. Example
999.99 |