Masters and transactions exchange with host systems over the integration API. Message types, payload shapes and error handling are documented in full in the API reference.
Receiving, putaway, picking and counting run on handheld RF devices against the same data as the web application. Where a task was started on a device, it is completed there — the web screen shows progress but hands confirmation back to the floor, so the record matches what was physically scanned.
Operational requests — spend, materials, movements — are raised in the system rather than over email. A request carries a heading, title and description, amount and currency, quantity and unit, vendor, needed-by date and a priority of low, normal, high or urgent. Files can be attached.
Requests are tagged by context: inbound with a linked ASN, outbound with a linked load or order, or internal. Status runs DRAFT, SUBMITTED, APPROVED, REJECTED, CANCELLED.
Issues are raised as tickets inside the application, with formatted text and attachments, and tracked through OPEN, IN_PROGRESS, RESOLVED, REOPENED and CLOSED at low, medium, high or critical priority. Tickets stay attached to the environment they were raised in.
The assistant answers questions about live warehouse data in plain language and returns figures and charts, for the operator who knows the question but not which report holds the answer.