Dynamic Products and Pricing Within Ontraport Checkouts

**Feature Request: Dynamic Products and Pricing Within Ontraport Checkouts**

I have commented on several similar requests, but I believe this deserves its own post because it represents both a significant limitation and a tremendous opportunity for improvement.

Currently, the product and price within an Ontraport checkout are fixed. This means that businesses offering multiple products, product variants, or pricing options must create a separate checkout page for every variation.

For example, we sell examinations to our students across numerous subjects, levels, and prices. Although the checkout journey is fundamentally the same, we must create and maintain a bespoke checkout for every exam variant.

This creates substantial administrative overhead:

1. Every checkout page must be created, configured, tested, and maintained separately.

2. If an error is discovered or a change is required, the same amendment must be made manually across every duplicated checkout.

3. There is a significant risk of inconsistent wording, settings, automation, or payment information between copies.

4. The complexity increases every time a new product or pricing option is introduced.

I have recorded a Loom video demonstrating the practical impact this has on our system:

https://www.loom.com/share/3db7a662c3a346b1ac7228465f3fc68c

**Requested functionality**

Please enable the product, pricing option, or price within an Ontraport checkout to be populated dynamically.

Ideally, a checkout could receive an approved product ID or pricing option from a trusted source such as:

1. A URL parameter

2. A contact or custom object field

3. A merge field

4. An Ontraport automation

5. An API request

The checkout would then securely retrieve and display the corresponding product name, description, price, payment structure, and other relevant information from Ontraport.

This would allow businesses to build and maintain one central checkout page while dynamically presenting the correct product and price based on the customer’s selection.

Any amendments to the checkout layout, wording, payment settings, or legal information could then be made once and applied consistently across every product using that checkout.

This would significantly reduce duplication, administrative time, configuration errors, and ongoing maintenance. It would also make Ontraport’s checkout functionality far more scalable for businesses with large or frequently changing product catalogues.