🧩 Byte Capabilities
Audience: Market Enablement, Launch Teams, Product Managers, Cross-functional Stakeholders Purpose: Single source of truth for what the Atlas / Byte Helium platform does, how it's structured, and what's needed to go live.
This section lives outside the operational guides by design. The Front-end Guide and Admin Portal Guide tell you how to operate the platform — Byte Capabilities tells you what the platform is and what it can do.
In Atlas Wiki, Byte Capabilities is intentionally scoped to the Atlas Commerce + Portal picture. In practice, that means:
- Atlas is KFC's global front-end
- Byte Commerce + Byte Portal are the commerce and configuration layer behind Atlas
- Byte Helium is Yum!'s enterprise design system and front-end foundation that Atlas is built on and branded through
- Byte Connect is the middle layer used when a market POS is not Byte POS
The Admin Portal Guide still owns the step-by-step operating instructions.
How to Use This Section
| If you want to… | Go to… |
|---|---|
| Understand the full platform in 5 minutes | Mental Model |
| See what each core part (Atlas on Byte Helium / Byte Commerce / Byte Portal / Byte Connect) does | Platform Layers |
| Find a specific feature | Domains — pick your domain |
| Know what can and can't be done | Capability Boundaries |
| Prepare for a market rollout | Reality Check |
| Get a go/no-go launch checklist | Market Launch Checklist |
| Look up a technical term | Glossary |
| Check performance SLOs | Performance SLOs |
The Platform in One Paragraph
KFC Atlas is KFC's global front-end for digital ordering. Atlas itself is built on Byte Helium, Yum!'s enterprise design system and front-end foundation, skinned to reflect the KFC brand. Behind that front-end sits the Byte Commerce + Byte Portal operating picture: Commerce processes orders, pricing, payments, and POS injection, while Byte Portal manages the market and operational configuration that makes Atlas work in production.
When a market is not on Byte POS, Byte Connect becomes the middle layer between Byte Commerce and the market POS environment. Understanding how Atlas, Helium, Commerce, Portal, and Connect fit together is the foundation for launch and operational decision-making.
The 12 Capability Domains
The platform is organised into 12 functional domains. Each domain has its own page with a feature table, how it works, dependencies, limitations, and links to related wiki guides.
| Domain | What It Covers |
|---|---|
| Identity & Sign-In | Account creation, OTP sign-in, Google/Apple OAuth, profile, privacy |
| Localisation & Order Mode | Market detection, delivery vs. collection mode, store locator |
| Menu Browse & PDP | Product listing, item detail, modifiers, nutrition/allergens |
| Cart | Add/update/remove items, apply promo codes, attach loyalty rewards |
| Checkout | Guest and registered checkout, delivery and collection variants |
| Payments & Tenders | Card, saved card, voucher, split tender, gift card |
| Promotions & Loyalty | Offers feed, rewards, challenges, loyalty onboarding, comms prefs |
| Donations & Tips | Add-Hope donations, delivery driver tips |
| Order Tracking & History | Real-time tracking, order history, receipts, reorder, favourites |
| Content & Legal | CMS pages, legal docs, cookie consent |
| Engagement & Messaging | In-app inbox, push and email notification preferences |
| Portal — Admin & Configuration | RBAC, stores, menus, promos, tax, payments, reporting, audit |
What This Section Doesn't Cover
This section is intentionally conceptual. For step-by-step guides on doing things in the platform, go to the relevant operational section:
- How to operate Byte Portal day to day → Admin Portal Guide
- How to set up and manage stores → Admin Portal Guide: Stores
- How to create and configure promotions → Admin Portal Guide: Promotions
- How to build and run promotions campaigns → Playbooks
- How customers experience the front-end → Front-end Guide