Expiring or Termed Subscriptions Using Webhooks

Creating this experience will require work from the client's development team or their technology partners and is expected to be self-serve.

If the client requires technical support from the Ordergroove team then any hours used will be applied toward the available service hours within the client's agreement. If not enough service hours are available then you may purchase additional hours by contacting Ordergroove.

Additionally, if you'd like to discuss possible customizations to this experience as outlined below please contact Ordergroove for a consultation.


  • Expiring subscriptions are subscriptions that are canceled after a set of conditions are met. The most common reason clients build expiring subscription functionality is to power a subscription that will cancel after a defined number of shipments. 
  • In order to set this up, you'll need to create a custom application that can receive HTTPS requests from our platform and configure your Ordergroove program to send webhooks to that application.
Areas Impacted
  • Front end for tracking which items are termed subscriptions on the order
  • Backend for handling cancel logic when subscription should expire
  • Backend for receiving webhook data
Out of Scope of Solution
  • Order XML modifications
  • Different endpoint for termed subscription and standard subscription orders
  • Custom messaging (current order count, remaining orders, etc.) in Ordergroove transactional emails
  • Display of current or remaining order counts in Ordergroove
  • Subscriptions created via Instant Upsell
  • Subscriptions created via Ordergroove
  • Gift subscriptions managed by a different user other than the individual creating the subscription
  • Webhooks Integration
  • Cancel Application

Resources Required


 Client/Systems Integrator

  • [S-M] Create separate SKUs for termed subscriptions
  • [M] Create an endpoint to receive data from OG webhooks
  • [S] Configure webhook setup
  • [L] Create a cancel application that:
    • Ingests the webhook data for a subscription
    • determines when a subscription should be canceled
    • Make an API call to cancel the subscription when the criteria are met



You should instruct your Customer Service Representatives that termed subscriptions should not be created via your Ordergroove admin. Doing so could result in the subscriptions never getting canceled through your cancelation application.


Example Design Using Subscription Extra Data

For an example design and detailed instructions, take a look at Expiring or Termed Subscriptions Using Webhooks in our Developer Documentation.