> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Extensions Overview

Extensions are the integrations that connect Omneo to the other platforms in your retail tech stack. They ensure customer data, transactions, and incentive states are synchronised in real time across every system that serves your customers and staff.

Omneo is built on the principle that it should be the source of truth for customer profiles and incentives, and that every other platform should benefit from that data without needing to build their own CDP.

## Extension categories

<CardGroup cols={2}>
  <Card title="eCommerce" href="/concepts/extensions/ecommerce" icon="shopping-cart">
    Shopify, SFCC, Magento, BigCommerce, commercetools, Commerce Layer
  </Card>

  <Card title="Communications" href="/concepts/extensions/comms" icon="envelope">
    Klaviyo, Emarsys, SFMC, Campaign Monitor, SendGrid, and more
  </Card>

  <Card title="ERP & POS" href="/concepts/extensions/erp-pos" icon="cash-register">
    In-store point-of-sale and enterprise resource planning integrations
  </Card>

  <Card title="Customer Service" href="/concepts/extensions/customer-service" icon="headset">
    Zendesk, Gorgias
  </Card>

  <Card title="Loyalty Partners" href="/concepts/extensions/loyalty-partners" icon="plane">
    Qantas Frequent Flyer, Corporate Invites
  </Card>

  <Card title="BI & CDP" href="/concepts/extensions/bi-cdp" icon="chart-bar">
    Tableau, Domo, Qlik, data warehouse connections
  </Card>
</CardGroup>

## How extensions work

Most extensions operate via a combination of:

1. **API Token**: a bearer token for the integration to authenticate with the Omneo API
2. **Machine User**: a dedicated Omneo user account named for the integration system
3. **Webhooks**: Omneo pushes events to the external system when data changes
4. **Targets**: formatted payloads sent to comms platforms for notification triggers
5. **SDK/Proxy**: front-end authentication and data access for customer-facing surfaces

<Note>Content needed: extension configuration architecture diagram and general setup checklist.</Note>