SAP CX for Manufacturing: How Commerce, Service and Sales Cloud Support Industrial B2B

Selling and serving industrial products is a different job from retail. A manufacturer sells configurable products with thousands of variants, at prices negotiated per contract, to buying organisations with approval rules, and then services the equipment for years. A CX platform that cannot represent that complexity ends up as a brochure website with a contact form.

Most of our customers are manufacturers, from Franke and BDTronic to Nussbaum and Lindt & Sprüngli’s factory maintenance team. This post walks through the manufacturing requirements we meet in almost every project and how each SAP CX product handles them.

TL;DR: SAP CX covers the three places where manufacturing CX gets hard. Commerce Cloud handles complex B2B ordering (configurable products, contract prices, approval workflows, spare parts). Sales Cloud V2 manages long sales cycles with ERP prices and availability in the quote. Service Cloud V2 links cases to installed equipment and spare parts, with SAP Field Service Management for on-site work. What makes it work is the connection to the ERP, so plan CX and ERP together.

Why is manufacturing CX different?

In a manufacturing company much of the customer knowledge sits in people’s heads. An experienced sales rep knows each customer’s contract prices, minimum order quantities, lead times and which variants make technical sense. The CX challenge is not putting a catalogue online; it is making that knowledge available digitally, to customers and to new colleagues.

Five requirements come up in nearly every manufacturing project:

Configurable products. A valve manufacturer does not sell one valve. It sells thousands of variants by material, size, pressure rating, connection type and coating. The platform has to support configuration with rules that prevent invalid combinations, otherwise you ship parts that do not fit together.

Customer-specific pricing. Every customer has its own conditions. A distributor in Germany pays different prices from one in Italy, and both differ from a direct customer. Volume tiers, contract prices and promotions are maintained in the ERP and must appear correctly everywhere.

Approval workflows. B2B orders often need internal approval. A plant manager may approve orders up to a set amount, larger ones need procurement sign-off. The platform must support these multi-level chains.

Spare parts. Customers need parts for equipment they already own. The parts catalogue has to be linked to serial numbers and installed base records, so customers only see compatible parts.

Long sales cycles. Capital equipment deals run for months with several decision-makers, technical evaluations and competitors. The CRM must track all of that over a long period.

How does SAP Commerce Cloud handle manufacturing B2B?

SAP Commerce Cloud brings the B2B functions manufacturers need as standard. SAP has been named a Leader in the Gartner Magic Quadrant for Digital Commerce for eleven consecutive years (SAP News, 2025), and that position rests largely on B2B depth.

Buying organisations. Model the customer’s structure: headquarters, regional offices, plant-level buyers, procurement. Each level gets its own permissions, budgets and approval rules.

Customer-specific catalogues and prices. Each customer sees only the products it may buy, at its own prices. Prices come from SAP S/4HANA, so a contract change in the ERP shows up in the shop without a manual update.

Product configuration. Guided selling for configurable products: the buyer chooses size, material and finish, and rules validate the combination before it goes into the cart. For complex configurations, SAP CPQ takes over. For BDTronic, we replaced manual quotes for dispensing and bonding systems with SAP CPQ and guided selling (BDTronic story).

Requisition lists and quick order. Industrial buyers reorder the same items. Requisition lists store them for reordering in one step; quick order lets buyers enter part numbers directly.

Self-service order management. Customers check order status, deliveries and invoices in the shop instead of calling customer service.

For Franke, a stalled Commerce Cloud platform went live in 90 days and manual orders fell by 75%; the project received the SAP Quality Award for “Rapid Time to Value” (Franke story). As in most of our commerce projects, the standard B2B functions carried the bulk of the requirements, and the company-specific logic runs as extensions on SAP BTP, which keeps the core standard and upgrades predictable. If you are comparing implementation partners for this, see the best SAP Commerce Cloud partners in Switzerland.

How do Sales Cloud V2 and Service Cloud V2 support manufacturing?

SAP Sales Cloud V2 for manufacturing:

• Long-cycle opportunities: deals tracked over months, with several contacts, technical evaluations and competitors on record.
• Quotes with ERP data: prices, availability and lead times come from S/4HANA, so the sales rep quotes what the shop and the order confirmation will show.
• Account view: open orders, deliveries, invoices, service cases and installed equipment per customer on one screen.
• Joule: account summaries, suggested next steps, email drafts and alerts on deals where activity has stalled.

Nussbaum, a Swiss packaging manufacturer, went from scattered data to one sales platform on Sales Cloud V2 in five months, consolidating three data sources (Nussbaum story). More manufacturing scenarios are in SAP Sales Cloud V2 for manufacturing.

Service Cloud V2 for manufacturing:

• Installed base: cases linked to the specific machine and serial number, so the agent sees product, configuration, warranty and maintenance history.
• Spare parts: from the case, agents check availability in S/4HANA and create a parts order without leaving Service Cloud.
• Field service: cases that need a technician on site move to SAP Field Service Management for scheduling, dispatch and mobile work orders. For factory maintenance at Lindt & Sprüngli’s Aachen plant, we implemented SAP FSM with mobile work orders and spare parts visibility (Lindt story).
• Knowledge base: technical documentation, troubleshooting guides and service bulletins searchable by product and serial number. The product documentation is on SAP Help.

What does the ERP connection change for manufacturing CX?

For manufacturers, the value of SAP CX grows with how closely it is connected to the ERP. The S/4HANA connection delivers what other CX platforms need custom middleware for:

• Current prices: customer-specific conditions, volume discounts and promotions from S/4HANA, not a copy from last night’s batch run.
• Available-to-promise: delivery dates checked against stock and production planning, so customers get realistic dates.
• Order to cash: orders flow from Commerce Cloud to S/4HANA for delivery, invoicing and posting without re-keying.
• Installed base: equipment records from S/4HANA reach Service Cloud V2, so agents see the current configuration and warranty.

This is also where most CX projects run into trouble: the order that will not post, the price the quote cannot resolve, the service case with no material behind it. That is why we deliver SAP S/4HANA Public Cloud and the CX products with one team. How the two fit together is described in S/4HANA Public Cloud and Sales Cloud V2 as one integrated stack; if you are planning the ERP and the customer side together, the transformation overview is a good starting point.

For Swiss manufacturers, our page on SAP CX consulting in Switzerland shows how one team connects Sales and Service Cloud V2 to the ERP behind them.

FAQ

Can SAP CX handle product configuration for complex manufactured goods?

Yes. SAP CPQ handles rule-based configuration (valid combinations, dependent options, price effects) and passes the result to S/4HANA for production and ordering. Commerce Cloud’s built-in variant management is enough for simpler product ranges. Which one you need depends on how many rules your products carry, which is worth checking in a short workshop before licensing.

Is SAP CX worth it for a mid-sized manufacturer?

It depends on order volume and complexity rather than company size. If a large share of orders still arrives by phone or email, prices are customer-specific and the ERP is SAP, self-service ordering and ERP integration usually pay off. If the product range is small and prices are uniform, a lighter set-up may be enough; we say so in the first conversation.

How does SAP CX compare to Salesforce for manufacturing?

SAP’s advantage is the native connection to SAP ERP: prices, availability, orders and installed base without a separate integration platform. Salesforce offers a larger ecosystem of third-party apps. For manufacturers on S/4HANA, the ERP connection usually decides; for manufacturers on a non-SAP ERP the comparison is more open.

Can I start with one CX product and add others later?

Yes. Many manufacturers start with Commerce Cloud to move routine orders into self-service, or with Sales Cloud V2 for pipeline visibility. Service Cloud V2 and FSM follow when the service organisation needs more structure. Plan the shared account and product master from the start so each new product builds on it.

What about IoT and connected equipment?

SAP CX can connect to machine data through SAP BTP. A sensor alert can open a service case in Service Cloud V2, suggest spare parts in Commerce Cloud or notify the account manager when a machine approaches the end of its life cycle. These scenarios are built per project on BTP, so start with one use case that has a clear business owner.