Configure

Below is a step by step process to configure Pelcro on your site.

Basic

Below are the steps required to complete a basic configuration of the platform.

  1. Create a Pelcro account here

  2. Enter your credit card and select the plan based on the features you are interested in. You can learn more about our plans here.

  3. Enter your site information

  • The site name will be used in end-user communication

  • Enter your site domain "https://www.example.com". This will be used in the reset password link sent to the end-users when they request to reset their password.

  1. Upload the site logo and enter your support email by clicking on settings here.
  • The support email will be used in the reply-to address in the automated emails that are triggered by default. You can learn more about them here.

  • Your logo and site name will be used by default in the automated email.

  1. Create your first product and plans
  • Products are the underlying service you are selling. An example can be that you are selling digital access to your site.

  • Pricing plans are the different pricing plans that you are offering the service for. An example is that you are selling the digital access to your site at $10/month and $100/year.

  1. Configure your product to customize the user flow for the end-user to go through all the steps to purchase your product.

  2. Install the integration script on your site

Advanced

Below are the steps required to achieve an advanced configuration of the platform after you've completed the basic configuration.

  1. Customize the design of the user flows by following the instructions here

  2. Customize the automated emails by integrating Pelcro with your MailChimp account. You can learn more about the integrations and steps required here

  3. Enable automated tax collections here

Updated 3 months ago

Configure


Below is a step by step process to configure Pelcro on your site.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.