Because: From Custom Setup to Loop

TL;DR

• Evaluated multiple subscription platforms over a 2-month assessment period
• Migrated from a custom Recurly setup to Loop over a 4-week timeline
• Built a customer portal tailored to Because's customer demographic
• Configured role-based user permissions for the support team
• Integrated a loyalty program through Loop's Bubblehouse integration
• Key Loop features used: Custom Customer Portal, User Permissions, Loyalty Integration, Prepaid Subscriptions

The Starting Point

Because is a wellness brand serving older consumers. The team had built a custom subscription setup on Recurly and was looking for a platform with native Shopify checkout to simplify their operations, support faster product development, and reduce engineering overhead.

The team wanted to evolve the subscription program to better fit their customer base while reducing the development resources required to maintain it.\

The Team's Decision Process

The Because team ran a two-month evaluation across subscription platforms and selected Loop. Their team had this to say about the decision and the relationship:

The Migration

Migration from the custom Recurly setup to Loop was completed over a four-week timeline.

What Because Built on Loop

1. Customer portal tailored to Because's customer base

Because's customer demographic skews older, and the team wanted a customer portal that was simple, clear, and easy for their subscribers to navigate.

Using Loop's APIs, the Because team:

• Built a customer portal tailored to their subscriber base
• Refined widgets, product presentations, and navigation for clarity
• Designed straightforward interfaces to reduce support load
• Maintained the brand's visual experience across the subscription journey

2. Role-based permissions for the support team

A meaningful share of Because's subscription orders are placed by phone, so the team needed subscription management tooling that worked alongside their customer support workflow.

Loop's user permissions system allowed Because to:

• Configure role-based access for support team members
• Set granular permission levels by agent responsibility
• Allow certain agents to issue discounts while restricting others
• Maintain access controls across the support organization
• Track activity across the customer service process

3. Loyalty program integration via Bubblehouse

Because uses Loop's Bubblehouse integration to bring loyalty and subscriptions into a single experience for subscribers.
The setup lets subscribers:

• View loyalty points inside the customer portal
• Redeem points for rewards without leaving the portal
• See custom benefit messaging tied to their subscription status
• Move between subscription and loyalty features within one branded flow