Official comment
A great idea and something we have in mind for the future!
A great idea and something we have in mind for the future!
Please sign in to leave a comment.
Landon, is there an ETA?
I completely support this request. Rather than submitting the same suggestion separately, I would like to add my full backing here because this functionality would be transformative.
Currently, I have to create and maintain a separate checkout page for every product, even when multiple products follow exactly the same purchase journey. For example, I might have 20 products using the same checkout structure, but I still need to build 20 individual pages simply to pass through the customer’s selected product.
Allowing a single checkout to dynamically use the selected product, and its associated details, such as name, price and description, would dramatically reduce unnecessary administration. It would also make the system easier to maintain, reduce duplication and minimise the risk of inconsistencies or errors across multiple checkout pages.
This would create a far more scalable purchasing experience for any business managing a substantial range of products, services, events or variations.
Even if the product price could be dynamically altered by a price field within an object record, this could provide exactly the same outcome.