Applying changes to pricing and packaging is an absolute must as your product evolves.

Luckily, Stigg makes the rollout of such changes easy - they immediately take effect in new subscriptions, and you have the choice between grandfathering existing subscriptions or applying the changes to them too.

When applied to existing subscriptions, a migration process ensures that the changes are reflected in customers’ accounts. For companies with tens of millions of subscribers, this can take a long time.

We've completely redesigned the subscription migration pipeline from the ground up. The new pipeline boasts a massive 100X improvement from the previous implementation - up from 200K subscriptions to 20M subscriptions per hour!

We’ve invested a lot of thought and hard work to ensure that our platform sustains vendors with a HUGE customer base. Click here to learn more.

We're excited to announce our integration with the AWS Marketplace!  🎉

Stigg's native integration with the AWS Marketplace allows you to leverage the same entitlement management and metering infrastructure for access enforcement and usage reporting regardless of where your product is listed (on your public website or the AWS Marketplace) or how your customers are billed (via AWS or other billing solution).

The integration with the AWS Marketplace is currently available in beta for select customers. To access it, please contact Stigg Support.

More details can be found in our docs.

We've updated the payload of the subscription.canceled webhook to include details as to why the subscription was canceled, for example: due to failed payment or a user-initiated action.

The new functionality allows you to trigger workflows to prevent customer churn.

More details about the subscription.canceled event can be found here.

We've made it easier for customers with a Java backend to get up and running with Stigg by leveraging the Stigg Java SDK.

The initial version of the Java SDK serves as a wrapper around Stigg's GraphQL API - caching, polling or streaming of customer entitlements is not currently supported, but will be available soon.

More details on how Stigg can be integrated into your Java application can be found here.

We've added the ability to archive features to which you no longer want to grant new access.

When a feature is archived:

1. The feature will no longer appear in the list of features.
2. It will not be possible to grant new access for this feature in plans and add-ons, or via a promotional entitlement. Customers who previously had access to this feature (for example: by subscribing to an old plan or add-on version or via a promotional entitlement) will not be affected.
3. It will not be possible to analyze the feature's usage using the Feature Inspector.

To archive a feature, use the "Archive" action in the context menu of the specific feature.

More details about archiving features can be found here.

We've added the ability to programmatically provision subscriptions to custom plans.

Custom plans are intended to be used when the price and content (entitlemeny value) of subscriptions are negotiated with each customer and therefore vary between different customers, as is usually the case in sales-led opportunities.

The ability to provision such subscriptions programmatically can be leveraged to implement custom flows, such as automatic provisioning of subscriptions when a deal is closed in Salesforce or Hubspot.

The new functionality is supported in the Stigg Node.js SDK v2.41.0 and the Stigg Python, Ruby and Go SDK v0.584.0 or later.

We've added the ability to download the product catalog of an environment. Doing so allows you to easily compare the pricing and packaging configuration that's defined in each environment.

Downloading the product catalog definition is possible using the context menu of each environment in the Account Settings screen of the Stigg app.

In the common use-case, Stigg only syncs customers with paid subscriptions to billing solutions that are integrated with Stigg.

There are cases where you'd like to explicitly sync customers to the billing solution, and we've recently made this possible by specifying billing information when updating customers. 

Syncing of entities between Stigg and third-party solutions usually takes place asynchronously. 

We've now made it possible to wait until the sync operation is complete. To do so, simply pass the shouldWaitSync parameter when updating customers. If successful, the response will include the ID of the customer in the billing solution.

The new functionality is supported by the Stigg Node.js SDK v2.31.0, Stigg Python SDK v0.577.0, Stigg Ruby SDK v0.577.0, Stigg Go SDK v0.577.0 or later, as well as the Stigg GraphQL API.

We've extended the Stigg Checkout widget to allow you to leverage third-party tax vendors such as Avalara to calculate and collect taxes according to customer's billing addresses.

To do so, follow this short guide.

The new functionality is supported by the Stigg React SDK v4.5.5, Stigg JavaScript SDK v2.24.2 and the Stigg Node.js SDK v2.31.0 or later.

We've updated the Stigg Go SDK to automatically retry requests that fail due to network errors.

The improved error handling is available in the Stigg Go SDK v0.570 or later.