Open API Architecture

Platform and Open API Architecture

Enactor Central Components:

• Retail Microservices (Estate Manager) - User Interface, Transaction Processing and Archive, Configuration and Master Data, Messaging
• Enactor Commerce Microservices - Basket, Promotions, Inventory, Orders, Customer, Gift Card

Enactor Store Components (POS/MPOS/SCO):

• Master Data and Configuration flows down from central
• Transactions, Monitoring data, and System Events flow up

Retailer's Unified Commerce Composable APIs:

• Basket | Loyalty | Inventory | OMS | CRM | Gift Card | Payments | Vouchers

APIs connect to Retailer Digital Channels (web, mobile, social, IoT). Available out of the box, with retailer project extensions.

API-First Architecture within a Retailer

Area	Systems
Master Data Providers	ERP, Merchandise, PIM, HR - feed master data into Enactor
API Providers	CRM, Voucher, Loyalty, Product/Basket/Order - connected via API request/response
Enactor Central Components	Retail Microservices (Estate Manager) + Commerce Microservices - process and distribute data
Enactor Store Components	POS/MPOS/SCO - connected via master data down, transactions up
Transaction Data Consumers	Finance, BI, Inventory or OMS, Audit/Loss Prevention
Retailer Digital Channels	Web, mobile, social, IoT - connected via APIs
Web Front-End	Search and Select, Interactive Sales Tools - via Enactor JavaScript API (Data Exchange and HTML Web Pages)

---

Further Reading

Document	Description
UC API - Introduction	Introduction to the Unified Commerce API
UC API - Functions	Available UC API functions
UC API - Extension Points	UC API extension points for customisation