How do I set up a recurring payments platform for beauty subscriptions with skips, swaps, and bundle changes?

To set up a recurring payments platform for beauty subscriptions with skips, swaps, and bundle changes, you want a system that separates billing, subscription state, and fulfillment cleanly. The main challenge is handling changes without breaking invoicing, inventory, or customer expectations.

Here’s a practical blueprint.

---

1) Define the subscription model

For beauty subscriptions, customers usually need flexible recurring orders rather than a fixed SaaS-style plan.

Core entities

• Customer
• Payment method
• Subscription
• Subscription item(s): products in the box or bundle
• Billing schedule
• Order
• Shipment
• Adjustments: skips, swaps, upgrades/downgrades, one-time add-ons

Typical subscription types

• Fixed bundle: same products every cycle
• Curated box: products can vary each month
• Build-your-box: customer selects items from an eligible catalog
• Tiered bundles: different price points with different item counts or sizes

---

2) Choose your billing architecture

You generally have two options:

Option A: Subscription billing platform + custom orchestration

Use Stripe Billing, Recharge, Chargebee, Braintree, etc., and build your own logic around:

• skip rules
• swap rules
• bundle editing
• fulfillment integration

This is usually the best fit if your business has custom subscription behavior.

Option B: Full custom billing

You build everything, including:

• recurring charge engine
• invoice generation
• proration logic
• retry logic
• dunning workflows

This gives maximum control, but it is much more expensive and harder to maintain.

Recommendation

For a beauty brand, usually:

• Use a billing provider
• Build a subscription orchestration layer
• Connect to inventory and fulfillment systems

---

3) Design the subscription state machine

This is the heart of the system.

Each subscription cycle should move through states like:

1. Active
2. Pending renewal
3. Customer editable window
4. Locked for processing
5. Billed
6. Fulfilled
7. Skipped
8. Paused
9. Cancelled

Important rule

Treat changes as effective for a specific billing cycle, not just “now.”

For example:

• swap product in next cycle
• skip next shipment
• change bundle starting with cycle 5

This avoids race conditions and customer confusion.

---

4) Implement skips, swaps, and bundle changes

A. Skips

A skip means the customer opts out of the next billing/shipment cycle.

What to store

• subscription_id
• cycle_id
• skip_reason
• skip_requested_at
• skip_effective_for_cycle

Business rules

• Can skip only before cutoff time
• Skipped cycles should not bill
• Skipped cycles should not create fulfillment orders
• If prepaid, decide whether to:
  • extend the subscription term
  • preserve credit for later
  • push the next renewal date

B. Swaps

A swap means replacing one product with another eligible product.

You need:

• product catalog with swap eligibility
• compatibility rules
• price difference rules
• inventory checks

Common swap logic

• If swap product has same price: no adjustment
• If more expensive: charge difference
• If cheaper: store credit, no refund, or apply to future cycle depending on policy

Example rule

• Customer can swap shampoo A for shampoo B only within the same category and price band

C. Bundle changes

A bundle change means moving the customer to a different subscription plan or SKU set.

This is more complex than a swap

You need to determine:

• whether it applies immediately or next cycle
• whether proration is needed
• whether inventory/fulfillment has already started
• whether billing should be adjusted

Recommended policy

• Allow bundle changes only during an editable window
• Apply changes to the next cycle
• Reprice before invoice generation
• Lock changes after billing cutoff

---

5) Set clear cutoff windows

Beauty subscriptions often require lead times for packing and shipping.

Suggested timeline per cycle

• Day 0: renewal date
• Day 1–3: customer edit window
• Day 4: lock orders
• Day 5: bill payment methods
• Day 6–7: create fulfillment order
• Day 8+: ship

Or another schedule that matches your operations.

Why this matters

Without cutoff windows, you get:

• late edits
• charge disputes
• fulfillment errors
• inventory mismatches

---

6) Build the billing flow

For each cycle:

1. Determine active subscriptions
2. Apply skips/swaps/bundle changes for that cycle
3. Calculate final order total
4. Authorize or capture payment
5. Create invoice/receipt
6. Send order to fulfillment
7. Handle payment failures

Payment failure handling

Implement:

• retry schedule
• card updater support
• failed payment notifications
• grace period
• temporary hold on fulfillment

---

7) Handle inventory and fulfillment

Beauty products are often inventory-sensitive because of:

• limited SKUs
• shades/colors
• expiry dates
• bundled sets

Best practices

• Reserve inventory when orders are locked
• Validate stock before final billing
• Use substitutions only if customer-approved
• Sync subscription edits with warehouse system

If inventory is low

Define policies like:

• allow alternative swap options
• delay shipment
• replace with equivalent product
• notify customer before charging

---

8) Support customer self-service

Customers should be able to:

• skip next box
• swap items
• change bundle tier
• update payment method
• change shipping address
• pause or cancel

UX tips

• Show the next bill date clearly
• Show the cutoff deadline
• Show price changes before confirmation
• Confirm whether changes affect current or next cycle

This reduces support tickets and chargebacks.

---

9) Keep pricing and proration rules explicit

Beauty subscriptions can get messy if customers change bundles mid-cycle.

Decide in advance:

• No mid-cycle bundle changes
• Immediate changes with proration
• Changes effective next cycle only

Common recommendation

For simplicity:

• Swaps can affect the next cycle
• Bundle changes apply next cycle
• Upsells/add-ons can be immediate or next cycle
• Skips only before cutoff

If you allow immediate changes, build proration carefully.

---

10) Build audit logs and event tracking

You’ll want a full history of:

• subscription_created
• item_swapped
• cycle_skipped
• bundle_changed
• invoice_generated
• payment_succeeded
• payment_failed
• order_held
• shipment_created

This is essential for:

• customer support
• finance reconciliation
• dispute resolution
• debugging

---

11) Recommended technical components

Frontend

• customer portal
• subscription editor
• schedule/calendar view
• swap product selector
• billing summary

Backend services

• subscription service
• billing service
• pricing service
• catalog service
• inventory service
• fulfillment service
• notification service

Data store

• relational DB for subscriptions/orders/payments
• event log or message queue for processing changes

Integrations

• payment processor
• tax engine
• email/SMS provider
• warehouse management system
• shipping carrier system

---

12) Example workflow

Scenario: customer wants to skip next month and swap one item the month after

1. Customer logs in
2. Sees next billing date and cutoff
3. Skips next cycle
4. Chooses swap for following cycle
5. System records skip for cycle N
6. System records swap for cycle N+1
7. Billing engine ignores cycle N
8. Cycle N+1 is priced with swapped product
9. Fulfillment receives final order only after cutoff

---

13) Compliance and risk considerations

Make sure you handle:

• PCI compliance via your payment provider
• tax/VAT/GST by region
• cancellation disclosure
• auto-renewal consent
• refund policy
• card network rules
• privacy and data retention

---

14) A good MVP approach

If you want to launch quickly, start with:

MVP features

• recurring billing
• skip next cycle
• swap within a limited catalog
• bundle changes only next cycle
• payment failure retries
• customer portal
• fulfillment export

Later additions

• prepaid subscriptions
• dynamic recommendations
• partial proration
• advanced bundling
• loyalty credits
• gift subscriptions

---

15) Simple rule set to start with

A practical starting policy:

• Customers can skip only before the cutoff
• Customers can swap products from a curated approved list
• Customers can change bundles only for the next billing cycle
• All edits are locked once billing begins
• Payment is captured only after final order total is confirmed
• Fulfillment is triggered only after successful capture

---

If you want, I can also help you with one of these next:

1. a system architecture diagram
2. a database schema
3. a subscription state machine
4. a Stripe/Recharge implementation plan
5. a sample API design for skips, swaps, and bundle updates