Help Center

What the dashboard is for

The dashboard is the place to answer “what needs attention today?” It is not meant to replace the inventory, order, or report pages. It is meant to show the operational cues that help a user decide where to go next: upcoming picks, prep work, returns, maintenance attention, and other work that should not be hidden inside a long table.

Use the dashboard at the start of a shift or when you are trying to regain context. A warehouse user may look for what needs to be picked, prepped, transferred, returned, or maintained. An owner may look for overdue work, open reservations, maintenance pressure, or a quick path into reports. The dashboard should be a launch point, not a place where every possible record is edited.

Dashboard work should normally start in the user’s assigned warehouse context. Managers and users with broader warehouse permissions can review other warehouses or all-company operations. Storage-only annex work appears with the operational warehouse that manages it so daily work is not split across unstaffed locations.

Reading calendar and workflow cues

Pick dates, prep windows, rental start dates, rental end dates, and expected returns are different signals. A rental may start Friday, but the warehouse may need to prep it Wednesday and pick it Thursday. Treat those operational dates as reminders for work that happens around the rental, not as decorative fields on the order.

When a date looks wrong on the dashboard, open the order and check the order dates first. Company settings can define default pick and prep timing, while an individual order can hold manual dates when the job needs an exception. If the rental start or end changes, availability and the visible work dates should be recalculated so the dashboard stays useful.

Using dashboard links safely

Dashboard links should take you to the workflow where the work is actually done. If a card points at a pick, open the order or pick workflow. If a card points at maintenance, open the maintenance job or item record. If a card points at a report, use the report page to adjust the scope before printing.

Do not treat a dashboard count as the final answer when money, availability, or fulfillment is at stake. Use it as a warning light, then open the underlying workflow before making a decision. The goal is speed with context: Pluck should bring important work forward without skipping the record that explains why that work exists.