Security
The controls behind brand orders reaching the warehouse: separated customer data, encrypted credentials, approved rules and an audit history.
Discuss security and pricing →Connection credentials are encrypted at rest and access to them is recorded. Key rotation is designed not to interrupt active connections.
Every request runs inside the authenticated customer context. Warehouse data and operational records are isolated between Prua tenants.
Your team approves how warehouse fields are handled before go-live. If a required value cannot be resolved, the order stops and names the gap instead of guessing.
Inbound requests are signed and checked so replayed files do not create a second warehouse order.
Authenticated sessions, role-aware access and an audit history show who changed a connection and what happened to each order.