Introduction

Contact our sales team directly to scope and plan your migration

Bill by Cycle - Subscriptions will bill every N days, weeks or months. An example subscription would be billed every 30 days.

Bill by Date - Subscriptions will bill on the Nth day of each month. An example subscription would be billed on the 15th of every month.

Bill by Day - Subscriptions will bill on the specified day of each month. An example subscription would bill on the first Friday of every month.

Bill by Schedule - Subscriptions will bill on the specified days of the year. An example subscription would bill on the 1st of July and the 1st of September.

Bill by Relative Date - Subscriptions will bill on a relative schedule every N internals. If a customer purchased an example subscription on the 13th of this month, their subscription would continue to bill on the 13th, either monthly or annually, depending on your selections.

Set up unique discount offers that are specific to given subscription models. For example, offer 15% off on a 30 day subscription model, but only 10% off on a 60 day subscription model for the same product.

Alternatively, set up uniform discount offers for all subscription billing models associated with a given product. For example, offer 10% off on both the 30 day and 60 day subscription models for a specified product.

Bill now

Pause

Resume

Cancel

Skip next cycle

Change recurring date

Change billing model

Change billing address

Change shipping address

View subscription history

Bill now

Pause

Resume

Cancel

Skip next cycle

Swap products

Swap product variants or modifiers

Update order quantities

Change recurring date

Change billing model

Change billing address

Change card on file

Change shipping address

Capture failed payments with the ability to set custom retry frequencies for declined transactions.

Subscriptions - Active Subscribers, Active Subscriptions, Subscription Growth

Churn - Subscription Churn, Churn % by Month and Churn by Type (Cancel, Pause, Payment Failure)

Product Forecast - Recurring Product by SKU and Recurring Product by Date

Additionally, customers with existing logins can login via an email link within the same checkout flow

Merchants will be able to customize the number of retries and the number of days between retried transactions. This configuration occurs on the backend of the sticky.io platform and must be completed by the sticky.io Client Success Manager. Contact your sticky.io Client Success Manager for assistance.

Yes, the subscription frequencies are stored as product modifiers in BigCommerce, and therefore, support a single product display page that allows the consumer to select between one-time purchase or subscription.

No, none of the digital wallets currently support storing the payment method on file in BigCommerce.

The sticky.io Subscriptions app allows for mixed-cart purchases of both subscription and non-subscription items. The consumer is billed in a single transaction on a single order in BigCommerce.

The sticky.io Subscriptions app leverages the native shipping settings within your BigCommerce store. The shipping method selected by the consumer during initial checkout will be leveraged for subsequent rebills, allowing for BigCommerce to recalculate the shipping cost based on this shipping method for each rebill. This ensures an accurate shipping cost even for subscriptions that might change over time. In the event that you change your shipping settings in BigCommerce and the shipping method that was selected during initial checkout is no longer available for an active subscription, the application will inherently leverage the lowest cost shipping method available in BigCommerce.

Yes, the sticky.io Subscriptions app is compatible with multi-currency storefronts on BigCommerce, but the app does not support localization. This means that some UI elements, notably the consumer portal, will remain in English.

Introducing variants to a product that did not previously have variants will break existing subscriptions, because variants are inherently required in BigCommerce and the existing subscriptions will not have variant values to pass in upon rebill. This will result in rebills failing due to missing variant values. Introducing a new variant value to a product that already has variants will not break existing subscriptions, because the existing subscriptions have variant values to pass in upon rebill.

CyberSource has a transaction velocity filter that is enabled by default. The default setting is to "Reject - IP Address 10 per hour". For clients with over 10 rebills in a day, this will cause declines. Contact your CyberSource representative for assistance with modifying this setting to prevent failed rebills.