Configuration
Configuration overview
After you connect your storefront to a Commerce backend in Create a storefront, use these topics to adjust that connection, secure cross-origin requests, or turn on optional features such as multistore and gated content.
| Topic | What it covers |
|---|---|
| Storefront configuration | Connect your storefront to your Commerce backend using the public config or a config.json file. |
| CDN configuration | Set up the CDN that delivers your storefront’s content. |
| CORS Setup | Configure CORS headers so your storefront’s domain can call your Commerce GraphQL endpoint. |
| CORS Troubleshooting | Diagnose and resolve CORS errors between your storefront and your Commerce backend. |
| AEM Assets integration | Display product images managed in AEM Assets instead of Commerce-hosted images. |
| Enrichment configuration | Configure query.yaml so content authors can add enrichment content to product pages. |
| Commerce Picker configuration | Set the root category ID so content authors can browse the catalog with the Commerce Picker extension. |
| Gated content | Restrict access to non-Commerce assets, such as images or pages, that customer segments can’t control. |
| Compatibility Package | Add the package that bridges older Adobe Commerce versions and B2B stores to the storefront. |
| Price Book ID setup | Enable Adobe Commerce Optimizer Price Book ID support for personalized pricing. |
| Multistore setup | Run multiple storefronts for different languages, regions, or brands from one codebase. |
| Data export validation | Confirm that data exports from your Commerce backend are reaching your storefront correctly. |
| Luma Bridge | Migrate a theme-based Adobe Commerce storefront to Edge Delivery Services in phases. |