Stigg Product Updates logo

Product Updates

Back to Homepage Subscribe to Updates

Labels

  • All Posts

Jump to Month

  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • August 2022
  • July 2022
  • June 2022
Announcement
a year ago

Ability to leverage third-party tax compliance solutions to calculate customers' tax rates

We've made it easier to leverage third-party tax compliance solutions such as Avalara to calculate tax rates and stay compliant with tax regulations.

To so do, simply provide the customer's billing address to the third-party tax compliance solution to calculate their tax rate. Then, include the response in the billingInformation of the provisionSubscription and estimateSubscription methods of the Stigg SDK.

When Stigg is integrated with a billing solution, Stigg will auto-magically create the relevant tax objects in the billing solution if they don't already exist and apply them to customers' invoices.

The new APIs are supported by the Stigg Node.js SDK v2.13.0, Stigg Python SDK v0.511.0, Stigg Ruby SDK v0.511.0, Stigg JavaScript SDK v2.13.0 or later.


Avatar of authorOr Arnon
Announcement
a year ago

Scheduling of subscription migration to the end of customers' billing periods

When changes to the plans add-ons are rollout out only to new subscriptions (for example: when changing their price), grandfathering takes place.

To prevent a SKU sprawl, Stigg allows you to manually migrate each subscription to the latest plan and add-on version.

It's now possible to schedule subscription migrations to take place at the end of customers' billing period directly from the Stigg app, in addition to being able to trigger them immediately.

Avatar of authorOr Arnon
Improvement
a year ago

Ability to create metered features during the usage-based price definition flow

We've made it easier than ever to model your usage-based pricing in Stigg by allowing you to seamlessly create metered features as part of the price definition experience.

Usage-based pricing models require usage to be reported on metered features. During the price definition of usage-based charges, you'll be asked to select the metered feature that will be leveraged to bill customers.

If you already created the feature, search for it and select it from the list.

If the relevant feature still doesn't exist, simply enter its name and click on the link in the drop-down menu to create it. 

After it's created, it will be automatically pre-selected, and you can continue to set the price amount of each unit.

The created feature will also be accessible under the Features section of the Stigg app.

More details about how to model usage-based pricing can be found here.


Avatar of authorOr Arnon
Announcement
a year ago

Plan price definition using multiple billable metrics

We've completely redesigned the process of defining plan prices in the Stigg app, and have extended it to support more advanced use cases.

The new configuration allows you to define the plan price using a recurring fixed fee (referred to in the Stigg app as a "base charge"), based on feature usage, or by a combination of both.

Usage-based charges can be billed in advance (i.e. seats), or according to actual consumption (pay-as-you-go, i.e. compute time).

Stigg's snap-in widgets have also been updated to support these new use cases.

1. When a plan's price is composed of more than one charge, the plan's price in the Stigg pricing table widget will appear with a "Starts at" indication, and the actual value will be composed of a sum of the base charge (if exists) and all of the usage-based charges with in-advance commitments.

2. In the new customer portal widget version, customers can see all of the charges that they're paying for in the "Subscription overview" section, as well as see an indication for paid usage under the "Usage" section.

Stigg's integration with Stripe also supports these new use cases and allows customers to be billed for all of the charges in the same invoice.

The new configuration allows to you move from a pricing that's based on one billable metric to one that's based on multiple metrics with no-code.

More details about the new price configuration method can be found here.

Multiple billable metric pricing is supported by the Stigg Node.js SDK v2.10.3, Stigg Python SDK v0.493.0, Stigg Ruby SDK v0.493.0, Stigg JavaScript SDK v2.9.2, Stigg React SDK v3.0.0, Stigg Vue.js SDK v2.0.0, Stigg Embed SDK v3.0.0 or later.


Avatar of authorOr Arnon
Announcement
a year ago

Redesigned customer portal widget

We're excited to announce our redesigned snap-in customer portal widget. The new customer portal widget includes the following improvements:

1. Ability to view the estimation of the upcoming bill in the subscription overview section.

2. Ability to view the usage of the value metrics that the customer is paying for in the subscription overview section (applicable only for subscriptions of paid plans)

3.  A dedicated usage section that provides customers with visibility for the usage of all the metered features that they're entitled to.

4. A dedicated section and button for accessing historical invoices.

The new design is available in the Stigg React SDK v3.00, Stigg Vue.js SDK v2.00 and the Stigg Embed (HTML) SDK v3.00.

If you're using an older version of the React SDK, please review our migration guide.


Avatar of authorOr Arnon
Announcement
a year ago

Syncing customer metadata to Stripe

We've extended our integration with Stripe, and now allow you to leverage the Stigg API and SDKs to sync metadata to the Customer object in Stripe.

To do so, when provisioning or updating customers via the Stigg API and SDKs, simply include the relevant metadata under the billingInfo property.

As with the rest of the billingInfo properties:

1. Providing the billingInfo when provisioning or updating customers will force the customers to be synced to Stripe.

2. Stigg doesn't store the billingInfo data, and only serves as a pass-through for sending it to Stripe; therefore, the information will only be stored in Stripe.

The new functionality is supported by the Stigg Node.js SDK v2.9.0 or later.


Avatar of authorOr Arnon
Announcement
a year ago

Ability to archive customers

We've added an ability to archive customers. When customers are archived, their PII (name and email address) will be nullified, and they will no longer appear in the Stigg app UI or be returned by the Stigg API and SDKs.

When Stigg is integrated with a billing solution, customers that are archived in Stigg will still exist in the billing solution to allow upcoming invoices to be finalized.

To archive customers in the Stigg app, under the customer details screen:

1. Ensure that they don't have any active paid or custom subscriptions - if they do, cancel them first.

2. Click on the dotted menu icon of the relevant row, and select the "Archive" action.

3. Confirm the action by clicking on the "Archive" button in the opened modal.

Archiving customers is also supported by the Stigg Node.js SDK v2.10.1 or later, Stigg Python SDK v0.491.3 or later, as well as the Stigg GraphQL API.

Avatar of authorOr Arnon
Improvement
a year ago

Improved feature definition experience

The basic building blocks of the Stigg platform are features, which represent configurable functionality in your application that can be monetized.

We've simplified the flow for defining features and made the distinction between boolean, configuration and metered features more clear.

As part of this change, the "fluctuating" and "incremental" meter types have been unified, and Stigg can now automatically reset the measured usage of any metered feature. 

More details about Features in Stigg can be found here.


Avatar of authorOr Arnon
Announcement
a year ago

Python SDK with typesafe classes (beta)

We're excited to announce the beta release of a typesafe Stigg Python SDK.

Similarly to the initial version of the Python SDK, the new SDK version provides Python clients for interacting with Stigg's GraphQL API based on the operations that Stigg's Node.js SDK is using under the hood.

Significant improvements from the initial SDK version include:

- Typesafe classes

- Ability to generate both synchronous and asynchronous clients

More details about the new Python SDK version can be found here.

Avatar of authorOr Arnon
Announcement
a year ago

Ability to undo scheduled cancelations

When the product's customer journey is configured to downgrade customers to a free plan upon cancelation, and cancelation is scheduled to take place at the end of the current billing period or a later date:

1. Stigg admins can undo the cancelation by clicking on "Cancel update" in the subscription details screen

2. Customers can undo the cancelation in a self-served manner using the Stigg customer portal widget


Avatar of authorOr Arnon