> 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/order-management/integrations/accounting-system/sage-evolution/stock-and-warehouses-with-sage-evolution.md).

# Stock and Warehouses with Sage Evolution

Match your OrderEazi warehouses to Sage Evolution, choose which system owns stock, and send stock movements.

Both OrderEazi and Sage Evolution count stock in each warehouse. If they don't agree on which warehouse is which, stock lands in the wrong place, or one system overwrites the other's counts. The **Warehouse Mapping** tells OrderEazi which Sage Evolution warehouse each of yours matches, and your plan decides which system owns the stock figures.

### Before you start

You'll need the **Accounting System** permission, in the **Integrations** permission group. If you don't have it, ask your OrderEazi administrator to add it to your role. Connect the connector first, and select **Test connector** so OrderEazi has the list of Evolution warehouses. See [Setting Up the Sage Evolution Connector](/central/order-management/integrations/accounting-system/sage-evolution/setting-up-the-sage-evolution-connector.md).

### How to map your warehouses

1. In the main menu, go to **Integrations** > **Accounting System**.
2. Under **Warehouse Mapping**, choose a Sage Evolution warehouse under **Good** for each OrderEazi warehouse.
3. If you use them, choose the **Faulty** and **Damaged** warehouses too. They're used for lines of those types.
4. For a warehouse with no Evolution match, such as goods in transit, choose **Not synced with Sage Evolution**.
5. Select **Save**.

Below the Enterprise licence, you map one warehouse. On the Enterprise licence, every active warehouse needs an answer under **Good** before syncing can be switched on. Until then, you see "Warehouse mapping is not finished." Your mapping saves either way, so you can work through it in stages.

### How to map many warehouses at once

On the Enterprise licence:

* **Auto-match by code:** Chooses the Evolution warehouse with exactly the same code as each OrderEazi warehouse.
* **Quick pair:** Matches unmatched warehouses to Evolution codes side by side.
* **Mark remaining as not synced:** Answers every warehouse still blank.
* **New Warehouse:** Creates an OrderEazi warehouse without leaving the page.

The first three only choose answers for you. They don't change a warehouse you've already answered, and nothing is kept until you select **Save**. Tick **Show only conflicts** to find two warehouses using the same Evolution code. Only the warehouse created first gets that code's stock levels.

### Which system owns stock

* **The Enterprise licence:** OrderEazi owns stock. Stock levels aren't brought in from Evolution, and OrderEazi sends Evolution the stock movements instead. If you don't count stock in OrderEazi's warehouses, turn on **Sage Evolution is the master of stock** to bring Evolution's figures in.
* **Below the Enterprise licence:** Evolution owns stock. Its figures come into your mapped warehouse every hour, while **Inventory Importer** is on.
* **The figures:** Evolution's quantity on hand becomes **Actual**, its reserved quantity **Reserved**, and its quantity on order **Incoming**. Only the **Good** warehouse is used, in whole units.

**Example:** You're on the Enterprise licence, with "JHB" and "CPT" warehouses in OrderEazi, and "001" and "002" in Evolution. You map JHB to 001 and CPT to 002 under **Good**, turn on **Stock Level Adjustment Exporter**, and save. When your Cape Town team adjusts GOLF-SHIRT-NAVY down by 3, OrderEazi sends a 3-unit adjustment to warehouse 002 in Evolution.

### Sending stock movements

* **Stock Level Adjustment Exporter:** Sends stock adjustments, closed stock takes, and warehouse transfers. A stock take is sent as adjustments for its variance lines only.
* **Send Disposals:** Sends dispatched disposals as stock decreases.
* **When it starts:** Sending starts on the day you first switch on either of these. Movements from before that day aren't sent.

Warehouse transfers need Sage Evolution 8.0.0.89 or later. On older versions they're skipped, and aren't sent after you upgrade. Movements in a warehouse marked **Not synced with Sage Evolution** aren't sent.

If Evolution refuses a movement, such as a decrease that would make stock negative, OrderEazi tries again every hour until it's fixed in Evolution.

### Related pages

* [Sage Evolution](/central/order-management/integrations/accounting-system/sage-evolution.md): what else syncs
* [Simple Inventory Management](/central/order-management/products/inventory/simple-inventory-management.md): stock levels in OrderEazi