Features
This section documents each capability built into the KFC Atlas platform. Every feature has its own dedicated page covering what it does, how it behaves across platforms, and any market-specific considerations.
What Counts as a Feature?
A feature in Atlas is a distinct, user-facing or operator-facing capability that:
- Delivers a specific piece of product or operational value
- Has defined behaviour across iOS, Android, and Web
- Can be enabled, configured, or extended per market
Current Features
| Feature | Description | Platforms |
|---|---|---|
| KFC Deeplink | Universal Link | Open specific KFC content directly in the app via any KFC URL | iOS, Android, Web |
| Branch Deeplink | Attribution-aware deep linking and deferred routing via Branch.io | iOS, Android |
| MarTech | Event tracking, customer data, and marketing automation integrations | iOS, Android, Web |
| Social Sign In | Google, Facebook, and Apple login across web and native app | iOS, Android, Web |
| Menu Item Reservation | Allow customers to pre-order and reserve specific menu items in advance | iOS, Android, Web |
Features are enabled per market via configuration — not separate code deployments. See Market Configurations for details.
Feature Dependencies
Each feature in Atlas is built to be reusable across markets. That said, some features may carry dependencies on third-party systems — such as a market's Point of Sale (POS) or Delivery Management System (DMS) — and will require an integration assessment before they can go live.
Menu Item Reservation is an example: any market-specific reservation flow depends on stock and timeslot APIs from the relevant POS or inventory system. Markets without equivalent API support from their POS would need to complete that integration before the feature could be enabled.