Recharge now opens in a standalone tab, rather than within the BigCommerce embedded view. No action is needed on your part and does not affect any functionality for your store - you'll see this update the next time you log in to your portal. 

You’ll experience these immediate benefits: 

• More room to work: You’ll be able to use the full page to manage your subscriptions. 
• Improved performance: The Recharge app experience will feel faster and smoother in a full-page tab than it does within the BigCommerce.
• Broader browser and device support: You can now use Recharge on Safari, in Chrome incognito mode, tablets and other mobile devices!

View documentation here to learn more. 

Now you choose to bulk update the subscription properties of all products in a collection. 
From any collection details page, you can choose to bulk update subscription properties for all products in that collection. You will be taken to a page, similar to the product details page where you can select the subscription properties you want. We are leveraging the power of Recharge’s async batch endpoint to allow subscription property updates of up to 10,000 products. Since a collection is just a grouping of products, you are free to update a subset of products individually or in a different collection without affecting any other products.

For more information, visit our support documentation. 

On BigCommerce, merchants can decide if a product variant is “Purchasable” on their storefront. When a product variant is set to “Purchasable”, it appears on the storefront and the Add to cart button is displayed when the product variant is selected. When the “Purchasable” setting is disabled, the product variant appears on the storefront, but the Add to cart button is hidden when the product variant is selected. 

Recharge has added this setting to our product so that when the “Purchasable” setting is disabled for a product variant, it is hidden in the customer portal. 

How does it work?

• When a product is set to “Purchasable” in BigCommerce, it will be displayed to customers in the product variant dropdown
• When the product is not set to “Purchasable” in BigCommerce, it will be hidden from customers in the product variant dropdown
• If all variants on product have the “Purchasable” setting disabled, the entire product will be hidden from customers in the Customer portal

• Checkout cart: triggers a workflow after the shipping quote process but before the order is submitted in Recharge
• Recurring order regeneration: triggers a workflow when a charge is regenerated for a recurring order (usually due to a product add/swap

• Select one of the new triggers when creating a workflow
• When creating a workflow using the checkout cart trigger, the workflow will modify the cart prior to the creation of the initial order
• When creating a workflow using the recurring order regeneration trigger, the workflow will modify the products prior to regenerating the recurring order

Store owners can now control what their team members can access. This feature will help reduce errors & business risk and increase productivity by removing store owners as bottlenecks.  

1. Default new account permissions: Because both Shopify and BigCommerce allow platform users to create accounts in Recharge simply by visiting the app, Recharge permissions allows store owners to set a default level of permissions for all new accounts. That way, merchants can specify that all new accounts will only receive access to the "Customers" and "Orders" sections, for example.
2. Existing account permissions: Store owners are able to view and edit the permissions of any existing user's store account--even users who have only ever accessed Recharge from Shopify.

How do permissions work? 

Permissions are used to determine which sections of the app a user can view. Users will only see sections of the application to which they have access. If they attempt to navigate to a section of the app that they do not have permission to see, they'll see an "Access denied" message instead of the page. These permissions are set at the account level, so a user with access to multiple stores can have different permissions for each individual store as determined by the store's owner.

Visit the documentation library to learn more. 

• Standard themes: Novum & Prima
• Theme Engine custom themes: Base_v3.0.0, Novum_v3.0.0, and legacy_novum 

If you are using legacy_base you must create a new theme for your customer portal using the Base or Novum theme template. Once you finish customizing your theme and assign it as your current theme you will begin seeing these performance improvements.

All merchants using Recharge can now access a new 'permission' to set whether a Recharge user can view/access the 'API Tokens' page under Integrations page. 

With this update, Recharge API token generation is ungated for any user with the appropriate permission!

Who has access by default? 

• All users with 'Store Owner' profile
• All users on stores that had API token permissions prior to Nov 5, 2021

Confirm you've access! A 'Store Owner' can instantly enable this permission for users by clicking the 'API tokens' checkbox on the 'Permissions' section of their merchant portal. 

IMPORTANT: The 'store owner' must read and accept the new terms of service for Recharge API before any user can access the API tokens page or generate a new API token. 

To learn more about permissions, click here. 

To learn more about our updated API terms of service, click here. 

Within the Orders section, we've updated the Upcoming orders tab and the Charge Errors tab to include some handy new search and filter options. This update makes it easier than ever for you to find the charge that you're looking for based on the data that you have (e.g. customer email, Recharge charge ID), or to narrow your view down to only a subset of records (e.g. all charge errors with a "first tried" date within the last 7 days).

Filter by: Order date

Filter by: Charge error type (existing filter, now moved into Filter menu for consistency), First try date

Developers using Recharge API (v2021-01 and v2021-11) now have the ability to access key API token information with a simple GET request. 

Once executed, the API resource will return information such as

• API token name
• Contact email associated with the API token
• Permission scope associated with the API token

Developers working with multiple tokens can use this endpoint as an admin tool to speed up their workflows. For example, a developer could prevent errors associated with incorrect permissions by quickly checking the API token permissions prior to accessing the endpoint.

Try it today with GET api.rechargeapps.com/token_information

To learn more, visit our API reference documentation here. 

You can also check out this blog post on how Recharge is empowering our developer community. 

Merchants using the Recharge API can now have access to configurable rate limits through their API tokens. This update represents significant efficiency gains within our API and with these configurable rate limits, merchants can scale rapidly and implement innovative promotions reliably. 

• New API tokens for merchants on the PRO or ENTERPRISE plan now default to 2X the existing call volumes.
• Even higher rate limits are available upon request for merchants who use the Recharge API heavily. 

These new rate limits can be several times the existing rate limits and enabling them would require the generation of a new API token from the Integrations page. Once created, these new API Tokens will include a prefix, as shown below:

• ‘sk’ indicates that this is a secret key that must remain confidential and not shared publicly in any way
• Example: 2x1 - this is the rate limit multiplier with 2X the current leak rate (standard is 2 requests/sec) and 1X the bucket size (standard bucket size of 40 requests).

If a store is at the maximum token limit, an existing token should be replaced with a new API token that supports the higher rate limits. 

Check it out today!