Summary and recommendation
Loop Returns user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Loop Returns is a Shopify-native returns and exchanges platform with shipment-volume-based pricing, starting at $155/month for up to 2,000 shipments. Team member management is handled through the merchant dashboard at admin.loopreturns.com, but the full role and permission structure is not publicly documented - details are only accessible to logged-in merchants.
Google SSO is available for portal login, but no SCIM or SAML provisioning is documented at any plan tier.
Quick facts
| Admin console path | Settings > Team (unverified; gated behind merchant login) |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Unknown |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Loop Returns' role and permission structure is not publicly documented. Details are only accessible to logged-in merchants via the admin portal. |
Permission model
- Model type: gated-role-based
- Description: Not publicly documented. Loop Returns does not publish role definitions, permission sets, or access control details in its public help center or developer docs.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Log in to the Loop Returns merchant dashboard.
- Open the team-management or settings area inside the admin portal.
- Enter the new team member's email address.
- Assign the available role or access level exposed in the merchant UI.
- Send the invitation so the user can activate access.
Required fields: Email address
Watch out for:
- User management documentation is gated behind merchant login at help.loopreturns.com. Steps cannot be verified from public sources.
- Loop supports Google SSO for login but no IDP provisioning (SCIM/SAML) is publicly documented.
- Platform is Shopify-native; it is unclear whether Loop user accounts are separate from Shopify staff accounts or linked.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: No public documentation describes whether Loop Returns supports user deletion, deactivation, or only removal. Cannot be verified without merchant account access.
- Open the team-management area in the Loop merchant dashboard.
- Locate the departing user in the team list.
- Remove the user or revoke their access from the dashboard.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- No public documentation on offboarding workflows, data retention after user removal, or license reclamation.
- Pricing is shipment-volume-based, not per-seat, so license implications of removing a user are unclear.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Essential | Returns management up to 2,000 shipments/month | $155/month |
| Advanced | Additional features (exchanges, analytics); up to 2,000 shipments/month | $272–$340/month |
| Enterprise | Custom shipment volume, dedicated support, advanced integrations | Custom pricing |
- Where to check usage: Not documented
- How to identify unused seats: Not publicly documented. Billing is shipment-volume-based, not per-seat, so unused seat identification may not apply in the traditional sense.
- Billing notes: Pricing is based on monthly shipment volume, not number of users/seats. Adding or removing team members does not directly affect subscription cost based on publicly available pricing information.
The cost of manual management
Because Loop's billing is based on shipment volume rather than seats, adding or removing team members does not directly affect subscription cost. That said, every app with manual-only user management creates operational drag: onboarding and offboarding require dashboard access each time, with no automated provisioning or deprovisioning path.
No public documentation describes data retention behavior or access revocation guarantees after a team member is removed, which creates an audit gap for security-conscious teams.
The decision
Loop Returns is well-suited for Shopify merchants prioritizing returns automation and exchange workflows over IT governance features. Teams that require IdP-driven provisioning (Okta, Entra, OneLogin), granular role controls, or audit-ready offboarding will find Loop's current access management capabilities limited.
If your organization manages every app through a centralized identity provider, Loop's manual-only team management will require a compensating process.
Bottom line
Loop Returns offers no documented SCIM, SAML, or programmatic user management at any pricing tier. Team access is managed entirely through the merchant dashboard, with no public documentation on role definitions, permission granularity, or offboarding behavior.
For small Shopify merchant teams, this is workable. For organizations that govern every app through a centralized identity provider or require audit-ready access controls, the current feature set introduces meaningful manual overhead and compliance risk.
Automate Loop Returns workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
