Summary and recommendation
Stamped.io 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.
Stamped.io is a reviews and loyalty platform built for e-commerce merchants.
Plans are priced by monthly order volume Basic at $23/mo (200 orders), Premium at $59/mo (500 orders), Business at $149/mo (1,500 orders), and Direct plans from $299–$499+/mo not by named user seats.
There is no per-seat billing model documented in official sources.
Quick facts
| Admin console path | Public Stamped.io documentation does not expose a detailed multi-user admin path; account administration appears to happen in the authenticated merchant dashboard and account settings. |
| 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 |
|---|---|---|---|---|---|
| Account owner / admin | Manages store configuration, billing, integrations, and any available staff access inside the Stamped.io merchant dashboard. | Detailed public permission boundaries are not documented. | Not publicly documented | No per-seat pricing documented | Public docs do not confirm a multi-user role matrix. |
Permission model
- Model type: account-based (public role details not documented)
- Description: Public Stamped.io documentation does not publish a detailed user-role or permission model for internal staff accounts.
- Custom roles: No
- Custom roles plan: Not publicly documented
- Granularity: Not publicly documented
How to add users
- Use the authenticated Stamped.io dashboard or account-settings workflow available in your tenant to add or invite a user, if multi-user access is enabled for your account.
- Assign any available dashboard role or account access level in the tenant.
- Validate the exact workflow in the live tenant because the public help center does not expose step-by-step staff-management documentation.
Required fields: Work email or account identifier as required by the tenant
Watch out for:
- Public documentation does not clearly confirm whether all plans support multi-user staff administration.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public Stamped.io documentation does not describe whether internal dashboard users are deleted, deactivated, or otherwise removed when access is revoked.
- Use the tenant-specific account or staff-management workflow inside the Stamped.io dashboard to revoke access.
- Confirm merchant account impact and integration ownership before removing the user because public docs do not describe offboarding behavior.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Order-volume plan | Billing is based on order volume and enabled modules rather than named user seats. | Basic $23/mo, Premium $59/mo, Business $149/mo, higher tiers custom |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Plans are priced by order volume (e.g., Basic $23/mo for 200 orders, Premium $59/mo for 500 orders, Business $149/mo for 1,500 orders), not by named user seats. No per-seat billing model documented in official sources.
The cost of manual management
Because Stamped.io does not publish documentation on multi-user team management, role-based permissions, or staff account controls, the true overhead of managing access manually is difficult to quantify with precision. What is clear: every app without structured offboarding or role controls creates the same category of risk - stale access that persists after staff turnover.
No official help center articles on adding or removing team members were found, which suggests access changes likely require direct account-owner intervention with no auditable workflow.
The decision
If your team needs structured, auditable access control across every app in your stack, Stamped.io's current documentation does not confirm that capability exists natively. The platform suits small e-commerce operators running single-owner accounts.
Larger teams or those with compliance requirements around access provisioning should verify directly with Stamped support whether staff account controls, role separation, or access logs are available before relying on the platform at scale.
Bottom line
Stamped.io is a capable reviews and loyalty tool for e-commerce, but its access management story is underdocumented.
No native SCIM, no published role-based permission model, and no help center guidance on team member management means every app-level access change likely falls to the account owner manually.
Teams with audit or offboarding requirements should treat this as a gap to investigate before expanding usage.
Automate Stamped.io 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.
