Solve a need
Migrate to Revenue Cloud
You are changing tools, and nobody knows what will follow, what will be lost, or how long it will take.
How claims are labelled
You are changing tools, and nobody knows what will follow, what will be lost, or how long it will take.
The architecture
Scroll the diagram sideways
Attributes hang off the classification, not off the product. The category is only what the seller browses. Modelling them as one thing works until the first product needs to appear on two shelves, or two products of the same type need different attributes.
Use case
A bundle catalog that survives contact with sellers
Model bundles, options and regional variants without producing a catalog nobody can maintain.
Price a setup fee by volume tier
A setup fee that steps at a threshold, plus adders that scale with a count — without filling the pricing procedure.
Move pricing configuration between orgs
Why a pricing procedure that works in one org returns nothing in the next, and what has to travel together.
Migrate from Salesforce CPQ to Revenue Cloud
What transfers, what does not, and the distinction that makes most CPQ material inapplicable.
Guide
Procedure Plans: what to do when one pricing procedure is full
A pricing procedure has a ceiling. We hit it at 128 elements with another offer still to build. Here is what the ceiling actually is, why counting it is harder than it looks, and what splitting the procedure costs you.
A genuinely complex offer: tiered setup, adders, and twenty-one hardware variants
What it takes to model a managed-services offer where the setup fee steps at a headcount threshold, adders scale on a quantity that is not the seat count, and one bundle carries twenty-one appliance variants in three roles.
Pattern
Included allowances and overage
Express “the first N hours are included, beyond that you pay” natively — and find out why only one of your allowances applies.
Scaling past the procedure ceiling
What to do when one pricing procedure can no longer hold the logic of every offer.
Field note
Why a pricing procedure that works in one org returns nothing in the next
Pricing is not one artefact but five, and moving a subset produces a procedure that runs and prices nothing.
Products created by API can behave differently from identical ones created in the UI
A bundle built by bulk API refused to open the configurator. A hand-built equivalent worked. The records looked the same.