Five building blocks. Each one touches the ERP somewhere, and that is where we look first.
Accounts, pipeline, visit planning, quotes and forecasts for B2B sales teams, on the desktop and in the mobile app. We configure the standard first and extend on SAP BAIP only where your process really differs. Joule summarises accounts and drafts follow-ups where it saves time.
The ERP seam: prices, availability and orders live in the ERP. The quote a rep sends has to be the order the ERP can post.
SAP Sales Cloud V2 →SAP CPQ →
Cases, SLAs, knowledge articles and a customer portal, with email, phone and chat in one inbox. CTI shows the caller before the agent picks up. For work on site we connect SAP Field Service Management, so the technician sees the same case as the back office.
The ERP seam: a case is only solved when the installed equipment, warranty and spare parts from the ERP are part of it.
SAP Service Cloud V2 →SAP Field Service Management →
B2B and B2C shops with contract prices, large catalogues, punch-out and self-service ordering. Commerce is where Spadoom started. Franke launched its Commerce platform in 90 days and received an SAP Quality Award for it.
The ERP seam: every order has to post in the ERP with the right price and stock, the first time, and the buyer wants to see delivery and invoice status in the shop.
SAP Commerce Cloud →
Campaigns, segments and automations across email, mobile and web, formerly known as SAP Emarsys. We set up the data feeds first, then the programmes, so the first campaign does not go out to an outdated list.
The ERP seam: an audience is only as good as the customer and order data behind it, from the CRM, the shop and the ERP.
SAP Engagement Cloud →
One customer profile and one login across shop, portal and apps, with consent you can prove under the revised Swiss Data Protection Act and the GDPR. For Medion we built a unified identity layer for its European e-commerce, with single sign-on and consent management.
The ERP seam: customer numbers, account hierarchies and contract data must match the ERP master data, or the profile tells a different story than the invoice.
Customer Data Platform →Customer Identity (CIAM) →