RattusWMS separates three levels. An organisation owns one or more warehouses. Each warehouse holds stock for one or more storers — the clients whose goods you handle. Every record in the system carries a warehouse code and, where relevant, a storer id, so one installation runs many warehouses and many clients without their data meeting.
| Level | What it is | Carried on records as |
|---|---|---|
| Organisation | The operating company | org_code |
| Warehouse | A physical site | warehouse_code / warehouse_id |
| Storer | A client whose stock you hold | storer_id / storer_code |
Users switch warehouse from the selector in the sidebar. Feature flags, master data and permissions are re-read on every switch, so nothing carries over from the site you were just in.
Every environment-aware record stores an environment value. UAT shows an amber strip across the top of every page; production shows none. The same build serves both, so a test in UAT exercises the code that will run live.
Warehouses differ, so the modules a warehouse runs are configuration rather than code. Flags are read from the warehouse record at login and again on every warehouse switch. A flag that is absent is off — it never inherits from the previous warehouse.
| Flag | Effect when on |
|---|---|
| warehouse_type | Marks the site as general or a free-trade / bonded type |
| ftwz_zone | Records the free-trade zone the site operates in |
| cold_chain | Turns on temperature handling |
| gdp_required | Enforces GDP capture on gate pass |
| wave_planning | Adds wave planning to outbound |
| batch_pick | Adds batch picking to outbound |
| pick_to_store | Adds the pick-to-store flow |
| crossdock_enabled | Allows ASN lines to be flagged for cross-dock |
| billing_enabled | Turns on the 3PL billing module |
| pickpack_enabled | Combines picking and packing into one step |
| kitting_enabled | Turns on kitting and de-kitting |
| replenishment_enabled | Generates replenishment tasks |
| replenishment_pick_strategy | FEFO or FIFO for replenishment picks |
| allow_warehouse_override | Lets warehouse settings override storer settings |
Access is granted per user, per module. Twelve modules can be switched on or off individually, grouped as General, Operations, Finance, Custom Apps and Admin.
- General — gate pass, reports
- Operations — inbound, outbound, kitting, cross dock, wave planning, batch picking
- Finance — billing, customs / LGP
- Admin — admin and product master
- Custom Apps — client-specific modules
Only a super admin or a role admin can change access. The same screen carries a second tab listing live sessions, filterable by online or idle state, by environment and by build version — so you can see who is in the system and on which release.
Activity is tracked per session. A green marker means active, grey means idle, and sessions lock themselves after a period without input. Session rows carry the build version, which is how you confirm an operator is on the release you think they are.
Actions that change stock or status write an audit row. Each row records the entity, the action, who performed it, the status before and after, and the warehouse and storer it belonged to.
Entity types written today:
- RECEIPT, ORDER, PICK, LOAD, PALLET
- ADJUSTMENT, TRANSFER, STOCK_COUNT
- CS_APPROVAL, STORER, WAREHOUSE