This update focuses on clarity, structure, and readiness across Elite Core. The work completed during this phase emphasizes how different parts of the platform connect, especially where frontend experiences meet operational reality.
From late December into early January, attention shifted toward tightening how users launch programs, manage visibility, and move work through Elite Core with less friction and fewer one-off decisions.
PromoStores: From Storefronts to Programs
PromoStores continued to evolve from a simple company store concept into a structured way to launch controlled programs. The focus during this phase was defining how a store behaves, not just how it looks.
Rather than treating every store as a permanent public website, PromoStores is being shaped to support temporary, purpose-driven experiences that align with how promotional programs actually run.
- Stores can be scoped to a specific audience, purpose, or timeframe
- Programs can be launched, paused, or closed without rebuilding pages
- Frontend behavior adapts based on the type of program being run
This allows teams to think in terms of programs and campaigns instead of static storefronts.
Guarded Access and Brand Control
A major area of refinement during this update was guarded access. Not every PromoStore is meant to be public, and not every product should be visible to every visitor.
PromoStores now support multiple layers of access control that allow teams to protect brands, pricing, and participation without introducing custom logic for each case.
- Brand guarding to ensure products appear only in approved contexts
- Email domain restrictions for internal or client-only programs
- Invite-based and voucher-driven access for controlled participation
These controls make it possible to run employee programs, client portals, and limited campaigns using the same underlying system.
Flexible Checkout and Engagement Models
Another focus during this phase was removing the assumption that every store interaction must end in immediate payment.
PromoStores are being designed to support different engagement models depending on the program, without confusing the end user.
- Checkout without payment for approval or review-based programs
- Quote or request flows instead of direct purchase
- Voucher-funded programs where users do not see pricing
This flexibility allows PromoStores to support internal rollouts, client approvals, and promotional initiatives that do not follow traditional ecommerce patterns.
Connection Back to Elite Core
While PromoStores focuses on the frontend experience, this update reinforced how tightly those experiences remain connected to Elite Core.
Actions taken in a store are designed to flow naturally into the rest of the system, without exposing internal complexity to the user.
- Store activity stays tied to the originating program
- Orders, requests, and submissions align with internal workflows
- Operational teams retain visibility without manual re-entry
This keeps PromoStores flexible on the surface while remaining grounded in a single operational source of truth.
Command Centre Direction
Alongside frontend refinement, the Command Centre continued to take shape as a way to coordinate work across Elite Core. Its role is to provide awareness and direction, not another place to manage details.
- High-level visibility into active work
- Clearer signals for follow-up and attention
- Reduced need to jump between modules for context
Smart Automation Support
During this phase, Elite Core continued laying the groundwork for smart automation that supports users quietly in the background.
The focus remains on helping work move forward faster while keeping people in control.
- Assistance for routine follow-ups and checks
- Support for scheduled and event-driven tasks
- Automation that reinforces existing workflows
What comes next
Update 0.0.9 is about intent. PromoStores is no longer treated as a side feature, but as a structured way to run programs on top of Elite Core.
By deepening control over access, behavior, and flow, this update makes it possible to launch more frontend experiences without increasing operational complexity.
