---
title: 'Integration landscape'
description: 'How Guper connects to your POS, Ecommerce and downstream systems.'
---

# Integration landscape

Guper is built on the **MACH architecture** — Microservices, API-first, Cloud-native, and Headless — with the goal of driving customer revenue through Loyalty, Promotion and Analytics engines.

This page is an overview of how the platform connects to your systems and where each API fits in.

## POS & Ecommerce

POS and Ecommerce integrations communicate with the **Integration API**, primarily through the Checkout endpoints (e.g. [Reward by Order](/docs/{lang}/api-reference/loyalty/checkout/reward-by-order)), to send order data to the Guper Engine.

The **Guper Engine** is the core component that evaluates and applies promotion and reward rules in real time. When data arrives the engine determines which rules are eligible based on the configured conditions and returns the corresponding **effects** — cashback, points, discounts — to the integration layer for an instant, smooth application of the rewards during navigation and checkout.

![Integration landscape](https://content.pstmn.io/b9730790-1d7f-4482-8711-3ec2950705bd/SW50ZWdyYXRpb24gTGFuZHNjYXBlLmRyYXdpby5wbmc=)

## Data Transfer

The **Data Transfer** layer keeps your CRM, BI tools, data lakes or any downstream system in sync with the latest customer and order activity.

Two dedicated feeds publish updates in real time:

- **Customer Feed** — every time a customer is created, updated or tagged.
- **Order Feed** — every time an order is created, modified, cancelled or has rewards applied.

![Customer and order feeds](https://content.pstmn.io/ae8e9afb-9c24-4aac-bdc1-df8fd4fe599f/RmVlZC5wbmc=)

Updates may include:

- New customer or order registration
- Profile or status changes
- Items added or removed from an order
- Tags or audiences added or removed
- Rewards or promotions applied or revoked
- And more

This setup ensures a seamless data flow for enriched analytics, reporting and customer engagement strategies.

## Next steps

- Configure your access — see [Authentication](/docs/{lang}/guides/authentication).
- Learn how Guper maps your data with [Data Interfaces](/docs/{lang}/guides/interfaces).
