Use case · Retail & e-commerce
Extending one SAP Commerce platform to serve many retail brands and countries
Custom SAP Commerce Cloud extensions for local payments, couriers, loyalty, vouchers, search and data integrations, deployed with Helm across environments.
Client details are kept confidential. This use case describes the problem and what we built.
The brief
The client is a multi-brand retail group that runs online stores for several brands across a number of markets on a single SAP Commerce Cloud platform.
MultiGenesys engineers contributed to the platform’s custom extensions and integrations, the work that turns a standard commerce suite into storefronts that fit each market’s payments, logistics and customer programs.
The challenge
What needed solving
One codebase, many markets
Several retail brands in different countries ran on one commerce platform. Each market needed its own payment methods, couriers, tax invoices and storefront behavior.
Deep integration with retail systems
Orders, stock, product content, customer data and promotions had to stay in sync with point-of-sale, product-information, content and CRM systems.
Customer engagement features
Loyalty, vouchers, subscriptions, e-wallets, OTP and push notifications were needed to keep shoppers coming back.
Safe change at scale
With more than a hundred custom extensions, every change had to pass automated tests and security scans before it reached production.
The solution
What we built
Custom SAP Commerce extensions
Over a hundred custom extensions on SAP Commerce Cloud (Hybris) add market-specific storefront add-ons, back-office tools and business logic on a shared core.
Local payments and logistics
Integrations with regional payment gateways, card and wallet providers, and courier and postal services, each packaged as its own extension.
Loyalty and promotions
Vouchers, coupons, offers campaigns, subscriptions, e-wallets and loyalty achievements built into checkout and the customer account.
Data integration
Kafka-based integration, hot-folder imports from cloud storage, product-information and digital-asset integrations, CRM sync and commerce data migration tools.
Search tuning
Market-specific Solr configurations and a search rule engine improve relevance for each storefront's language and catalog.
Cloud delivery and testing
Docker images and Helm charts for development, UAT and production, SAML single sign-on for back office, New Relic monitoring, API tests, UI automation and SAST/DAST scanning.
The outcome
What changed
New markets on a shared core
Market-specific needs are added as extensions, so new countries and brands reuse the same platform instead of forking it.
Local checkout options
Shoppers in each market can pay and receive orders through the methods common in that market.
Repeatable releases
Helm-based deployments with automated API, UI and security testing give each release a consistent path to production.
Technology used
- SAP Commerce Cloud (Hybris)
- Java
- Spring
- Apache Solr
- Apache Kafka
- MySQL
- Azure Storage
- Docker
- Kubernetes
- Helm
- New Relic
- Postman
- Selenide
- Cucumber
Related use cases
Keeping product options, swatches and SKUs accurate across every channel
Microservices for product options, color swatches and SKUs, with bulk upload, approval workflow and Kafka sync from PIM, pricing and inventory systems.
Read the use caseManaging multi-site store build-outs: projects, RFIs, change orders and punch lists
A construction project management platform for brands rolling out stores, with Gantt schedules, RFIs, change orders, punch lists, approvals and fine-grained access.
Read the use caseRunning a B2B hotel-distribution business on one admin, supplier and pricing back end
Admin and supplier services for hotel rates, availability, rate plans, buyer margins, wallets and virtual cards, with queue-based pricing updates on AWS.
Read the use caseHave a similar problem to solve?
Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.