How to Create Warehouses in an ERP: Godowns, Zones, Bins and What Each One Is For
For businesses with more than one godown, depot or plant store: set up locations once so stock, picking and GST all follow from the right place.
Learning how to create warehouses in an ERP is the first real step of any inventory rollout. Every stock figure, pick list and e-way bill later depends on how locations were set up, and a poor setup is expensive to undo once transactions start.
The common mistake is a flat list of godown names. The returns corner, the rejected material cage and the main store all become one place, so damaged goods look sellable and rejected material counts as available.
This guide covers the decisions to make before you create a warehouse, an illustrative setup at a Rajkot engineering firm, and how Apragya's inventory app models locations.
How to create warehouses, step by step
A warehouse in an ERP is any place stock is held and counted separately: a godown, a branch store, a plant floor, a van, or a cage for rejected material. Treat something as its own warehouse when its stock must be counted, valued or blocked apart from the rest.
Before creating records, decide four things for each location. Which company owns it. Which state and pincode it ships from, since that drives GST registration and e-way bill distance. What it is for, such as sellable stock, transit, quarantine, production or finished goods. And whether it needs zones and bins for picking.
Group nodes help with reporting by region or site, but they should hold no stock themselves. Keep names short and consistent so a picker can read them on a slip.
- List every physical and logical location that holds stock.
- Decide the owning company and GST state for each one.
- Arrange locations in a tree of regions, sites and stores.
- Flag each location's purpose and whether its stock is sellable.
- Add zones for returns, damaged goods and scrap, then bins for picking.
- Set a default warehouse for new documents and test one receipt and one dispatch.
Before and after a proper warehouse setup
With Apragya
- Return and damaged zones kept apart from sellable stock
- State code and pincode stored on each warehouse
- A transit warehouse holding stock on the road
- Zones and bins recording where items sit
- Work in progress and finished goods stores flagged
An example: a Rajkot engineering firm maps its sites
Take an illustrative maker of submersible pump parts with a plant in Gujarat and a sales depot in Maharashtra. Before go-live, the stores head drew every location on one sheet and set its purpose.
One warehouse record, filled in before go-live
Depot warehouse
Groups organise locations but hold no stock.
Set at creation, so stock history stays with it.
Picks the GST registration and e-way bill distance.
Counts towards stock that can be promised.
Returned pumps never land on the sellable shelf.
Pickers go straight to the right shelf.
At go-live the depot's dispatches went out under its own GST registration, returned parts waited in the returns zone for inspection, and the plant's rejected castings sat in a flagged store that nothing could allocate from. The stores head spent a day on the setup and none on fixing it later.
How to build a warehouse master in ERP with Apragya
Step 1 of 5
Nested tree
Arrange locations by region or site; group nodes organise but hold no stock.
- Nested tree: Arrange locations by region or site; group nodes organise but hold no stock.
- Purpose flags: Mark transit, quarantine, rejected, work in progress or finished goods stores.
- Zones and bins: Divide a warehouse into zones and bins, with system zones for returns, damaged and scrap.
- GST geography: State code, city and pincode set the registration and e-way bill distance.
- Sellable or not: Choose which locations count as available to sell, and which bill at a counter.
Planning a multi godown setup that lasts
A list of names tells you where a godown is. It does not say what the godown is for, whether its stock can be sold, or which state it ships from. Those settings drive picking, allocation and GST every day without anyone thinking about them.
A godown list, compared with Apragya
| Feature | List of godown names | Apragya warehouses |
|---|---|---|
| Structure | Flat list | Tree with zones and bins |
| Purpose | Implied by the name | Flags on each warehouse |
| Returns and damage | Same shelf | Separate zones |
| Goods in transit | Not tracked | Transit warehouse |
| GST state | Typed on each bill | Stored on the warehouse |
| Retired godown | Deleted with its history | Disabled, history kept |
Checked against public information on 16 September 2026.
Getting your bin location setup right
Company ownership
Each warehouse belongs to one company, and its stock follows it.
Quarantine stays out
Stock in quarantine is never allocated to an order.
Return routing
Each warehouse names where returned and damaged goods go.
Counter stores
Mark locations that bill at a point of sale.
AI you can put to work
An agent can flag depots with rising damaged stock.
Access by role
Who may create or change warehouses is set per role.
Warehouses underpin putaway rules and pick lists. See warehouses software for the feature, and how to create stock levels for the next step.
Getting started
- Walk each site and list every place stock sits, including corners with a special purpose.
- Arrange the list in a tree by region and site.
- Flag transit, quarantine, rejected and production locations.
- Enter the state code, city and pincode for each warehouse.
- Add zones and bins where pickers need them.
An hour on purposes and state codes saves months of confusing stock and GST reports.
What it costs to start
Creating warehouses, answered
Can a warehouse's company be changed later?
Do bins hold their own quantities?
Can we stop using a warehouse without losing history?
Do we need a transit warehouse?
What does it cost to start?
Set up your godowns the way you actually work
Model every location, flag its purpose and add GST details before stock goes live.