What it does
Broadleaf Commerce provides modular commerce capabilities for multiple brands, buying models and catalogs. Its change-management services can keep proposed data changes separate while authors and approvers prepare them for the storefront.
A seasonal catalog update can begin in a user's isolated workspace, called a sandbox. Broadleaf moves proposed changes through approval before applying them to live records. An approver can reject a change for revision; authorized staff can release approved work immediately or schedule it.
Catalogs group merchandise for channels or regions, while an application determines what shoppers can see. Approval workspaces can merge changes from several people. Changes are merged field by field, with the latest change winning, so coordinate editors working on the same information.
Administrative access requires a user with an assigned role. In Security / Users, configure roles and access to the relevant stores. A connected identity provider can handle login and, with the appropriate setup, roles. Externally managed roles update when the person signs in again.
A vendor or partner quote defines the licence, deployment and term. Updates require an eligible support contract or service subscription. Include that ongoing access when planning a customized store.
Strengths
- Proposed catalog changes can pass through review before reaching live records
- Approved changes can be scheduled for a future release
Watch out for
- Concurrent edits use the latest change for each field
- Update access depends on the support contract or service subscription
Best for
- Commerce teams implementing governed catalog changes across brands or regions
Sources
- Broadleaf Commerce | Composable Commerce Platform & Managed PaaS (Oct 26, 2026)
- Sandbox Services - Overview - Broadleaf Dev Central (Oct 27, 2026)
- Data Workflow Overview - Broadleaf Dev Central (Oct 27, 2026)
- Commercial License | Broadleaf (Oct 27, 2026)
- Admin User Management via Third-Party Authentication Provider (Oct 27, 2026)