> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/apps/business-systems/cin7-core/mappings.md).

# Mappings

How the Cin7 Core app links Cin7 customers, products, suppliers, tax rules, price tiers, and locations to OrderEazi, and how to change a link.

When a Cin7 customer or tax rule is linked to the wrong thing in OrderEazi, every order and price that follows is wrong too. The Cin7 Core app's **Mappings** tab shows how each Cin7 record and value is linked to OrderEazi, and lets you correct a link. In the app's labels, OE is short for OrderEazi.

### Before you start

Most rows are created by the syncs, so run a reference sync first, with **Sync Now** on the **Reference Data** tab. See [Master data sync](/central/apps/business-systems/cin7-core/master-data-sync.md).

### How records are linked

**Customer Mappings**, **Product Mappings**, and **Supplier Mappings** link individual records:

* **Customers:** A row is added for every Cin7 customer, except those on an excluded price tier, when the customer cache refreshes. The customer cache is the app's own copy of your Cin7 customers, refreshed every hour.
* **Products:** A row is added for every Cin7 product, linking it to the OrderEazi product with the same code as its SKU (the product code). A product with no row is sent to Cin7 under its OrderEazi code.
* **Suppliers:** A row is added for every Cin7 supplier when the supplier cache refreshes.

### How to link a record by hand

> **Note:** The customer cache rewrites a customer row's OrderEazi name with the Cin7 name each time it refreshes. Only **OE Code (optional)** is kept, so always fill it in for a customer you link by hand.

1. On the app's **Mappings** tab, find the record's row, if it has one.
2. Select its bin icon.
3. Select **OK** to confirm "Delete this mapping?".
4. In the inputs above the table, enter the OrderEazi name or code. For a customer, that's **OE Customer Name** and **OE Code (optional)**. For a product, it's **OE SKU / Code**.
5. Enter the Cin7 ID, such as the **Cin7 Customer ID** or **Cin7 Product ID**.
6. Select **Add**.

You see "Customer mapping added." (or "Product mapping added." or "Supplier mapping added."). If the row still exists, you see "A mapping for Cin7 customer '\[ID]' already exists.", with the Cin7 customer ID in place of \[ID]. For products, it's "A mapping for SKU '\[SKU]' already exists." A record mapping can't be edited: remove it and add it again.

### How reference values are linked

Under **Reference Mappings**, each Cin7 value is linked to an OrderEazi target when the reference sync runs:

* **Tax Types:** Each Cin7 tax rule is linked to the OrderEazi tax type with the same name, ignoring capitals. Tax types are never created.
* **Currencies:** Your active OrderEazi currencies are used for clients and suppliers that come from Cin7.
* **Pricelists:** Each Cin7 price tier (a Cin7 price level, such as Wholesale or Retail) is linked to the pricelist with the same name, or a new one is created. See [Pricelists](/central/order-management/pricelists.md).
* **Locations:** Each Cin7 location is linked to an OrderEazi location with the same name, or a new one is created. See [Stock and locations](/central/apps/business-systems/cin7-core/stock-and-locations.md).
* **Brands** and **Categories:** Each is linked to one with the same name, or created when missing.

The **Source** column shows **Auto** for links the sync made, and **Manual** for ones you chose. A manual link is kept on every later sync.

### How to change a reference link

1. On the **Mappings** tab, go to **Reference Mappings**.
2. In the value's **OrderEazi Target** list, choose the OrderEazi value it should use.

You see "Mapping updated.", and the row's **Source** becomes **Manual**. Choosing "not mapped" clears your link and returns the row to **Auto**, so the next sync links it again if a name matches.

To check every link against OrderEazi straight away, select **Recheck links**. You see "Reference mappings rechecked against OrderEazi.", or a list of problems, such as Cin7 locations that couldn't be created.

**Example:** Cin7's "Standard Rate" tax rule has no OrderEazi tax type with the same name, so it isn't linked. You choose **VAT 15%** next to "Standard Rate", and the row shows **Manual**. Clients created from Cin7 then get "VAT 15%", even after later syncs.

### What mappings do not do

* **Send currency to Cin7:** Sales use the Cin7 customer's own currency.
* **Change products' brands and categories:** Products take their brand and category names from Cin7, whatever their links.
* **Prevent duplicate clients:** Clients coming from Cin7 are matched by code, not by these links. See [Master data sync](/central/apps/business-systems/cin7-core/master-data-sync.md).

### Related pages

* [Master data sync](/central/apps/business-systems/cin7-core/master-data-sync.md): the syncs that create these links
* [Sales documents and statuses](/central/apps/business-systems/cin7-core/sales-documents-and-statuses.md): how links are used when a Sales Order is sent
* [Configuration](/central/apps/business-systems/cin7-core/configuration.md): exclude price tiers