For regional 3PLs
Prua receives each brand's orders, validates the warehouse fields, posts approved data to your existing WMS and tracks the run through dispatch.
One recurring workspace gives the shed the same intake, exception and status process for each brand.
Email, CSV, PDF, SFTP, portal export or API all open the same Prua order thread.
Prua validates and posts approved data without asking pickers to move to a new operational system.
Units and locations fail the same way. Prua holds anything unresolved for the office before it reaches the pick face.
The recurring warehouse workspace and its current product boundary.
In scope
Out of scope
Sample data shown to explain the layout.
PO-1042 · Parton · sample
A brand sends a weekly CSV with extra columns and mixed units. Two SKUs have no location — those lines stop and wait. The rest land in the WMS. The row shows received; in-WMS sits past the next working day; the shed sees it before the brand calls.
Same clock if the WMS is on-site. Unmatched fields wait for confirmation.
The home screen is a dispatch board grouped by client. Orders sit at received, in the WMS, picked or dispatched. Stalled orders name the missing field.
The brand keeps sending orders the way it sends them now. There is no new portal for the brand to learn.
If they call about an order, you can send a read-only link to that one row: received 09:14, in the WMS 09:16. No other clients. No keys.
Recurring software subscription with 14-day onboarding for the first connection.
Get subscription pricing →