LWR versus Aura store component support
Key Takeaway
An LWR store supports only Lightning web components (LWCs), so every Aura component must be replaced to complete a move to LWR.
A B2B Commerce store runs on one of two platforms: the older Aura platform or the Lightning Web Runtime (LWR). The platform decides which kinds of components the store can use. The component rule for LWR stores drives most of the work of building for LWR or moving a store to LWR.
Which components each store supports
A B2B store builds its desktop and mobile UI with the Lightning Component framework. The framework has two programming models: the original Aura Components model and the Lightning Web Components (LWC) model.
A B2B store on Aura supports both Aura components and LWCs. A B2B store on LWR supports only LWCs, so an Aura component can't run in an LWR store.
Starting with Summer '23, all new B2B stores are built on LWR. Some existing stores still run on Aura. Salesforce recommends migrating those stores to an LWR template.
To keep an Aura component's function in an LWR store, you must replace the Aura component with an LWC. In that replacement, you can reuse the LWCs the Aura component contains and other LWCs built for an Aura store. Many LWCs built to run in an Aura store work on LWR with no changes or need only small edits. The Aura components are the main migration work.
Lena's Aura store has a custom Aura component called deliveryPanel, which contains an LWC called dateBadge. Lena is moving the store to LWR, so deliveryPanel must be replaced. She builds a new LWC that does the same job and places dateBadge inside it. In her case, dateBadge needs only a small edit.