> 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/sales-documents-and-statuses.md).

# Sales documents and statuses

How the Cin7 Core app sends OrderEazi Sales Orders to Cin7, notes Cin7 status updates on the project, and creates OrderEazi documents from Cin7.

Once a client's order is confirmed, your warehouse needs it in Cin7 straight away, and your sales team needs to know when it ships. The Cin7 Core app sends each Sales Order to Cin7, and notes Cin7's updates on the project. It can also create OrderEazi documents from Cin7 invoices and orders.

This page covers how it works with the rules engine off. With the rules engine on, your rules decide what's sent. See [Rules](/central/apps/business-systems/cin7-core/rules.md).

### Before you start

You'll need:

* **The push switches on:** Tick **OrderEazi → Cin7 (push)** and **Sales documents**, under **Sync Settings** on the **Configuration** tab. See [Configuration](/central/apps/business-systems/cin7-core/configuration.md).
* **The client in Cin7:** The app never creates Cin7 customers. Each client must exist in Cin7, or be linked on the **Mappings** tab. See [Mappings](/central/apps/business-systems/cin7-core/mappings.md).
* **Your products in Cin7:** Each line's product code must match a Cin7 SKU (the product code), or be linked on the **Mappings** tab.

### How a Sales Order is sent

When a [Sales Order](/central/order-management/documents/sales-documents/sales-orders.md) is created in OrderEazi, the app sends it to Cin7 as a draft sale, ready for you to authorise (confirm in Cin7, which reserves the stock):

* **The customer:** The client is found by its code, then its name, then by searching Cin7 by name.
* **The details:** The document's reference, the contact, and the billing and shipping addresses are copied. Tax rules and the price tier come from your mappings.
* **The lines:** Each product is sent under its linked Cin7 SKU, or else its OrderEazi code. Lines without a product code aren't sent.

The project's history then shows "Synced to Cin7 sale \[number] (\[ID]).", with the Cin7 order number and sale ID in place of \[number] and \[ID]. See [Project History](/central/order-management/projects/project-history.md). Each Sales Order becomes its own Cin7 sale, so a project with Sales Orders for two warehouses has two Cin7 sales.

**Example:** A project for Clientco (Pty) Ltd is approved, and its Sales Order SO000567 is created. Within a few minutes, Cin7 has a draft sale for Clientco with the same lines and reference. The project's history shows "Synced to Cin7 sale" with the Cin7 order number.

### When a Sales Order isn't sent

The reason is on the **Sale Logs** tab, and on the project's history:

* **"Customer '\[name]' does not exist in Cin7 and is not mapped; create/map it in Cin7 first.", with the client's name in place of \[name]:** Create the customer in Cin7, or link it on **Mappings**. Then resend the Sales Order from the **Queue** tab under **Integrations** > **Webhooks**. See [Webhooks](/central/order-management/integrations/webhooks.md).
* **"Client '\[name]' is on the excluded Cin7 price tier '\[tier]'; document not pushed to Cin7.", with the client's name and tier in place of \[name] and \[tier]:** The client's pricelist is linked to an excluded tier, so it's skipped on purpose.
* **"This project's Cin7 sale came from a quote, so its sales orders are not pushed.":** The rules engine already sent this project to Cin7 as a quote, so the rules handle it.
* **"Document '\[number]' has already been synced to Cin7.", with the document number in place of \[number]:** Each Sales Order is only sent once.

### How Cin7 status updates reach the project

Every 30 minutes by default, the app checks Cin7 for sales that have changed. For a sale that came from OrderEazi, the project's history gets a note, "Cin7 sale \[number] status: \[status].", with the Cin7 sale number and status in place of \[number] and \[status]. Once the sale is invoiced, " (invoice \[number])" is added.

This needs **Cin7 → OrderEazi (pull-back)** on, and at least one of **Shipment status**, **Invoice status**, or **Payment status**. Sales that didn't come from OrderEazi leave a Failed row you can ignore. See [Logs](/central/apps/business-systems/cin7-core/logs.md).

### Documents created from Cin7

> **Warning:** **Documents → OE** is on by default. Once you choose a **Sales Channel**, every Cin7 sale that didn't come from OrderEazi is created as a new OrderEazi order, whatever its status in Cin7. The first check can include older sales. Clear **Documents → OE**, or leave **Sales Channel** blank, until you want this. Clearing it also stops Tax Invoices coming from Cin7 invoices.

With **Documents → OE** on, a Cin7 invoice on a sale that came from OrderEazi becomes a [Tax Invoice](/central/order-management/documents/sales-documents/tax-invoices.md) on the project. It's numbered with the Cin7 invoice number, and invoices that came from OrderEazi aren't created again.

A Cin7 sale with no OrderEazi project becomes a new OrderEazi order, described "Imported from Cin7 sale \[number]", with the Cin7 sale number in place of \[number]. This needs a **Sales Channel** on the **Configuration** tab. Quantities on documents created from Cin7 are rounded to whole units.

### What the app does not do with sales documents

* **Send Quotes or Tax Invoices:** With the rules engine off, only Sales Orders go to Cin7.
* **Move the project through its workflow:** Cin7 updates are notes on the project's history only.
* **Update a sent order:** Once a Sales Order is in Cin7, changes in OrderEazi aren't sent.

### Related pages

* [Rules](/central/apps/business-systems/cin7-core/rules.md): send Quotes, Tax Invoices, and stock transfers at chosen workflow steps
* [Logs](/central/apps/business-systems/cin7-core/logs.md): check what was sent and received
* [Sales Channels](/central/order-management/integrations/sales-channels.md): set up the channel for orders from Cin7