Making Your Page Live: Layout Mappings & Conditions Print

Layout Mappings determine which Layout is used for a given storefront presentation page or CMS page. Mappings connect a Layout to a Target (page location, CMS page, or route) and may include Conditions (rules like date ranges or audience). The Layout Resolver evaluates mappings in priority order and selects the first match.

Key Terms

• Target — the location where a Layout can apply (home, category, Product Menu, CMS page, or custom URL)
• Condition — additional rules that must be satisfied (e.g., date range, segment, device, custom flag)
• Priority — ordering of mappings; higher priority mappings are evaluated first
• Layout Resolver — the mechanism that checks mappings in order and picks the first mapping whose Target and Conditions match

ERP Awareness

• 365 Cannabis ERP remains the source of truth for products and pricing; mappings do not change product data
• Mappings control presentation (which Layout shows), not ERP synchronisation behaviour

Target Types

• Storefront Home — /
• Category Pages — /category/<slug> (e.g., /category/edibles)
• Product Menu Pages — /menu/<slug> (e.g., /menu/summer-specials)
• CMS Pages (optional content) — content-driven routes such as /about, /contact, /education/<topic>
• Custom URL-page addresses — any valid storefront path (e.g., /campaign/420, /brand/<name>)

When to Use Layout Mappings

• Assign a specific Layout to the home page
• Attach themed Layouts to category or Product Menu pages
• Apply layouts to CMS pages for enriched content presentation
• Run campaign-specific Layouts on custom URL-page addresses
• Show different presentation for certain customer segments

Creating a Layout Mapping

1. Go to Page Management → Layout Mappings
2. Click Create Mapping
3. Select the Layout to apply
4. Choose the Target:
   • Storefront route (home, category, Product Menu)
   • CMS page (pick from CMS list or enter its route)
   • Custom URL-page address (enter path)
5. (Optional) Add Conditions (e.g., start/end date, audience segment)
6. Set Priority (evaluate this mapping before broader defaults)
7. Save

Using Conditions

• Date Range — schedule campaign layouts
• Segment — tailor for specific audiences (e.g., wholesale)
• Device — optionally tailor for mobile/desktop if supported
• Custom Flags — implementation-specific toggles

Priority & Evaluation

• The Layout Resolver evaluates mappings in priority order
• The first matching Target + Conditions combination is used
• Place narrow or time-sensitive mappings above broad defaults

Examples

• Home default: Target / → Layout Home – Standard
• Home campaign: Target / + Condition Apr 15–Apr 22 → Layout Home – 420 Promo (higher priority)
• Category theme: Target /category/edibles → Layout Edibles – Product Menu
• CMS content: Target /education/terpenes (CMS page) → Layout Education – Article
• Custom landing: Target /campaign/summer + Condition segment=retail → Layout Summer Retail

Previewing and Testing

1. Use Preview to verify which Layout resolves for the Target
2. Temporarily adjust priority to test fallback behaviour
3. Validate date-based Conditions with test windows
4. Confirm CMS routes and custom URL paths exactly match the published addresses

Troubleshooting

• Wrong Layout appears: A higher-priority mapping is matching first — move your intended mapping higher
• No Layout appears: Target path or CMS route mismatch — confirm the exact URL
• Campaign not showing: Check date/time and Conditions; verify time zone if applicable
• Segmented layout missing: Confirm the signed-in account qualifies and that mapping scope includes authenticated views

MEO Considerations

• Mappings are typically per SellStack instance — define them separately for each entity
• CMS pages and custom URLs may differ by instance; verify each route before mapping

Best Practices

• Create a default mapping for each key Target as a fallback
• Use Shared Layouts for recurring content; use mappings for where/when content appears
• For campaigns, prepare Layouts in advance and activate via date Conditions
• Document mapping priorities so administrators avoid accidental overrides

Quick Setup Checklist

1. Create/confirm your Layout(s)
2. Add mapping(s) for storefront, CMS, or custom URL targets
3. Apply Conditions for timing or audience as needed
4. Order mappings by priority (specific above general)
5. Preview and test before going live