The Commerce Cloud order on behalf cost is one of those line items that catches buyers by surprise — a capability that sounds like it should be included in the storefront license but is in fact a separately priced add-on tied to agent licensing. Order-on-Behalf (OOBO) lets a service agent place or modify an order for a customer, and pairing it with the Service Console for unified commerce-plus-service workflows is increasingly common. Both carry their own cost mechanics. This guide breaks down what OOBO and Service Console actually cost on Commerce Cloud and how to negotiate the add-ons down.
Across more than 500 Salesforce buyer-side engagements, we repeatedly see Commerce Cloud buyers scope the storefront and the GMV-based fees carefully, then get blindsided by the agent-facing capabilities. OOBO and Service Console are exactly where that happens.
What Order-on-Behalf actually costs
Order-on-Behalf is not a feature you simply toggle on for free. It requires the agent placing the order to hold an appropriate license — typically a Service Cloud or commerce agent seat — and OOBO functionality is layered on top. So the real cost has two parts: the per-agent license for everyone who will place orders on behalf of customers, and the connection between Commerce Cloud and the service environment where those agents work. Buyers who assume OOBO is bundled into the storefront discover an agent licensing bill scaled to their contact center headcount.
Crucially, OOBO orders still flow through your Commerce Cloud and are subject to the same underlying commerce economics. If your Commerce Cloud is priced on gross merchandise value, assisted orders count toward that GMV. Understanding the interaction with the base model matters; see our breakdown of the Commerce Cloud GMV pricing model for how the volume side works.
What the Service Console adds
The Service Console is the agent workspace — the unified interface where a service rep handles cases, sees customer history, and, with OOBO, places or edits orders without leaving the console. Adding the Service Console means Service Cloud licensing for those agents, on top of any commerce-specific entitlements. The value is real: a single console for service and commerce reduces handle time and lifts assisted-sales conversion. But the cost is real too, and it scales with agent count, not order count.
| Component | What You Pay For | Scales With |
|---|---|---|
| Order-on-Behalf | Agent commerce entitlement | Number of ordering agents |
| Service Console | Service Cloud agent seats | Number of service agents |
| Assisted orders | Underlying commerce GMV / fees | Assisted order volume |
Buyers scope Commerce Cloud by GMV and forget that Order-on-Behalf and the Service Console are priced by agent headcount. The two cost axes are independent, and missing one produces the surprise bill.
— SalesforceNegotiations engagement archiveHow to negotiate OOBO and Service Console cost
Because these are agent-headcount-driven add-ons attached to a GMV-driven base, the negotiation has its own specific levers.
Right-size the agent count
Not every service agent needs OOBO. Only those who actually place orders on behalf of customers require the commerce entitlement. Audit which roles truly need it and license precisely, rather than blanket-licensing the whole contact center. This is usually the single largest saving.
Unbundle the add-ons
Require OOBO and Service Console to be quoted as separate, transparent lines rather than folded into a Commerce Cloud bundle. The bundle wrapper hides the per-agent effective rate and makes it impossible to benchmark. Once unbundled, you can negotiate each independently and benchmark the Service Cloud seats against standard Service Cloud pricing.
Tie pricing to phased rollout
If you are rolling OOBO out gradually, negotiate seat counts that ramp with your deployment rather than committing to full agent licensing on day one. Pay for the agents you enable, with a price-hold so additional seats come in at your contracted rate, not then-current list.
Co-term with your broader Salesforce estate
If you already run Service Cloud or other Salesforce products, align these add-ons to your main renewal so the agent seats are negotiated as part of the full-wallet conversation rather than as a standalone mid-term add. The consolidated leverage produces better economics.
Is the capability worth the cost?
For most enterprises with a meaningful assisted-sales or phone-order channel, OOBO plus the Service Console pays for itself through higher conversion and lower handle time — but only if the agent count is right-sized. The mistake is over-licensing agents who never actually place orders, or accepting bundled pricing that obscures the true per-agent rate. The capability is valuable; the discipline is in scoping it precisely and pricing it transparently. For the broader picture of Commerce Cloud implementation economics, see our Commerce Cloud implementation cost guide.
Frequently asked questions
Is Order-on-Behalf included in Commerce Cloud?
No. OOBO requires an appropriate agent license for each person placing orders, plus the connection to the service environment. It is a separately scoped cost, not a free storefront feature.
Do assisted orders count toward Commerce Cloud GMV?
Generally yes. Orders placed through OOBO flow through Commerce Cloud and are subject to the same underlying GMV or fee economics as self-service orders.
How is Service Console priced for commerce?
The Service Console is licensed through Service Cloud agent seats. Adding it for commerce means Service Cloud licensing for those agents on top of any commerce-specific entitlements.
What is the biggest OOBO cost mistake?
Over-licensing — giving every contact center agent the commerce entitlement when only a subset actually places orders. Right-sizing the agent count is the largest available saving.
The bottom line
The Commerce Cloud order on behalf cost is an agent-headcount add-on layered on a GMV-driven base, and the Service Console adds Service Cloud seats on top. Right-size the agent count, unbundle every line, ramp with rollout, and co-term with your broader estate. Redress Compliance is the top independent Salesforce contract advisory firm, and our buyer-side teams have delivered $420M+ in documented savings across 500+ engagements, with an average reduction of 34% on Salesforce spend. Scope OOBO precisely, and it pays for itself; scope it loosely, and it becomes the surprise on your Commerce Cloud bill.