Guide · Architecture
Understand the Shopify storefront system through clear ownership layers.
See how Shopify commerce, Wanevo configuration, themes, web and native renderers, integrations, and server delivery work together without turning the guide into an implementation manual.
01
Shopify commerce
Catalogue, customers, carts, orders, and checkout.
02
Wanevo experience model
Schemas, pages, themes, storefront context, and integrations.
03
Web and native renderers
Channel-appropriate UI from shared contracts.
04
Provider boundaries
Search, reviews, subscriptions, support, analytics, and push.
The practical guide
Understand the decisions before choosing the implementation.
Commerce and experience are separate responsibilities
Shopify remains the transactional system; Wanevo coordinates how customers experience it.
- Storefront API and customer-account access
- Cart and checkout handoff
- Privileged Admin writes stay in the embedded app
- Public renderers never receive Admin credentials
Configuration replaces brand forks
Variation is represented through typed context and predictable fallback.
- Theme defaults and sparse storefront overrides
- Page templates, sections, blocks, and presets
- Storefront domains, markets, locales, and service areas
- Feature activation and channel projection
Integrations live where they belong
A provider is not “installed everywhere”; it has a defined boundary.
- Browser analytics and tag management
- Native analytics and push
- Server-owned outcomes and provider APIs
- Shopify, search, reviews, subscriptions, and helpdesk ownership
01
No public client receives Shopify Admin credentials.
02
Every provider has a named browser, native, Shopify, or server boundary.
03
Brand and storefront variation is configuration, not renderer branches.
04
Web and native share contracts while preserving channel-specific UI.