Stock per Zid location from your ERP warehouses
Each Zid location is linked to its ERP warehouse. That warehouse's stock is written to the location, then read back to confirm it.

Where does the stock number on each location in your Zid store come from?
From the warehouse behind that location in your ERP. Each Zid location is linked to its warehouse, the warehouse’s stock is written to the location, and then it is read back to confirm it.
The trouble with one number
A store that ships from more than one warehouse needs to know what each warehouse holds. When the store shows one number that adds up every warehouse, a product looks in stock even after one location has run out.
That is where overselling starts. You sell stock that exists in the pooled number but not in the location the order has to leave from. The result is a late order, a cancellation, or stock moved between warehouses at the last minute.
The alternative is for each Zid location to show the stock of the warehouse behind it. That is what the app’s stock flow does.
From warehouse to location
Stock flows from your ERP to Zid, in four steps.
Stock in the ERP
Each warehouse's stock is held in your ERP, the source of the number.
Warehouse linked to its location
Each location in your Zid store is linked to its matching ERP warehouse.
Stock written to the location
The warehouse's stock is written to its location in Zid.
Read back
The stock is read back after it is written, to confirm it.
1. The ERP is the source
Your ERP holds each warehouse’s stock, so the flow starts there and runs to Zid. The Zid location shows what reaches it from the ERP.
2. Each location linked to its warehouse
The app reads your store’s locations from Zid. During setup, each Zid location is linked to its matching warehouse in your ERP. Our team does the setup with you, and you go live in about two weeks, after a test report you approve.
3. Stock written to the location
Once linked, the warehouse’s stock is written to its location in Zid, as often as every minute. Each location then shows its own warehouse’s stock, and a stock-out shows in the location that ran out.
4. Read back
After the stock is written to the location, it is read back. That read confirms the location shows the number that was written.
One number or one per location
The table compares the two, row by row.
| One number for the store | One number per location | |
|---|---|---|
| Stock in Zid | One number for the whole store | A number for each location in the store |
| Where it comes from | All warehouses added up | That location's warehouse in your ERP |
| A location that ran out | Hidden inside the pooled number | Shows in that location |
| Overselling | Stock gets sold that the right location does not have | Each location shows its own warehouse's stock, so a shortfall shows where it is |
What you see in each place
Your ERP shows the stock in each warehouse, where the flow starts. Zid shows each location with its linked warehouse’s stock, once written and read back.
| Place | What it shows | Its role in the flow |
|---|---|---|
| Your ERP | Stock in each warehouse | The source of the number |
| Zid | The warehouse’s stock on its location | Shows the number after it is written and read back |
The numbers
These figures come from Zid Integrations data.
- stock updates from ERPs to Zid
- Over 800,000
- automated operations between Zid stores and ERPs
- Over 1 million
Questions merchants ask
Correcting a quantity in the ERP
Correct a warehouse’s quantity in your ERP, and the new number shows on its Zid location with the next update. The flow starts in the ERP.
Out in one warehouse, left in another
Each Zid location shows its own warehouse’s stock. The first location shows its warehouse’s quantity, which is zero, and the second shows what is left in its warehouse.
Editing the quantity by hand in Zid
The flow runs from your ERP, the source of the number, to Zid. So the place to correct stock is your ERP.
One location, several ERPNext warehouses
With ERPNext, one Zid location can link to several regular warehouses, and their stock is added together on the location. A location cannot link to a group warehouse, the kind that holds other warehouses. Adding a branch after go-live is a settings change with no code: our team links its location to its warehouse. More on the ERPNext page.
Orders
Orders have their own flow, separate from stock, from Zid to your ERP. Each paid order is posted to the ERP with the customer, items, tax and shipping, then read back from the ERP to confirm it.
Routing an order to its warehouse
Showing stock per location is different from routing an order. Routing each order to the warehouse that serves the shopper’s city comes with the Business plan: the order goes to the warehouse that serves its ship-to city, from a city list our team sets during setup. If no city matches, it goes to the warehouse of the Zid location fulfilling it, and otherwise to the default warehouse.
Plans
Stock per location comes with the Growth plan, which covers 500 orders a month and also adds the grow-sales tools; price sync is set up on request. Business covers 2,000 orders and adds routing by ship-to city across several warehouses, and priority support. Trials run 7 days on monthly billing and 30 days on yearly billing.
Details of each plan and current prices are on the app’s page in the Zid App Market.
To show each warehouse’s stock on its own location in your store, install the app from the Zid App Market.


