Adobe Commerce

business.adobe.com ↗

Commerce for complex catalogues and company purchasing with approval rules

SI Score
80/100
Pricing
Contact for Pricing AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Adobe Commerce

Answers use saved listing facts and recorded sources.

What it does

Adobe Commerce supports B2C and B2B selling with catalogue, checkout and company-purchasing tools. Buyers can route purchase orders through rules based on value, shipping cost or distinct SKUs. Its complete commerce services and its separate Commerce Optimizer offering have quote-based pricing.

Adobe Commerce suits an organization coordinating more than a straightforward retail checkout. Its B2B company accounts can separate the people requesting purchases from the roles authorized to approve them. Integration tools connect payments, tax, shipping and back-office systems.

Set a company purchase-order rule

In a B2B company account with the required permissions, open Approval Rules > Add New Rule. Name it, choose the affected roles and set an order-total, shipping-cost or distinct-SKU threshold. Select the approving roles and save; the rule starts enabled.

Approving roles need a user. If a role contains only the order's buyer, that person's order is automatically approved. With several users, self-approval depends on the separate setting. Review role membership before relying on the rule as a spending control.

Select the service that fits the existing system

Offering Operating model Commerce engine
Adobe Commerce as a Cloud Service Managed multi-tenant SaaS Included
Adobe Commerce on Cloud Dedicated single-tenant PaaS Included
Adobe Commerce Optimizer Managed catalogue and storefront services Uses the existing engine

Optimizer does not replace the existing system's transactions, promotions or B2B engine. That distinction matters when replacing a platform versus improving its storefront and merchandising. All three require a pricing conversation; the published comparison gives no universal numeric fee.

Merchant administration requires an account created by an administrator. Standard sign-in uses a username, password and two-factor authentication; deployments using Adobe Identity Management Services use the corresponding Adobe credentials. Scope the company permissions and integrations as part of implementation.

Strengths

  • Purchase-order rules distinguish requesters from approving company roles
  • Complete commerce services and an existing-engine option support different implementation needs

Watch out for

  • Commerce Optimizer depends on an existing transaction and B2B engine
  • An approval role containing only the requester automatically approves their order

Best for

  • Commerce teams managing company purchasing and connected enterprise systems

Sources