> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/cin7.md).

# Cin7

Sync Cin7 inventory, sales, purchases, and customer data into Google Sheets, BigQuery, or Excel via Coupler.io.

Cin7 is a cloud-based inventory management and point-of-sale platform that helps product businesses manage stock, orders, suppliers, and sales across multiple channels. It combines inventory control, order management, and financial tracking in one place. Connecting Cin7 to Coupler.io lets you pull that data into your reporting and analytics tools automatically.

**Why connect Cin7 to Coupler.io?**

* Sync sales, purchases, inventory, and customer data into Google Sheets, BigQuery, Excel, or Looker Studio without manual exports
* Combine Cin7 entities — for example, join Sales with Products to analyze revenue by SKU, or Append purchase records across multiple accounts
* Send Cin7 data to AI destinations like ChatGPT, Claude, or Gemini for demand forecasting, supplier analysis, or sales commentary
* Keep dashboards and reports up to date on a schedule without touching Cin7

## Prerequisites

Before connecting, make sure you have:

* A Cin7 account with API access enabled (available on most paid plans)
* Your Cin7 **API Username** and **API Key** — find these in Cin7 under **Settings > Integrations > API**
* Sufficient permissions to access the entities you want to export (e.g., sales, purchases, inventory)

## Quick start

{% hint style="success" %}
If you want a broad view of your inventory and sales performance, start by adding the **Sales**, **Products**, and **Product availabilities** entities in a single data flow. Use the Join transformation to combine them by product ID.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account, go to **Data flows**, and click **Add data flow**. Search for **Cin7** and select it as your source.
{% endstep %}

{% step %}
**Enter your Cin7 API credentials.** In the source settings, paste your **API Username** and **API Key**. You can find these in Cin7 under **Settings > Integrations > API**. Click **Save**.
{% endstep %}

{% step %}
**Select the entity you want to import.** Choose from the list of available entities — such as Sales, Products, Customers, or Purchase lists. Each entity is a separate source block; add more source blocks to the same data flow if you need multiple entities.
{% endstep %}

{% step %}
**Choose your destination.** Select where you want your data to land — Google Sheets, BigQuery, Excel, Looker Studio, or an AI destination like ChatGPT or Claude. Configure the destination settings.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync and verify the data looks correct before setting up a schedule.
{% endstep %}
{% endstepper %}

## Cin7 data overview

Cin7 exposes a wide range of operational and financial data through Coupler.io. You can pull everything from live stock levels and product catalogs to sales transactions, purchase history, supplier details, and your chart of accounts.

## Available entities

| Entity                 | What it contains                                                       |
| ---------------------- | ---------------------------------------------------------------------- |
| Accounts               | Chart of accounts, account types, and financial codes                  |
| Bank accounts          | Bank account names, numbers, and currency details                      |
| Attribute sets         | Product attribute group names and configurations                       |
| Brands                 | Brand names, codes, and identifiers                                    |
| Carriers               | Carrier names, tracking methods, and service types                     |
| Customers              | Names, contact details, billing/shipping addresses, and account status |
| Deals                  | Deal names, values, associated contacts, and stage                     |
| Leads                  | Lead source, contact info, status, and assigned owner                  |
| Locations              | Warehouse names, addresses, and location codes                         |
| Opportunities          | Pipeline stage, estimated value, close date, and linked account        |
| Product availabilities | Stock on hand, available quantity, and location breakdown              |
| Product categories     | Category names, parent categories, and hierarchy                       |
| Product families       | Family names and linked product groupings                              |
| Products               | SKUs, barcodes, descriptions, pricing, cost, and inventory levels      |
| Purchase lists         | PO numbers, supplier, line items, quantities, and status               |
| Purchases              | Purchase dates, supplier, amounts paid, and payment status             |
| Sale lists             | Order numbers, customer, line items, quantities, and order status      |
| Sales                  | Sale dates, customer, revenue, cost, and margin data                   |
| Suppliers              | Supplier names, contact details, payment terms, and lead times         |
| Taxes                  | Tax code names, rates, and applicability                               |

## Metrics and dimensions

#### Sales and revenue

| Field          | Description                                     |
| -------------- | ----------------------------------------------- |
| Sale date      | Date the transaction was recorded               |
| Total amount   | Total sale value including tax                  |
| Sub-total      | Revenue before tax                              |
| Tax amount     | Tax charged on the sale                         |
| Cost of goods  | Total COGS for the sale                         |
| Margin         | Gross profit on the transaction                 |
| Payment status | Whether the invoice is paid, unpaid, or partial |
| Order status   | Current status of the sale order                |
| Customer       | Customer linked to the transaction              |
| Channel        | Sales channel (e.g., B2B, POS, e-commerce)      |

#### Inventory and products

| Field              | Description                                  |
| ------------------ | -------------------------------------------- |
| SKU                | Stock keeping unit identifier                |
| Barcode            | Product barcode                              |
| Product name       | Full product description                     |
| Buy price          | Cost price of the product                    |
| Retail price       | Listed retail price                          |
| Quantity on hand   | Current stock level                          |
| Available quantity | Stock available to sell (excluding reserved) |
| Location           | Warehouse or bin location                    |
| Category           | Product category classification              |
| Brand              | Brand associated with the product            |

#### Purchases and suppliers

| Field         | Description                        |
| ------------- | ---------------------------------- |
| PO number     | Purchase order identifier          |
| Supplier      | Vendor name                        |
| Order date    | Date the PO was raised             |
| Expected date | Expected delivery date             |
| Total cost    | Total purchase value               |
| Payment terms | Agreed payment terms with supplier |
| PO status     | Draft, approved, received, etc.    |

#### CRM (Leads, Deals, Opportunities)

| Field           | Description                         |
| --------------- | ----------------------------------- |
| Lead source     | How the lead was acquired           |
| Status          | Current lead or deal status         |
| Estimated value | Projected deal or opportunity value |
| Close date      | Expected or actual close date       |
| Assigned to     | Sales rep or owner                  |
| Contact details | Email, phone, and company           |

## Common metric combinations

* **Sales + Products** (joined on SKU) — analyze revenue, margin, and COGS by product
* **Product availabilities + Locations** (joined on location ID) — see stock levels per warehouse
* **Purchases + Suppliers** (joined on supplier ID) — track spend and lead times by vendor
* **Sale lists + Customers** (joined on customer ID) — build a customer order history report
* **Leads + Opportunities** (appended or joined) — create a full CRM pipeline view

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* Export **Sales** and **Accounts** into BigQuery or Google Sheets to reconcile revenue against your chart of accounts
* Pull **Purchases** and **Suppliers** to track outstanding payables and supplier spend trends
* Use **Taxes** data to verify tax codes applied across transactions
* Send financial summaries to ChatGPT or Claude for automated commentary on monthly P\&L
  {% endtab %}

{% tab title="Inventory managers" %}

* Sync **Product availabilities** on a frequent schedule to keep stock level dashboards current in Looker Studio
* Join **Products** with **Product availabilities** to flag low-stock SKUs by location
* Pull **Purchase lists** to monitor open POs and expected stock arrivals
* Use **Product categories** and **Product families** to group stock reports by segment
  {% endtab %}

{% tab title="Sales teams" %}

* Export **Sales** and **Sale lists** to track order volume, revenue, and fulfilment status
* Use **Leads**, **Deals**, and **Opportunities** together (Append or Join) to build a unified CRM pipeline report
* Join **Customers** with **Sales** to identify top buyers and repeat purchase rates
* Send pipeline data to Gemini or Perplexity for AI-assisted forecasting
  {% endtab %}

{% tab title="Operations" %}

* Pull **Locations** and **Carriers** to monitor fulfilment routes and warehouse activity
* Join **Sale lists** with **Products** to identify which SKUs are moving fastest per channel
* Use **Suppliers** data to maintain an up-to-date vendor directory in Google Sheets
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Cin7 API access is typically available on Business and Enterprise plans — check your subscription if the connection fails
* The **Product availabilities** entity reflects real-time stock levels; for point-in-time snapshots, set up scheduled refreshes and store historical runs
* **Sale lists** and **Sales** are separate entities — Sale lists contain order line-item detail, while Sales contains the transaction-level summary
* **Purchase lists** and **Purchases** follow the same pattern — use both if you need line-item and transaction-level purchase data
* CRM entities (Leads, Deals, Opportunities) are only populated if you use Cin7's built-in CRM module

## Cin7 common issues

### Connection issues

<details>

<summary>My API credentials are rejected during setup</summary>

Double-check that you're using the **API Username** and **API Key** from Cin7, not your regular login email and password. Find them in Cin7 under **Settings > Integrations > API**. Make sure there are no extra spaces when copying the key.

{% hint style="warning" %}
Some Cin7 plans restrict API access. If the API section isn't visible in your settings, contact Cin7 support to confirm your plan includes API access.
{% endhint %}

</details>

<details>

<summary>The connection was working but has suddenly stopped</summary>

Cin7 API keys can be regenerated or deactivated. Log in to Cin7, go to **Settings > Integrations > API**, and check whether your key is still active. If it was regenerated, update the credentials in your Coupler.io data flow source settings.

</details>

### Missing data

<details>

<summary>Some products or orders are missing from the export</summary>

Cin7 may filter records based on status. Archived products, voided orders, or draft records may not be returned by the API. Check the record status in Cin7 directly to confirm whether they should appear.

</details>

<details>

<summary>CRM entities (Leads, Deals, Opportunities) return no data</summary>

These entities are only populated if your Cin7 account has the CRM module enabled and records have been created. If you don't use Cin7's CRM features, these entities will return empty.

</details>

<details>

<summary>Product availabilities show incorrect or stale stock levels</summary>

The **Product availabilities** entity reflects the current state at the time of sync. If stock appears outdated, increase your refresh frequency in Coupler.io. If numbers still look wrong, verify the figures directly in Cin7 to rule out a sync lag on Cin7's side.

</details>

### Permission errors

<details>

<summary>I get a permissions error for specific entities</summary>

The Cin7 API user associated with your key may not have access to all modules. In Cin7, check the user role assigned to the API credentials under **Settings > Users**. Make sure the role has read access to the modules you're trying to export (e.g., Purchases, Sales, CRM).

</details>

### Data discrepancies

<details>

<summary>Totals in my export don't match what I see in Cin7 reports</summary>

Cin7's built-in reports sometimes apply additional filters (date ranges, status, location) that aren't reflected in a raw API export. Make sure you're comparing the same subset of records. If you need filtered data, use Coupler.io's filter or transformation features to match the Cin7 report logic.

</details>

<details>

<summary>Sale lists and Sales show different amounts for the same period</summary>

**Sale lists** contain line-item detail (individual products on each order), while **Sales** contains transaction-level summaries. The totals may differ because of rounding, adjustments, or how tax is attributed at each level. Use **Sales** for revenue totals and **Sale lists** for product-level breakdowns.

</details>

### Rate limits

<details>

<summary>My data flow fails with a rate limit or timeout error</summary>

Cin7's API has rate limits that vary by plan. If you're syncing many entities at once or have a large dataset, try splitting entities across separate data flows and staggering their schedules. Reducing sync frequency can also help avoid hitting limits.

</details>

## Cin7 FAQ

<details>

<summary>What authentication method does Cin7 use with Coupler.io?</summary>

Cin7 uses API key authentication. You'll need your **API Username** and **API Key** from Cin7, which you can find under **Settings > Integrations > API** in your Cin7 account. There's no OAuth flow — just copy and paste the credentials into Coupler.io.

</details>

<details>

<summary>Can I connect multiple Cin7 accounts in the same data flow?</summary>

Yes. Add each Cin7 account as a separate source block within the same data flow, then use the **Append** transformation to combine the records. This is useful if you run separate Cin7 accounts by region, brand, or warehouse.

</details>

<details>

<summary>What's the difference between Sale lists and Sales?</summary>

**Sales** contains one row per transaction with summary-level data like total revenue, COGS, and margin. **Sale lists** contains one row per line item within each order, so you can see exactly which products were sold. Use Sales for revenue reporting and Sale lists for product-level analysis.

</details>

<details>

<summary>What's the difference between Purchase lists and Purchases?</summary>

Same pattern as sales — **Purchases** is the transaction-level summary (total cost, supplier, payment status), while **Purchase lists** is the line-item detail (which products, quantities, and unit costs were on each PO). Use both if you need a complete picture of procurement.

</details>

<details>

<summary>Can I get historical stock level data from Cin7?</summary>

Cin7's API returns current stock levels, not a historical log. To build a stock history, configure your Coupler.io data flow to **append** data on each run rather than overwrite it. Each sync will add a new snapshot with a timestamp, giving you a time series over time.

</details>

<details>

<summary>Why are my CRM entities (Leads, Deals, Opportunities) empty?</summary>

These entities only contain data if you actively use Cin7's built-in CRM module. If your team uses a separate CRM tool, these entities won't have records. Check in Cin7 whether the CRM module is enabled and whether records exist.

</details>

<details>

<summary>Can I send Cin7 data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route any Cin7 entity — for example, Sales or Opportunities — directly to an AI destination for analysis, forecasting, or automated reporting.

</details>

<details>

<summary>How do I analyze revenue by product using Cin7 data?</summary>

Add both the **Sales** and **Products** entities as source blocks in the same data flow, then use Coupler.io's **Join** transformation to link them on the shared product or SKU identifier. This gives you a combined dataset with transaction revenue alongside product details like cost price, category, and brand.

</details>

<details>

<summary>Is Cin7 API access available on all plans?</summary>

No — API access is typically available on Cin7's Business and Enterprise plans. If you can't find the API section under **Settings > Integrations**, contact Cin7 support to confirm whether your plan includes it.

</details>

{% hint style="info" %}
For a full breakdown of what each Cin7 entity contains and how to combine them, see [Data Overview](#cin7-data-overview). If you're running into connection or data problems, check [Common Issues](#cin7-common-issues).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/cin7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
