How do roles and partners work?
Rotion is built for multi-party loops: producers, fleet owners, carriers, service partners, and retailers each work with role-based access and permissions.
Last updated: 29 September 2026
Rotion is built for multi-party operation: producers, fleet owners, carriers, service partners, and retailers all touch the same assets, and each participates with role-based access and permissions. Partners confirm handovers in the browser or on a phone, drivers can record scans on a partner's behalf, and the loop does not stall when some partners never adopt a tool.
Which parties participate in a reusable packaging loop?
A Rotion loop typically involves five kinds of parties, each with a different relationship to the assets. All of them work against the same asset records, the digital packaging passports, but each within its own role and permissions.
| Party | Typical role in Rotion |
|---|---|
| Producer | Issues assets with goods, scans at dispatch |
| Fleet owner | Owns the assets, manages the pool, sees the whole fleet |
| Carrier | Moves loads, confirms pickups and drops, scans batches |
| Service partner | Runs washing, repair, or return handling, records those events |
| Retailer | Receives assets, returns empties, holds a balance or deposit position |
External operators are supported as first-class participants: a fleet can be run day to day by a logistics or pooling operator on behalf of the owner, with its own role and scope.
Do all partners need to use Rotion for it to work?
No. Rotion is designed for chains where not every partner has the same maturity or willingness to adopt tools. A partner needs nothing installed to confirm a handover in the browser or on a phone, and for partners who do nothing at all, your drivers record the scans. The loop stays accountable either way.
This is the practical difference between a multi-party system and a single-company tool. Coverage starts with the parties you control, your own dispatch, your own drivers, and grows as partners see their balances and want access. A retailer that only ever clicks a confirmation link is still a fully accounted participant in the loop.
Onboarding partners also carries no per-seat license cost on the Launch and Scale plans: washers, carriers, and depot staff join the loop and scan without seat-metering, so the cost of the system does not grow with every partner employee who touches an asset.
How are access and permissions controlled?
Rotion uses role-based access and permissions per team, vendor, and entity, so every user sees exactly what their role needs and nothing else. Guided actions per scan are role and state dependent: what a washer can record about an asset differs from what a driver or a retailer can. Sign-in can run through your identity provider with SSO, and movements, handovers, and status changes land in audit logs automatically (see security and deployment).
How much each customer and use case can see is a configuration choice. A fleet owner decides what each retailer sees of the fleet, what a carrier sees of destinations, and what an operator running multiple customers keeps separated between them. Sensitive commercial data stays with the party that owns it.
What does a partner see in their portal?
Each partner gets a portal view scoped precisely to them: which stages, products, and assets a partner sees is configured per partner, and a retailer, grower, washer, or carrier logs into a dashboard that shows their part of the loop and nothing else. Portal dashboards are configurable per partner, with custom KPIs, partner-specific sections, and your branding, so a partner-facing view can run white-labeled under the fleet owner's identity.
Users can also belong to more than one partner and switch between them, which fits operators and service companies that work for several parties in the same loop.
Why does multi-party design matter for asset recovery?
Because assets are lost between parties, not inside them. When every handover has a named giver, a named receiver, and a scan, responsibility never goes dark at a dock door. Per-partner views and balances (see asset-level vs balance-level tracking) turn recovery into a routine conversation backed by a shared record: this partner holds these returnable transport items (RTIs), totes, or dunnage racks, since these dates. That shared record, rather than any single party's spreadsheet, is what keeps a loop of independent companies running as one system.
Rolling out across partners?
How does quality control work?
Rotion's quality control module covers inspections, damage photos, repair tracking, and wash cycles, so asset condition is part of the same record as location.
How does reuse reporting and compliance work?
Rotion turns lifecycle data into reuse reporting: rotation, reuse performance, and per-partner flows, as a foundation for PPWR and US EPR readiness.