Account Hub
Customer-account shell and navigation designed to unify enabled merchant modules.
LOVIQO — Shopify Customer Lifecycle Platform
Case study / 02
Owned software venture · Published on ShopifyOne customer lifecycle.One connected system.
LOVIQO is a modular customer lifecycle platform for Shopify merchants, built from the BABALU pilot to replace disconnected post-purchase tools with one coherent customer-account experience and one merchant-side operating model.
CategoryCommerce software
ModelOwned / operated
PlatformShopify
StatusAvailable on Shopify App Store
Product footprint
Proof through product scope and implemented architecture.
7Capability domains
Core Platform, Experience, Engagement, Commerce, Service, Intelligence and Automation.
5Primary account surfaces
Account Hub, Wishlist, Rewards, Returns and Support in the current customer-account build.
8Lifecycle moments
Save, Buy, Own, Gift, Earn, Reorder, Return / Claim and Support.
1Reference tenant
BABALU remains the pilot and validation environment, not the public product identity.
Lifecycle thesis
From save to support without stitching together separate customer journeys.
The product thesis is simple: customer retention, ownership, service and post-purchase activity should live in one connected system. LOVIQO is designed around the full lifecycle rather than around isolated app features.
01 / DiscoverSave
02 / ConvertBuy
03 / Post-purchaseOwn
04 / ShareGift
05 / RetainEarn
06 / RepeatReorder
07 / ResolveReturn / Claim
08 / ServiceSupport
The product context
Customer experience becomes fragmented when every lifecycle moment is a separate tool.
The BABALU pilot exposed a recurring ecommerce problem: wishlist, loyalty, returns, support, ownership, reorder and customer data can become separate systems with separate logic. LOVIQO turns that operating friction into a product thesis — one multi-tenant platform, one entitlement model and one customer-account experience.
Capability architecture
Seven domains. One product system.
01
Core Platform
Multi-tenant merchant lifecycle, Customer Account Hub shell, configuration, plans, entitlements, feature gates, audit foundations, privacy lifecycle and production persistence.
02
Experience & Branding
Merchant-scoped Visual Studio controls, premium presets, typography, density, corner styles, logo, accent palette, module order and safe semantic presentation tokens.
03
Engagement
Persistent Wishlist, sharing, stock and price alerts, Rewards and Smart Reorder designed to support repeat engagement rather than isolated campaigns.
04
Commerce
Gift Hub, contributions and Product Vault connect gifting, ownership, warranty/documentation and product-specific post-purchase experiences.
05
Service
Returns and Support use order and ownership context so customer-service workflows remain connected to the commerce record.
06
Intelligence
Unified Customer Timeline and cross-module Analytics are designed to distinguish observed customer activity from unsupported attribution claims.
07
Automation
Persistent tenant-scoped trigger, condition and action workflows connect product, lifecycle and service events with auditable execution.
Implemented foundation
More than a concept deck.
Wishlist & Alerts
Persistent, variant-aware wishlist with sharing plus stock and price alert foundations.
Rewards
Pending and available points, expiry, reversals and idempotent redemption foundations.
Returns & Support
Order-aware returns eligibility and support-ticket workflows inside the customer lifecycle.
Product Vault
Purchased-product registry, warranty/documentation and product-specific care and support context.
Smart Reorder
Purchase-cadence logic, confidence scoring and predicted reorder-window foundations.
Unified Timeline
A normalized chronology for meaningful purchase, rewards, wishlist, return, support and ownership events.
Cross-module Analytics
Observed module adoption and activity with explicit separation between facts and attribution.
Visual Studio
Merchant-controlled presentation settings mapped safely into Shopify Customer Account surfaces.
Commercial architecture
Designed to move from one pilot to many merchants.
01Multi-tenant by design
Merchant-owned data and configuration are scoped by canonical Shopify tenant identity rather than BABALU-specific conditions.
02Plan & entitlement engine
Commercial feature availability is controlled server-side through merchant status, plan entitlements and staged enforcement.
03Shopify-native surfaces
Customer-facing modules are designed for Shopify Customer Accounts and supported platform primitives rather than unrestricted injected UI.
04Privacy lifecycle
Data export, deletion and mandatory Shopify privacy-request handling are treated as product architecture, not post-launch paperwork.
05Production persistence
Commercial persistence is designed for PostgreSQL with release-readiness, schema and health verification built into the deployment model.
Current state
Live on Shopify App StoreFrom operating insight to a published Shopify app.
LOVIQO Customer Hub launched on 20 October 2026 and is available to install through the Shopify App Store. It brings wishlists, loyalty rewards, gifting, returns and customer support together, with feature access depending on the merchant’s subscription plan. The BABALU pilot informed the original product direction.
ProductCustomer Hub published
PlatformListed in the Shopify App Store
CommercialFree and paid plans available
Launch20 October 2026
What this demonstrates
BRANTSI can turn operating friction into a software product.
01 / Product
A real merchant problem is translated into a coherent customer-lifecycle product thesis.
02 / Engineering
The concept is carried into multi-tenant architecture, customer modules, persistence, billing and release controls.
03 / Validation
The BABALU operating environment informed the original product concept and its early validation.
LOVIQO Customer Hub was published on the Shopify App Store on 20 October 2026. Features vary by subscription plan. This case study documents product design and development; it does not claim merchant adoption, revenue growth or independently measured customer outcomes.
Connected capabilities