📋 Platform Glossary
Definitions for all terms used across the Byte Capabilities documentation. When in doubt about what a term means, start here.
| Term | Definition |
|---|---|
| Byte Helium | Yum!'s enterprise design system and front-end foundation. KFC Atlas is built on Helium and skinned to reflect the KFC brand |
| Byte Commerce | The commerce engine behind Atlas. It processes orders, pricing, payments, and POS injection; if a market is not on Byte POS, Byte Connect is required as the bridge to the market POS |
| Commerce Backend | The backend component of Byte Commerce — see Byte Commerce |
| Byte Portal | The admin interface paired with Byte Commerce for market and ops teams to configure and operate the platform |
| Byte Menu | The menu authoring tool — external to Atlas; Byte Portal assigns published menus |
| Byte Connect | The middle layer used when Atlas / Byte Commerce need to reach a non-Byte POS environment; it also supports aggregator order flows into Byte Commerce |
| PSP | Payment Service Provider — handles card tokenisation and capture |
| Vault | Secure storage for card tokens and PSP credentials |
| PLP | Product Listing Page — the menu browse view |
| PDP | Product Detail Page — single item view with options |
| OTP | One-Time PIN — used for passwordless sign-in |
| SSO | Single Sign-On — centralised authentication service |
| CMP | Consent Management Platform — manages cookie and marketing consent |
| CRM | Customer Relationship Management — manages customer profiles and comms prefs |
| KDS | Kitchen Display System — the screen in-store showing incoming orders |
| POS | Point of Sale — the in-store order management system; Atlas reaches Byte POS through Byte Commerce, and reaches non-Byte POS markets through Byte Commerce plus Byte Connect |
| DCI | Data Contracts & Interfaces — the versioned registry of all API/event schemas |
| RBAC | Role-Based Access Control — how Portal user permissions are managed |
| Scope Guard | Byte Portal security mechanism that blocks out-of-scope access at UI and API level |
| Add-Hope | KFC's global charitable donation programme integrated at checkout |
| Split Tender | Paying with two payment methods — e.g., voucher + card |
| Idempotency Key | A unique ID that prevents duplicate orders or payments if a request is retried |
| TRD | Technical Requirements Document |
| FRD | Functional Requirements Document |
| SLO | Service Level Objective — the performance target for a system |
| DLQ | Dead Letter Queue — where failed webhook events are held for review |
| 3DS | 3D Secure — card authentication protocol for fraud prevention |
| Byte | The programme name for the overall KFC e-commerce initiative |
| Atlas | KFC's global front-end for digital ordering, built on Byte Helium and powered by Byte Commerce + Byte Portal, with Byte Connect included wherever a market POS is not Byte POS |
| Context | The platform's record of a customer's market, language, order mode, and store |
| BCOM | Short form of Commerce Backend — see Commerce Backend |
| Patch | A menu override applied on top of a published menu version — used for price or availability changes at store or group level |
| Store Group | A logical grouping of stores in Byte Portal used for menu assignment, promotions scoping, and tax rule inheritance |
| Coverage Zone | A delivery geographic boundary configured in Byte Portal / Geo service that determines which addresses can receive delivery orders |
| Feature Flag | A runtime toggle in Byte Portal that enables or disables a feature for a specific market, channel, or customer segment without redeployment |
| Aggregator | A third-party delivery platform (e.g., Uber Eats, DoorDash) whose orders are ingested via Byte Connect into Byte Commerce |