Mobile Commerce with SAP Commerce Cloud: Features, Performance, and PWA

Mobile isn’t a channel — it’s the dominant way people shop online. When 57% of e-commerce happens on mobile, your commerce platform’s mobile capabilities aren’t a nice-to-have. They determine whether customers can buy from you.

SAP Commerce Cloud handles mobile through three layers: the Composable Storefront’s responsive Angular application, PWA capabilities, and OCC APIs optimised for mobile bandwidth.

TL;DR: Mobile commerce reached $2.07 trillion in 2024 — 57% of total e-commerce, projected to hit 59% ($2.51 trillion) by 2025 (Oberlo, 2025). Commerce Cloud handles mobile through the Composable Storefront (responsive Angular + PWA), OCC APIs (bandwidth-efficient REST), and CMS-driven mobile layouts. PWA bridges the gap without requiring a native app.

How Does Commerce Cloud Handle Mobile?

Mobile commerce reached $2.07 trillion in 2024 — 57% of total e-commerce. The global mobile commerce market is valued at $2,239 billion in 2025, projected to reach $5,010 billion by 2034 at 9.5% CAGR (Fortune Business Insights, 2025).

Commerce Cloud’s mobile strategy operates across three layers:

Layer 1: Responsive Angular storefront. Components adapt to screen size — grids collapse, navigation switches to hamburger, touch targets are sized for fingers.

Layer 2: Progressive Web App (PWA). Add-to-home-screen, offline caching, push notifications, app-like navigation — without an app store.

Layer 3: Mobile-optimised APIs. OCC REST APIs return structured JSON. Responses can be tailored to reduce payload for mobile bandwidth.

Do You Need a Native Mobile App?

For most commerce use cases, no. PWA covers offline browsing, push notifications, add-to-home-screen, and app-like navigation.

Native apps are worth it for: AR product visualisation, device hardware access (barcode scanning, GPS), heavy offline functionality (field sales), and dedicated B2B workflow apps.

If you build native, Commerce Cloud’s OCC APIs serve it the same way they serve the web storefront.

What Mobile Performance Matters Most?

E-commerce accounts for 34% of B2B revenue (McKinsey, 2024). Mobile performance directly impacts that revenue.

Core Web Vitals to optimise:

• LCP — main image within 2.5s on mobile. Use responsive images, lazy loading, CDN.
• INP — reduce JavaScript bundle through lazy loading and code splitting.
• CLS — set explicit width/height on images, reserve space for dynamic content.

Commerce Cloud-specific optimisations:

• Image compression and WebP format negotiation
• CDN caching for static assets and API responses
• SSR to reduce time-to-first-meaningful-paint
• Lazy loading for below-the-fold product images
• Optimised search API responses for mobile product cards

FAQ

Does Commerce Cloud support Apple Pay and Google Pay?

Yes, through payment gateway integration (Stripe, Adyen, PayPal). Configuration is at the gateway level, not Commerce Cloud itself.

How does the storefront handle poor connectivity?

PWA service worker caches previously browsed products and static assets. Transactions require connectivity — checkout can’t complete offline.

Can I have different layouts for mobile and desktop?

Yes. Responsive CSS adapts components. SmartEdit CMS also supports page variants — different content slot layouts for mobile and desktop.

How does mobile search work?

Same Solr engine powers both. The storefront adapts the UI: full-screen search overlay, touch-friendly filters, swipeable facet panels.

What about barcode scanning for B2B?

Commerce Cloud doesn’t include native scanning. This requires a native app or PWA camera API access. Several partner solutions add this capability.