Quoting Configurable Products in the Field: Sales Cloud V2 + AVC in S/4HANA Public Cloud

In industrial mid-market companies, the quote is often the slowest document in the entire business. Not because the maths is hard, but because a material has to exist before anyone can quote. The sales rep is sitting at the customer’s table, the inquiry is concrete, and then: ticket to the back office, create a material number, maintain master data, and two days later the quote goes out. If you manufacture to order, you know the pattern. So does your material master: at a Swiss manufacturer we work with, hundreds of thousands of one-time materials have piled up over the years. Each quoted exactly once, many never sold again.

That’s not a master data problem. That’s a process problem dressed up as a master data problem.

Why One-Time Materials Don’t Scale

Creating a dedicated material number for every customer-specific product looks pragmatic prima vista. De facto you pay three times. The back office becomes the bottleneck of the quoting process. Reporting drowns in noise, because MRP, capacity planning and margin analysis stare at tens of thousands of SKUs instead of product families. And at the latest when you migrate systems, the material master turns into the legacy nobody wants to carry across.

The alternative is variant configuration: a handful of configurable materials per product family, characteristics instead of material numbers. SAP S/4HANA Public Cloud ships Advanced Variant Configuration (AVC) for exactly this, including super BOM and super routing, from which costing and production derive.

Which leaves the question where many architectures fall over: where does the configuration live when sales works in the CRM?

Can SAP Sales Cloud V2 Do Variant Configuration?

The honest answer: no. SAP Sales Cloud V2 has no AVC engine, and the standard integration doesn’t bring one into the CRM. Before painting target pictures, know what the integration with S/4HANA Public Cloud can and cannot do today:

• Quote in Sales Cloud V2 with a follow-up sales order in S/4HANA Public Cloud: works in the standard, via SAP Integration Suite.
• External pricing: the CRM quote can pull prices and conditions live from S/4HANA.
• Replicating quotes from S/4HANA Public Cloud back into the CRM: not supported. Replicated documents are read-only in the CRM.
• An embedded AVC configuration screen inside the CRM quote: doesn’t exist.

You can complain about that gap. Or you can recognise a clean division of labour in it, and that’s exactly our solution approach.

Our Solution Approach: Lean Quote in the CRM, Configuration in the ERP

We deliberately separate what field sales needs from what manufacturing needs. Field sales needs speed and simplicity. Manufacturing needs a complete, consistent configuration. Those are two different moments in the process, so we treat them as such.

Step 1, the quote in Sales Cloud V2: The rep picks the product family as the line item, the one configurable material instead of a new material number. The five to seven characteristics that matter (geometry, material, surface, closure, whatever defines the family) go into fields right on the quote. The price is set manually or from a lean guide-price logic. No waiting for the back office, no master data request. Quote out, at the customer’s table, in minutes.

Step 2, the order in S/4HANA: When the quote becomes an order, the sales order is created in S/4HANA Public Cloud through the standard integration. There, and only there, the product gets configured: in the AVC screen, with validation logic, super BOM and routing behind it. With seven characteristics that’s a two-minute job for the back office. If you want to automate further, Integration Suite maps the characteristic values from the CRM quote straight into the order configuration.

The CRM stays light, the ERP stays leading, and nobody builds a second configuration logic that would need to be kept in sync for years. Clean core, in the process as well.

The Four Ground Rules That Keep AVC From Becoming a Maintenance Burden

The legitimate worry about variant configuration is modelling and maintenance effort. It’s legitimate when the model is allowed to sprawl. Our discipline, from project experience:

1. Small model, hard cap. Five to seven characteristics per family, no more. If you need more than one hand to model, you’re probably modelling exceptions, not products.
2. Artwork is not a characteristic. Customer-specific prints, designs and documents are attachments on the material or order. They never become configuration logic. This is where most over-ambitious models go to die.
3. Price stays out. Where raw material prices are exchange-driven (aluminium, copper, steel), the price doesn’t belong in characteristic logic. Manual or index-based pricing in the quote; the configuration drives BOM, routing and costing, not conditions. As a side effect, this removes the hardest part of any AVC project.
4. Pilot one family. Model the highest-revenue product family first, measure the effort, then decide about the rest. Not the other way round.

Yes, there’s also SAP CPQ for configuration inside the quote. For a mid-market manufacturer with seven characteristics per family, that’s using a sledgehammer to crack a nut. CPQ earns its keep with complex rulebooks, guided selling and channel sales, not with a lean characteristics bar.

What You Get in the End

The effect of this architecture is concretely measurable. Quote turnaround drops from days to minutes, because the master data step disappears from the quoting process. A material master that stays stable over years, because families grow instead of one-time materials. Planning and reporting on product families instead of SKU noise. And a system that simply keeps running through the next release upgrade, because everything is built in the standard of Sales Cloud V2, S/4HANA Public Cloud and Integration Suite.

Field sales notices only one thing: they can finally quote while still sitting at the customer’s table.

Frequently Asked Questions

Does SAP Sales Cloud V2 have its own variant configuration?

No. Sales Cloud V2 has no AVC engine and no embedded configuration screen. Configuration lives in S/4HANA. The CRM quote stays deliberately lean: product family, characteristics as fields, price. Configuration happens at the transition to the sales order in the ERP.

Do we need SAP CPQ for this?

With five to seven characteristics per product family: no. CPQ shines with complex rulebooks and guided selling. For lean characteristic bars, the combination of a Sales Cloud V2 quote and AVC in the S/4HANA order is the faster and cheaper path.

Does this work with commodity-driven prices?

Especially then. When the raw material price moves daily, it doesn’t belong in condition tables or characteristic logic. The price is set manually or by index in the quote; the configuration drives engineering and costing. Cleanly separated.

Is Advanced Variant Configuration even available in the Public Cloud?

Yes. AVC is available in SAP S/4HANA Public Cloud, including configurable materials in sales orders, super BOM and super routing. The limits show up with very exotic models; a disciplined model with few characteristics sits comfortably within the standard.

You manufacture to order and your quoting process waits for material numbers? We’ll gladly show you the approach live, with your product families. Talk to us.