Reporting

LogisticaHQ gives you four ways to get numbers out of your warehouse, from ready-made screens that need no setup to your own queries emailed to your clients every morning. This page explains what each one is for, so you can pick the right one; each has its own page with every detail.

Which one to use

Built-in reports

The Analytics menu holds reports that are ready to use: Inventory, Bulk inventory, Empty bins, Inventory availability, Inventory detail, Four wall report, Staging LPNs, Warehouse min/max, Bin min/max, Expiry, Lot trace & recall, Substitutes, Inventory snapshot and LPN snapshot under Inventory, and Cycle count bins, Cycle count LPNs and Cycle count audit under Cycle count. Each is a screen with its own search, filters and Excel export; nothing needs to be built.

Widgets and dashboards

A widget is one report you define: a query that reads your data, and one or more presentations of its rows, as a chart, a grid, tiles, a single number or a gauge. A dashboard arranges widgets side by side, each in a panel you can drag and resize, and appears in the menu under Analytics > Custom dashboards for everyone to read. One widget can sit on many dashboards, and filters let the same widget show a different warehouse or period on each panel.

To start with a complete set rather than from nothing, press Actions > Seed default reports on the Dashboards list: it installs LogisticaHQ's standard performance widgets and a Warehouse performance dashboard.

Scheduled reports

A scheduled report runs a query hourly, daily, weekly or monthly and emails the rows as an Excel file. Pick one of the ready-made reports (orders shipped yesterday, late orders, lots expiring, last night's inventory, month-end closing stock and more) or write your own. For a 3PL operation, one scheduled report can go to each of your clients separately, each receiving only its own rows at its own address.

The SQL behind them

Widgets, scheduled reports and the Query builder share one SQL editor: SQL is coloured as you type, suggestions offer only table names after FROM and only columns in the SELECT list, every table and column is listed beside the editor, and Execute shows the rows before anything is saved or sent.

Everything written there is read-only, enforced three times over: only a single SELECT is accepted, it runs on a database login that cannot change data, and it runs inside a transaction that is always undone. Passwords, password hashes and API keys can never be read. A report can never add, change or delete anything in your warehouse.

Two values are always available to a query: @ClientId, the client a report is for (empty for warehouse staff, who see every client), and @UtcNow, the current date and time in UTC. Filtering on @ClientId with (@ClientId IS NULL OR x.ClientId = @ClientId) is what lets one report serve warehouse staff and each client alike.

Who can do what