Kai Heinricy
Introduction
Although SAP Customer Checkout (CCO) provides a broad set of standard features, retail environments often have specific process requirements that go beyond its out-of-the-box functionality. SAP CCO addresses this by offering an open extension framework, both within the POS itself and through the Customer Checkout Manager (CCOM).
This approach makes it possible to implement customer-specific features, integrations, and UI customisations in a way that is easy to maintain and remains compatible with future releases.
What are some common POS requirements?
Typical extension requests from retail stores and commercial businesses include:
- Additional information or QR codes printed on receipts
- Integration with third-party systems, such as CRM systems, payment providers, or partner solutions
- New POS features, including deposit returns, voucher validation, and age verification
- UI enhancements to streamline daily operational processes
- Special promotions that cannot be handled with standard functionality
- Store-specific rules or workflows
All of these requirements have one thing in common: the solution must operate at the POS in a simple, fast, and reliable way.
SAP Customer Checkout – Plug-in concept
The POS system offers a clearly structured plug-in framework with the following capabilities:
- Development in Java
- Access to events and business objects (e.g. during item scanning or payment completion)
- Extension of the POS layout, including new buttons and dialogues
- Custom business logic for discount rules, receipt actions, etc.
- Maintenance-friendly design, with SAP ensuring compatability across releases
As a result, plug-ins run locally on the POS and respond in real time. When a plug-in (JAR file) is removed from the plug-in directory, the POS automatically returns to standard operation. This approach enables a high degree of flexibility in day-to-day store operations.
SAP Customer Checkout Manager – API concept
SAP CCOM provides REST-based APIs for a wide range of use cases, including:
- Synchronisation: materials, customers, prices, and authorisations
- Transaction data: transmission to SAP S/4HANA or third-party systems
- Administrative functions: store control and monitoring
- Gift cards, loyalty, and coupons
These APIs make it possible, for example, to integrate external loyalty systems, connect third-party gift card platforms, and link centralised campaign logic.
Plug-in management und updates
Developing plug-ins requires a certain level of expertise, both to set up the development environment and to identify the right extension points. This often involves a combination of different methodologies or UI adjustments. In general, it is important here to stay close to the standard to ensure that plug-ins remain scalable and usable across future feature packs.
Major updates, known as feature packs, are typically released four times a year. Minor updates are delivered at the patch level as and when fixes are needed. There are no hotfixes, only patch-level updates, and the lifecycle of each feature pack is defined by SAP’s official guidelines.
SAP CCOM should also be kept on a similar version level as CCO. While the APIs continue to be supported, UI customisations may change between releases and should therefore only be used with caution.
New tool: RBO CCO Launchpad
A plug-in needs to be compatible with the corresponding manifest (the plug-in version and feature pack). This means that when a POS system is upgraded to a new feature pack, the plug-in manifest usually needs to be updated and the file manually replaced in the system.
To make things easier, we at RBOmnishore have developed the RBO CCO Launchpad – a central platform for monitoring, removing, and deploying plug-ins across multiple POS systems. More information about the CCO Launchpad can be found here.
Summary
With its plug-in and API-based concept, SAP Customer Checkout offers room for flexible customisations alongside its standard functionality. This includes:
- Flexible extensions for custom POS requirements
- Easy maintenance
- Compatibility with future releases
- Support for international retail processes
Overall, SAP CCO provides a solid, future-ready platform for building tailored POS solutions that support multiple channels and are ready for the cloud.
Sound interesting?
Want to learn more about SAP Customer Checkout? Feel free to reach out to us – no strings attached.
Articles recommended for you
Choosing the right POS system (1) – Introduction
A modern POS system needs to do much more than simply scan items and print receipts. Customer expectations, legal requirements, and omnichannel workflows have transformed the checkout area into a central control hub of every store. SAP Customer Checkout delivers a compliant, SAP-native solution that runs offline and deploys fast.
Choosing the right POS system (2) – SAP Customer Checkout Cloud Edition
SAP Customer Checkout Cloud Edition is a cloud-based POS solution for international retail – fully SAP-integrated, scalable, compliant, and built for modern omnichannel operations
Choosing the right POS system (3) – Gift cards, loyalty and coupons
SAP Customer Checkout provides a powerful omnichannel solution for retailers, complete with built-in gift card, loyalty, and coupon features. In this article, we’ll take a closer look at how these modules work and the benefits they offer.