🎨 Byte Helium Capabilities
Byte Helium is Yum!'s enterprise design system and front-end foundation. In Atlas, KFC's global front-end is built on Helium and skinned for the KFC brand, covering everything from sign-in and menu browsing through to checkout, payment, and post-order tracking.
In the Atlas context, Helium renders what the backend provides. It does not own pricing, promo eligibility, order state, or content — those belong to Byte Commerce, Promo Engine, and CMS respectively. Helium's job is to provide the front-end foundation that Atlas presents through the KFC brand and customer journey.
Byte Helium Capability Domains
| 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 charitable donations, delivery driver tips |
| Order Tracking & History | Real-time delivery tracking, order history, receipts, reorder, favourites |
| Content & Legal | CMS brand pages, legal documents, cookie consent |
| Engagement & Messaging | In-app inbox, push and email notification preferences |
Byte Helium renders but does not own: pricing (Commerce Backend), promo eligibility (Promo Engine), loyalty points (Loyalty service), payment capture (PSP), menu content (Byte Menu), legal content (Legal CMS), or store state (Byte Portal + POS). See Capability Boundaries for the full ownership map.
Technical Sources
📎 Technical Source: Byte Helium Capability Overview
- FRD References: FRD-HEL-001, FRD-HEL-011, FRD-HEL-048, FRD-HEL-072
- TRD Domains: Identity, Localisation, Menu, Cart, Checkout, Payments, Loyalty, Tracking, Content
- Key Interfaces / APIs: App shell, Context/Store selection, Menu, Cart, Checkout, Payment, Order Status
- Data Contracts: Session context, cart, checkout session, payment intent, order summary, order status
- Source Summary:
- Byte Helium is the customer-facing front-end foundation and orchestration surface for the KFC digital journey
- Backend systems remain the source of truth for pricing, eligibility, order state, and most configuration
- Domain-level technical details live in the linked capability pages below, each with its own source notes where needed