Navigating the App

The WMS is a single-page web app with a left-hand sidebar. Everything in this guide is reached from that sidebar, which is organised into sections rather than a drill-down hierarchy — for example, Zones, Aisles and Bins are each their own top-level entry, not pages you open “inside” a warehouse.

Sidebar structure

Section	Items	Used for
Stock	Items, Item Warehouse, Quants, Lots	The product catalog, per-warehouse item enrollments, on-hand stock records, and lots/batches
Inbound	Inbound Order	Receiving stock
Outbound	Outbound Order	Picking and dispatching stock
Internal	Transfer Order, Stock Count	Moving stock between bins, and counting/reconciling
Locations	Zones, Aisles, Racks, Shelves, Bins	The physical location hierarchy
History	Inventory Transactions, Audit Log	The read-only ledger and the user-action audit trail
Master Data	Categories, Warehouses	Catalog categories and warehouse setup (admin only)
Admin	Users & Roles	Accounts, roles, and permission assignment (admin only)

A few mappings worth knowing because the label differs from what you might expect:

• Item Warehouse (under Stock) is where you enroll a catalog item into a warehouse — there is no separate “Enroll Item” screen.
• Quants (under Stock) is where you view on-hand stock and make manual stock adjustments — there is no separate “Stock Adjustments” screen.
• Warehouses lives under Master Data, not at the top level.
• Lots is a top-level entry under Stock, not nested inside a warehouse item.

Common actions

• Create buttons read like ADD NEW INBOUND ORDER, ADD NEW ZONE, or ADD STOCK COUNT — “ADD” (or “ADD NEW”) plus the entity name. The exact wording is inconsistent between screens (some include “NEW”, some don’t), so match on the entity name rather than the precise phrasing.
• Workflow steps appear as row or detail actions: Start Receiving, Receive, Reserve, Complete, Delete, and the Edit (pencil) action.

Two different access controls

The app gates access in two independent ways, and it’s easy to confuse them:

1. What the API lets you do — the granular action:resource permissions on your role (see Users and Roles and the Permissions Reference).
2. What appears in the sidebar — the Master Data and Admin sections are shown only to users whose role name is admin or superadmin. This is a separate check from the permission system: a user could hold the right API permissions yet not see these menu entries because their role isn’t named admin.

If someone “has permission” but can’t find a screen, check their role name, not just their permissions.