Run the floor from a browser tab.
The warehouse manager dashboard for Acumatica operations.
Live session visibility, exception approvals, and every behavioural setting — putaway strategy to print events — changed by a manager, not a developer.
You find out about the problem when someone phones you about it.
A pick session stalled forty minutes ago. A receiver has been sitting on an over-receipt waiting for someone to say yes. A variance from Tuesday's count is still unapproved.
None of it is visible until it is late, and changing how any of it behaves means an email to a consultant and a wait.
Illustrative only. All three exceptions surface here the moment they happen — not when someone calls to ask about them. Approving the over-receipt from this screen is what posts it.
The Sales Orders view this page describes:
Multi-warehouse visibility in a single view is not supported — you switch between warehouses one at a time from the portal's warehouse selector, but cannot view more than one at once.
Before it becomes the phone call.
Every active session, live
Who is working, what they are working on, where they are in the workflow and how long they have been there — from any browser on the network.
Inventory answers in seconds
Product detail, location detail, LP detail, transaction history, staging visibility and open allocations are one search away. No call to the floor, no digging through ERP screens.
See inventoryThreshold alerts on the dashboard
Configurable KPI widgets surface sessions idle too long, overdue cycle count locations, approvals sitting unactioned and replenishment tasks not started — before they become the phone call.
See cycle countingApprove it here, without touching a scanner.
- Approval authority Over-receiving exceptions, quality hold dispositions and cycle count variance approvals all route here. Review, approve or reject without touching a scanner. See quality hold.
- Intervene without disrupting A stalled pick, a mid-pick amendment, a hot order that needs to jump the queue — the manager acts from the portal and the worker's scanner updates without the session stopping or restarting. See fulfillment.
No developer. No change window.
- Putaway strategies
- Receiving thresholds
- Replenishment rules
- Carrier routing
- Allergen stacking rules
- Cycle count schedules
- Print event assignments
- Notification preferences
Every behavioural decision is a portal setting. Putaway strategies, receiving thresholds, replenishment rules, carrier routing, allergen stacking rules, cycle count schedules, print event assignments and notification preferences. No developer, no change window.
Notification management. Which roles receive which alerts, internal messages composed and sent, and a full notification log confirming what was delivered and acted on.
See putaway strategies · see print events · see replenishment.
Every action ties to a user.
Worker accountability
Every action ties to a user — who received it, put it away, picked it, packed it, shipped it, approved the variance. The audit trail is always queryable.
Access control and login audit
User provisioning, role assignment, the login audit log, failed-login lockouts and exportable access reports.
What your auditor asks forThe configuration is the operation.
In most warehouse systems, how the software behaves is buried in code or costs a consultant to change. In WMSi, how inventory is routed, when exceptions escalate, what prints and when, and how workers are directed are all settings in this portal.
The manager owns the operation, not just the oversight of it.
Where the two systems are shown agreeing.
The portal is where the two systems are shown agreeing. Sync discrepancies raised by the reconciliation pass surface here for review rather than in an ERP report nobody opens, and the approvals made here — a count variance, a hold disposition — are what post back to Acumatica as Inventory Adjustments. The manager approves once, in one place, and the ERP follows.
- Discrepancies
- Raised by the 30-minute reconciliation pass and surfaced here for review. How the pass works.
- Approvals
- Count variances and hold dispositions post back to Acumatica as Inventory Adjustments.
- Audit evidence
- Login audit log, user access reports and the immutable transaction log. What an auditor asks for.
- Delegation
- Approval authority itself cannot be delegated or escalated on a schedule. Instead, a covering user can be added to the role that can approve, so someone else can act while the primary manager is away.
Twenty minutes, the live session dashboard, no slides.
The approval workflow and configuration control, on a real instance. We sell through Acumatica VARs — tell us how your floor runs and we will introduce you to the right partner.