Purchases are a commitment to a product. For a free product this is just requesting access, while for a paid product, it is what happens when a user ends the payment flow.

​
Order fullfilment - Post purchase actions

Purchase is the first step in the flow, it is obtaining access. Once a purchase was successful you’ll need to provide the end user with the purchased product. It is important to undersand that the purchase is disconnected from providing the product. Post purchase actions are the mechanism to fullfil the order.

We support a variety of post purchase actions, that you can set up for your products. This can be set for every Product type or for a specific Product.

  • Link (redirect after purchase)
  • Callbacks
  • Download file
  • Webhook for merchant
  • Send email to merchant
  • Zapier action for merchant
  • Fill a form
  • Create a license key

Post purchase actions continue to be available after the product has been purchased. This means the user can go back and redownload the file, or click again on the link. Merchants can choose to limit this behavior, by setting a limit on the number of times a user can perform the post purchase action.

​
Versioning

If product has versioning enabled, then it is tied to the current version. Access is then limited by the setting at the time of purchase. This way, users can receive access to updates of products they purchased.

​
Purchases for an account level

If you’re a B2B company, and your software is used by teams, you may want your marketplace to allow purchases for an entire account. This is a way to sell your software to your entire team, instead of selling it to individuals.

In order to support this, you’ll need to:

  1. Enable account level purchases in the store settings. You can also choose whether all purchases are on the account level, or up to the user to choose.
  2. Make sure to send the accountId property in the end user session.
  3. If a product has seat-based pricing, you’ll need to send the seats property in the account in the end user session.

Purchases that are made for an account level will show up in the Purchased page (and API) for all users within that account automatically.

​
Off-SideDish purchases

If you want to manage purchases for products on your own, you can pass purchases to SideDish as part of the session creation.

ListsApproval process