Platform / Theming
Liquid storefront themes with real developer workflow.
PyroApex gives each tenant a customizable Liquid storefront backed by reusable sections, local pull and push commands, product and location sync, lead capture, wholesale content, and seasonal merchandising.
Operator view
Theming
Theme files live as tenant data, so a merchant can fork the storefront experience without re-platforming.
Developers can pull and push themes locally through the PyroApex CLI instead of editing inside a hosted-only builder.
Reusable Liquid sections connect hero, product, location, lead-capture, and wholesale blocks to live platform data.
How it works
A storefront design system that keeps commerce logic intact.
Fireworks retailers need storefronts that change quickly: pre-season lead capture, tent opening announcements, wholesale program explanations, featured assortments, store finder content, and product education all move with the season. PyroApex uses Liquid themes so tenants can customize the storefront while cart, checkout, inventory, accounts, and compliance stay consistent underneath.
The theme system ships with eight reusable sections for common storefront work. Operators and developers can compose hero areas, featured collections, product blocks, location content, lead-capture prompts, and wholesale messaging without rebuilding the commerce engine. Because themes are tenant data, a merchant can fork and iterate without migrating to a generic site builder.
PyroApex also treats theme development like software work. The CLI can pull and push theme files, sync product and location data for local development, and let teams use their normal editor and review process. That keeps the storefront extensible without trapping operators in a closed template editor.
Tenant theme data
Themes are stored per tenant, allowing each merchant to fork and customize storefront presentation without leaving the platform.
Liquid sections
Eight reusable sections cover hero, product, location, lead-capture, wholesale, and merchandising patterns.
CLI pull and push
Developers can pull a theme locally, edit in their normal tools, and push updates back through the PyroApex CLI workflow.
Data sync
Product and location sync gives local theme work realistic storefront data before changes are promoted.
Commerce-safe customization
Brand styling can change while checkout, cart, eligibility, and fulfillment rules stay platform-managed.
Screenshots
The work surfaces operators use.
Representative product views show storefront, admin, and operator surfaces for this capability.
Theme CLI workflow
Pull, edit, sync data, and push tenant theme files through local tooling.
Theme pull and push commands
Local file tree for sections
Product and location sync
Reviewable changes before publish
Reusable Liquid sections
Reusable section blocks help teams compose storefront pages without touching checkout logic.
Hero and featured products
Lead-capture modal section
Wholesale messaging block
Location and store finder content
Tenant storefront styling
Per-tenant theme data controls the customer-facing brand while preserving shared commerce behavior.
Brand colors and assets
Homepage section order
Seasonal campaign content
Shared cart and checkout flow
Product and location sync
Local theme work can use realistic product and store data before operators publish changes.
Product catalog snapshot
Retail location records
Collection and SKU context
Local preview confidence
Operator comparison
PyroApex vs. generic platforms.
Generic commerce tools start from other industries. PyroApex starts from fireworks operations.
Customer quote
"[Customer quote - TBD]"
Testimonial slot reserved for an approved theming quote.
Map this to your operation.
Bring your workflow questions. We will walk through the fit and gaps plainly.