> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudify.biz/llms.txt
> Use this file to discover all available pages before exploring further.
# Customer Sync settings
## Setting Up Customer Sync Preferences
### Customer Match Rule
Define how customers are matched between Shopify and Tripletex. Select a **Shopify field** and the **Tripletex field** it should be matched against. The integration uses this pairing to check whether a customer already exists in Tripletex — a new customer is created only when no match is found, which prevents duplicates.
Where possible, match on a field that is unique per customer to keep duplicates out.
Ensure the selected Shopify field is not empty on your orders. An empty match field will trigger sync errors.
**Default Customer for POS Orders (Optional)** — Enable **Use a Default Customer for Point of Sale (POS) Orders** if you process in-person sales. When a Shopify POS order doesn't have a customer assigned, the integration automatically creates a customer named **POS Customer – Cloudify** in Tripletex and uses it for all POS invoices where no customer information is available.
***
### How Should Customer Data Fields Be Mapped?
Specify how Shopify customer data maps to Tripletex fields. This controls how customer information is transferred when a customer is created or updated in Tripletex. Some common fields — such as **Name** and **Telephone** — are pre-mapped for you.
* To change a mapped field, click its box and select your preferred Shopify field.
* To remove a mapping, click **Clear**.
* To map a fixed value instead of a Shopify field, click **Use Text** and enter the value.
* Click **Create new Shopify field** to add a mapping that isn't listed.
Fields are grouped across tabs — **General**, **Postal address**, **Invoice settings**, **Business address**, **Delivery address**, and **Additional**. The **Status** column shows whether each field is **Mapped** or **Not mapped**.
**Name** is required. Map all relevant customer fields before going live to avoid incomplete customer records being created in Tripletex.