​
About

In some cases, you might want to limit the purchases of products to specific requirements. For example, you might want to limit the purchases of a product to a specific country, or limit a specific product to users with a PRO subscription tier. SideDish supports that.

​
How it works

Store owners can decide on requirements. A requirement is a string value of a user.requirements[] that a user must have in order to start the purchase flow. User.requirements are passed to SideDish by you in the session creation. Read more about it here.

Requirements are being configured on the store settings page by team members with role developer. We limit this to developers because they are the ones who needs to send this data to SideDish.

Other team members can then add a requirement to a product or product-type (when applied to product-type, all products with this type share that requirement) from the approved list of requirements.

When a user tries to purchase a product with requirements, then we check if the user has these requirements (match user.requirements with product.requirements). If they pass, they can proceed with the purchase. If they don’t pass then we follow the store settings for unmet requirements.

Regardless, we will still track analytics for clicked and stopped by unmet requirements, and track a list of blocked users for store owners to use / export.

​
Unmet requirements

Frontend (for the user)

  • Redirect to a different page
  • Callback(for customized action on your app)

Backend (for the team)

  • Webhook (for customized action)
  • Email a team member (try to upsell)
SearchRelated products