Warehouse settings
Create and manage warehouse location, the default warehouse, and warehouse addresses from Admin › Setup.
Overview
The Admin Warehouses screen manages physical locations and warehouses. Every instance needs at least one warehouse, and exactly one warehouse must be the default.
Where it lives
Route: /admin/settings/warehouses (admin.settings.warehouses)
Open Admin → Setup → Warehouses. Mutations go through warehouse policies (settings.manage).
Key workflows
| Action | Behaviour |
|---|---|
| Add Warehouse | Modal: name, address fields, country (defaults to company country), currency, timezone (defaults to the company timezone) |
| Edit | Update an existing warehouse |
| Set Default | Clears the preceding default atomically |
| Delete | Allowed for non-default warehouses only |
The table supports search and sort on name, city, and country. The first warehouse created becomes the default automatically.
Currency
Each warehouse may run on its own currency, or inherit the company base. The picker's first option is Inherit company base currency; choosing it records nothing, and the warehouse follows company.base_currency. Only enabled currencies are offered.
The warehouse currency is what its rentals are priced in — a rental takes the warehouse's effective currency and cannot be created with a different one. Because of that, an established warehouse cannot simply be switched:
| Blocker | What the field reports |
|---|---|
| The warehouse has open rentals (Quote or Order state, excluding Lost / Expired / Cancelled / Complete) | The warehouse currency cannot be changed while it has open rentals. |
| Price cards scoped to this warehouse are still in the original currency | …price cards remain in :currency (:count found). Run php artisan signals:audit-price-currencies before retrying. |
Open rentals are reported first, so a warehouse with both problems shows only that message. A change that leaves the effective currency where it was — picking the company base explicitly, or clearing a warehouse that already inherits it — is always allowed. Deleting a currency runs the same guard for every warehouse configured to use it, so an in-use currency cannot be removed out from under a warehouse.
See Multi-Currency & Tax for the rate-currency invariant and the audit command.
Timezone
Each warehouse carries the IANA zone its floor runs on. Rental times are entered and displayed in this zone — type 08:00 against a New York warehouse and 08:00 is what the New York crew reads, whatever the viewer's own timezone is.
A warehouse without an explicit zone follows the company timezone. The picker's first option is Inherit company timezone, showing the zone that would be inherited; choosing it records no zone, so the warehouse keeps following the company clock and an unrelated edit never pins it by accident.
Set a named zone when these functions must use the warehouse clock. Company-timezone inheritance is resolved by the rental form, the rental diary, the resource timeline, and the rental document resolver. Other consumers read the stored warehouse column directly:
| Consumer | Timezone |
|---|---|
| Document numbering | Stored warehouse zone, falling back to UTC |
| Stock-check numbering | Stored warehouse zone, falling back to UTC |
| Invoice, credit-note, purchase-order and stock-check document dates | Stored warehouse zone, falling back to UTC |
| Availability slot boundaries and workspace dates | Stored warehouse zone, falling back to the application timezone (app.timezone, default UTC) |
These consumers do not resolve company-timezone inheritance. Their fallback can differ from the company clock when a warehouse is left on Inherit company timezone. Numbering sequences use their resolved local date for rollover; rendered document dates and availability day boundaries use the zones shown here.
Over the API, timezone: null on a PATCH means leave the zone unchanged. To return a warehouse to the company clock, send clear_timezone: true — and send it on its own, because supplying both timezone and clear_timezone: true is rejected.
At a glance
|--------|-------------| | Add Warehouse | Opens a modal to create a new warehouse with name, address, and country | | Edit | Update an existing warehouse's details | | Set Default | Designate a warehouse as the default (atomically clears the preceding default) | | Delete | Remove a non-default warehouse (the default warehouse cannot be deleted) |
The first warehouse created is automatically set as the default. New warehouses default their country to your company's country setting.
Related
- Deeper stock/scoping behaviour: Warehouses
- Warehouse Transfers