GK OmniPOS

Architecture
 Shopping Evolution

The Cloud

POS SCO Kiosk MPOS Forecourt Scan & Go – Apps Scan less Touchless Frictionless

2
 OmniPOS - Not Just POS

API First
• No customer specific Branches,
• all customization based on public APIs
• Easy to upgrade

GK Separation of UI and Business Logic

• Provide POS functionality to all Channels and Touchpoints

Pluggable extensions
• Extend functionality without development
• Support external Apps (App Enablement)

3
 Traditional / Legacy POS Applications

• Monolithic
Frontend
• Everything on the POS
• We still offer this: Full POS
Business Logic

Hardware
Layer

DB
4
 GK OmniPOS - Separation of Client and Business Logic

• Separation of Client and

Business Logic Frontend

• Usage of Service Locator

Pattern
Business Logic

Hardware
Layer

DB
5
 Exposure of Business Logic as Services
OmniPOS Thin Client

Frontend • Java
Mobile POS • Swing
Hardware
Layer • Windows & Linux
• HTML5 App
Frontend
• IOS & Android
Hardware
Layer • Windows & Linux

HTTP/S

Service POS Service

HTTP/S
• RESTful
• JSON and XML
Business Logic

Headless… Food Ordering Kiosks

BYOD… Mobile Ordering Hardware Layer
BYOD… Mobile Pump Start DB
6
 Platform benefits
Transaction AI Omnichannel Mobile
eCommerce Returns ERP Orders services Services price service services

www ERP

Adapter to central systems ( Internal / External )

Authentication Pricing Loyalty

POS Service / Transaction Engine Tax Inventory Customer

Microservices
OmniPOS Orchestration Services

Realtime basket calculation

Store eComm / Webshop / OMS

Mobile Mobile Inventory Kiosk ESL Apps

Point Of Self Kiosk
devices customer
7
Sale Checkout
 CRM flow

Services

Price Interfaces
External
Promotion

Orchestration Layer
Tax
Client
Coupon

Customer Interfaces
GK Internal

Order

8
 The GK Retail Suite – Consolidated deployment view
Decentralized Stores

Store Type 4

Centralized
Stores
Store Type 3
No Local Services
Store Type 2
POS Service

Store Type 1
Mobile/ Thin Offline
Support

Apache Tomcat

Fuel Service*
Hybrid InfoService
Config Service
Application Service
T+ Payments Store Edge Server

Back Office
* Only for fuel stores POS Service Functionality
Central EJ & Reporting

Store Edge Server

Good internet connection - small offline periods Poor internet connection - longer offline periods
9
 The GK Retail Suite – Store Deployment Options
Store Type
4
All Services Deployed to Store

Store Edge Server

Store Type
3
Services for offline support of Mobile & Thin Client

Store Type 2
Services for Backup and Consolidation of
Config, Master Data, Payments, Fuel
Store Type 1 Centralized
No local services Deployments

Decentralized
Deployments

Good internet connection - small offline periods Poor internet connection - longer offline periods
10
 Flexible Deployment Choices

GK/Retail Applicatiion Services

GK/Retail DB

E Journal
Reporting
Database Universal Returns
Server POS POS (BO)
Connector Charge Backs
Service Server
(UCON)

Oracle, MS SQL Tomcat, Kubernetes

Central

Store
Decentralized
Store type 1 Store type 2 Store type 3 Store type 4 Store
Apache Tomcat Apache Tomcat Tomcat + Docker
On Edge Server

Smaller stores Store

Medium Stores Persistence Store Edge
Server (POS/Back office)
Large stores
Good online infrastructure. Small offline periods Poor online infrastructure, longer offline periods.
11
 Deployment Options
GK/Retail Central DB GK/Retail Central Systems

OmniPOS CEJ DB
POS POS (BO) Store Device Cluster Universal
Service Server Control Infrastructure Connector
(SDC Service) Service (UCON) E Journal
Reporting
HANA, Oracle, MS SQL Tomcat, Kubernetes Returns
Central Charge Backs

Store
Type 1 Type 2 Type 3 Type 4
Thin Store Hybrid Thick Store Decentralized Store
•Central Environment • Central Environment •Additional Store Server/Store Hub •All Central Service Running on
•No Store Servers • Additional Store Server/Store Hub (optional HW requirement) local servers at store space
(minimal HW requirement) •Local POS Service (Transactional •Full offline services
•Thin clients only
• Store Hub for redundancy and local Database)
• OmniPOS / Mobile POS / BYOD
API
•Central Environment Data
•All Calls go to central API / • i.e. transaction service, price & Promotions
•Thin clients connect to local store Synchronization
Services server or enterprise service

Decentralized
Type 4 Store
Type 2 Type 3
Type 1

Poor online
Store Edge Server
Tomcat infrastructure,
Tomcat POS Service longer offline
Small (POS/Back office) periods
Larger
12

Good online infrastructure, small offline periods

 Redundancy of Data, Transactions, Messages, EJ, POSLog, etc.

Central
Services

Database
Server
Central
EJ

Oracle, MS SQL On prem: SAP Netweaver, Tomcat Cloud (k8s) Central EJ

Central
Store
Very Lean Store Lean Store Thick store

Tomcat Server

Store Server Store DB

ThinPOS FullPOS ThinPOS FullPOS

ThinPOS FullPOS
Small Medium - Large

13
 Flexible Cloud Choices
Baremetal / VM Hosts

Replica Kubernetes Cluster

ERP System 1
App Digital Auth Config Stored ERP system 2
ECON
Gateway Signage Service Service Value Backend services

Customer Mobile GK Menu Active

SDC MWB
Portal Editor MQ
Selfscanning APP

Launch POS POS

CIS SM
pad Service Server

All services POD

Central
Database
Loadbalance
Public r

Network CLOUD
STORE
HTTPS (REST)
HTTPS (REST)

Backoffice Mobile POS Device Service Apache Tomcat POS Scale SCO Self scan
Client
Web Browser UI5 App Tomcat Tomcat Java Runtime Java Runtime Java Runtime UI5 App
14
 Hybrid Deployment – Components
OmniPOS
Central Central
Database

Central
EJ
Database
Universal Cluster Store Hybrid POS Transaction Store Label Print Promo Mobile Stock POS Server
Info Central EJ
Connector Infrastructure Device Service Pool Manager Service Designer Workbench Info (Back Office)
Server Reporting
(UCON) Service Control Service Service Service Service Service Service
Central Returns
Active MQ Chargebacks

Store • Master Data (Store only: Item, Tax, Promos, etc.)

Tomcat • Hybrid InfoServer
• Configuration Data (Parameters, Screens, Flows)
• Transaction+ Payments Service
• Transaction Pool for Returns (Local Transactions)
• Device Service (Payments)
• POS Service (REST APIs)
• Active MQ
• POS App*
• Info Client • Scale App
• Config Data* • MPOS App • Info Client
• Master Data • T+ Payments • Self Scan App • Config Data • InventoryApp • LPP App • Browser
• T+ Payments* (Optional) GK &/or Retailer • Master Data • Master Data • Master Data

Full POS SCO / Kiosk MPOS Payments Self-Scan Scale Mobile Labels Back Office Client & 3rd Party
MPOS tablet Full or Thin* Thin Thin Inventory Signs apps
ESLs
15
 Hybrid Deployment – Replication
OmniPOS
Central Central
Database

Central
EJ
Database
Universal Cluster Store Hybrid POS Transaction Store Label Print Promo Mobile Stock POS Server
Info Central EJ
Connector Infrastructure Device Service Pool Manager Service Designer Workbench Info (Back Office)
Server Reporting
(UCON) Service Control Service Service Service Service Service
Central Returns
Active MQ Chargebacks

• Master Data – Store specific REDUNDANCY NOTES:

Store • Config Data – Store specific Tomcat • Touchpoints below in RED can operate offline on each device
• Transactions – Store specific • Touchpoints below in RED also have redundancy to the Store Hub and the Central services and data
• POS service above
• Payments service • Touchpoints below in Blue have redundancy to the Store Hub and Central services and data above,
except the Back Office and some Client / 3rd party applications (device dependent)
• The Back Office connects directly to the Central POS Server and data. Important to note that basic
financial functions such as Pickup/Loan, Paid In/Out, Log in/out can be done offline on the POS,
enabling critical sales and business functions.

Full POS SCO / Kiosk MPOS Payments Self-Scan Scale Mobile Labels Back Office Client & 3rd Party
MPOS tablet Full or Thin Thin Offline capable with Thin Signs apps
Inventory
Offline capable Offline capable SAF, connected to ESLs
in Full mode POS
16
 The GK Retail Suite – Components and Communication - POS
 POS Transaction POS Transaction →
 Master Data  Master Data
→ Promotion → Promotion POS Transaction →
Master Data Master Data  Master Data
→ Promotion POS Transaction → Customer SI
Master Data  Master Data
POS Server Cluster Enterprise ERP, CRM,
Infrastructure Connector OMS,...
Service

POS Transaction →  Promotion

POS Transaction → Master Data
Promotion Master
Basket Price Data→  POS Transaction
Web-Shop Calculation →  Master Data Promotion
POS Service Store
POS Transaction   Promotion Master Data Designer
Device
Master Data 
Backend Promotion Master Data
Control

Centralized Store Decentralized Store

POS Server Cluster

 Master Data Infrastructure
 Promotion Master Data Service  POS Transaction →
 Scale & RVM Transaction  Promotion
POS Transaction → Master Data

 POS Transaction →
 Promotion
Master Data

Store
Backoffice POS, StoreHub POS,  Master Data Device
Launchpad SCO, SCALE SCO, SCALE  Promotion Master Data Control
 Scale & RVM Transaction
17
POS Transaction →
 Omni-Channel POS | Component & Communication

POS Transaction → POS Transaction → POS Transaction →

 Master Data  Master Data

POS Server  Master Data

CIS, Enterprise
→ POS Transaction
Connector 3rd Party 3rd Party
POS Transaction →

Transaction  Customer
Web-Shop Pool Master Data Picking
 Customer
Repository POS Tx.  Picking  Gift Basket
Master Data → Master Data   Gift Basket
Basket Price
→ Master Data
Calculation → Pricing
Service

Store Device Mobile

Control (Service) Workbench Enterprise
 Master Data POS Transaction 
Master Data 
Store
 Scale & RVM Transaction
 Customer Picking
 Gift Basket
POS Transaction → Device
 Function Call Adapter
Store Hub Scale Transaction 
Scale Master Data 

Backoffice Open Scale

18 POS
Client
Development and
Extensions
Open And Standards-based
Software Development & Deployment / CI / CD

push run

DevOps
Ops AKS Load WAF* Touchpoints
repo Balancer

ACR
*optional
trigger
Customer
User
Helm Docker
Charts Images
▪ CI, short for Continuous Integration, is a software
development practice in which all developers merge
Code
change
code changes in a central repository
multiple times a day.

Developer ▪ CD stands for Continuous Delivery, which on top of

Continuous Integration adds the practice of
Code build & test artifacts automating the entire software release process.
repo
Omnibasket.com - Software Extension Tools

Parameters Thousands of parameters to modify system behavior, via GK Storemanager.

Wysiwyg menu editor enables UI changes. HTML and CSS can also be used to modify the POS
UI Customization UI. Headless enabled architecture.

Process Model Process description language enables workflows to be modified without coding.

App Integration HTML/Javascript Apps can be embedded into the POS UI, reading and writing to the
current transaction via API. Postman available on Omnibasket.com for prototyping.

Comprehensive SDK and API library with Java coding enables upwards-compatible
SDK / APIs extensions. The core code of GK OmniPOS is not touched. Postman is available on
Omnibasket.com for prototyping.

Business agility without impacting upgradability

400+ REST APIs
OmniBasket.com: Innovation Platform – Open to GK Customers and Partners
Security
Security Overview

GDPR and PCI certifications, GK incorporates security GK's IT Compliance group

GK adheres to industry practices into the SDLC lives and breathes security
standards for application and CI/CD process. Every and compliance
security. Examples include check-in requires a code enforcement. They actively
requiring TLS 1.2 for data in review before merging watch for threats and
flight, strong encryption for into the build, every intrusions. This group is
data at rest, role-based build undergoes a SAST actively leading a project
access controls for all analysis, every container to achieve ISO 270001
functions, strong password is scanned before compliance.
requirements, etc.. deployment, etc..
Privacy is a Priority – Data access and Security

Data In Flight • All communications secured via TLS 1.2+

Data at Rest • Vendor database encryption

Access Control • Employees must have access rights to view and / or modify customer
data

Audit Logging • Log access and modification of customer data

• Scheduled purge of data that is not accessed

Purge Routines
• Includes transaction data
Security Assessments
The Retail Innovators