CapraFlo growth OS
The problem
DTC brands assemble Appstle or PayWhirl for subscriptions, Smile for points, Refersion for creators, then a separate bundle or discount app. Each one owns a slice of Admin, a slice of the theme, and a monthly line item. Checkout stays Shopify — the stack around it does not.
How it works
CapraFlo is one embedded Partner app. Site modes pick the money path. CapraFlo AI stages selling plans and automatic discounts. You agree. GraphQL syncs them. Theme blocks and the /apps/capraflow proxy read the active mode. Bundles, Subscribe & Save, Loyalty, and Affiliate stay in one hub.
Problem. Merchants know they want “more AOV” or “more subscribers” but configure four apps independently. The storefront never agrees with itself.
How it works. CapraFlo AI recommends a mode from catalog posture. You preview selling plans and discount tiers. Yes, I agree writes local records, then syncs Shopify objects. Theme blocks follow the mode — checkout does not leave Shopify.
Admin — pick a mode, preview, agree.
Storefront — theme blocks read the active mode.
Site mode: DTC Growth · selling plan + volume discount on this PDP
Problem. Bundle apps often clone products or hijack cart. Merchants pay for a widget that fights theme quantity rules.
How it works. CapraFlo stores bundle rules locally from the Site mode template, then syncs automatic basic discounts. The PDP shows volume and mix tiers. Shopify applies the discount in native checkout.
Admin — bundle rules and sync state.
Storefront — shopper picks a tier on the PDP.
Problem. Subscription apps often stand up a parallel purchase flow. Shoppers bounce when the checkout they trust disappears.
How it works. CapraFlo creates selling plan groups and syncs them through Admin GraphQL. The PDP toggle is one-time vs subscribe. Checkout remains Shopify checkout with a selling plan on the line item.
Admin — selling plan groups.
Storefront — selling plan on the PDP, native checkout next.
Problem. Loyalty bolt-ons add another account widget, another CSS fight, and another bill — often before the brand has a paid-order signal worth rewarding.
How it works. CapraFlo listens to orders/paid. Points accrue from the template (for example 1 point per dollar). VIP thresholds unlock after paid, not at browse. Cart and account blocks show the balance.
Admin — program and webhook health.
Storefront — points on cart after a paid history.
Capra Loyalty · 214 pts on this account · 286 to Silver
Problem. Refersion-class tools sit outside the rest of the stack. Attribution and discount codes drift from the subscription or loyalty program.
How it works. Partners live in Capra Admin. Default commission and codes come from the Site mode template. Cart/checkout can collect a creator code. CapraFlo records the referral against the order — still native checkout.
Admin — partners and default commission.
Storefront — referral field before native checkout.