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

Mobile isn’t a “channel.” It’s where most shopping happens. 57% of e-commerce takes place on a phone now. So your commerce platform’s mobile capabilities aren’t a nice-to-have. They determine whether customers can actually buy from you.

I talk to companies that still treat mobile as a shrunken desktop site. That’s backwards. Design for the phone first. Then stretch it to the bigger screen.

SAP Commerce Cloud handles mobile through three layers: the Composable Storefront’s responsive Angular application, PWA capabilities, and OCC APIs optimised for mobile bandwidth. Here’s how each works and where the limits are.

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). Those numbers only go one direction.

Commerce Cloud’s mobile strategy works across three layers:

Layer 1 is the responsive Angular storefront. Components adapt to screen size. Grids collapse, navigation switches to hamburger, touch targets get sized for fingers. The basics, done properly. We had a client whose previous implementation used 32px touch targets on mobile. Thirty-two pixels. People were tapping the wrong thing constantly. The Composable Storefront defaults are sensible here.

Layer 2 is Progressive Web App (PWA). Add-to-home-screen, offline caching, push notifications, app-like navigation. No app store needed. No approval process. No update cycles. It just works.

Layer 3 is mobile-optimised APIs. OCC REST APIs return structured JSON. Responses can be tailored to reduce payload for mobile bandwidth. When you’re on a 3G connection in a Swiss mountain village (I’ve tested), this matters.

Do You Need a Native Mobile App?

For most commerce use cases, honestly no. PWA covers offline browsing, push notifications, add-to-home-screen, and app-like navigation. That’s enough for the vast majority of B2C and B2B scenarios.

Native apps are worth it when you need AR product visualisation, device hardware access (barcode scanning, GPS), heavy offline functionality (field sales), or dedicated B2B workflow apps. Fair enough if that’s your situation. But don’t build a native app just because someone on the board thinks you should have one in the App Store. I’ve seen companies spend 6 months and half a million on a native commerce app that got 200 downloads. PWA would’ve done the job.

If you do go native, Commerce Cloud’s OCC APIs serve it the same way they serve the web storefront. Same backend, different frontend. Clean separation.

What Mobile Performance Matters Most?

E-commerce accounts for 34% of B2B revenue (McKinsey, 2024). Mobile performance directly impacts that revenue. A slow mobile storefront is a leaky bucket.

Core Web Vitals to get crisp:

• 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

None of this is glamorous work. But it’s the difference between a crisp mobile experience and one that loses customers at every tap.

FAQ

Does Commerce Cloud support Apple Pay and Google Pay?

Yes, through payment gateway integration (Stripe, Adyen, PayPal). Configuration happens 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 still 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, so you can set up 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. You’ll need a native app or PWA camera API access. Several partner solutions add this capability.