Upsell Products in Online Store checkouts

Store owners can now increase their average order value by upselling additional products after users complete their checkout. In a few clicks, store owners can build upsell funnels for their entire customer journey from Checkout Page to Thank You Page and maximize revenue on every sale.

1. 1Create a new page for Upsell along with the current store pages. Add a full width section and a row in it.
2. 2Click on Add Element button then drag and drop the Upsell element in the row. Store owners can add multiple upsell components in different columns in a row.
3. 3Select the upsell element to configure its settings.
4. 4Upsell can be skipped by adding a Button whose Button action can be linked to Thank you page.
5. 5Sale Action has to be chosen as Go to page and Website page has to be selected as the newly created Upsell page.

• mended to create a dedicated page featuring the Upsell element.

1. 1Add a New page to add Upsell element:

Click on Edit Page:

1. 1Add Upsell Element:
2. 2Make the following configuration in Sale Actions and Website Page for Upsell element. You can add a Button to skip Upsell action incase user doesn't want to buy anything:

Enable disable shipping for Upsell elements in the builder:

Before you begin

“Upsell Products in Online Store checkouts” is part of the Payments → Products area in Adaptive AI. Create products, prices, and sellable service items. Payment settings can create real charges, invoices, subscriptions, tax records, and customer notifications. Use a controlled test and verify the complete financial record before relying on the setup. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the correct payment provider is connected to the correct business and determine whether you are working in test or live mode.
• Verify currency, price, billing frequency, tax behavior, product or variant details, and customer-facing description.
• Use a clearly labeled internal test customer and avoid using a real customer record while validating a new configuration.
• Review the email, receipt, invoice, estimate, fulfillment, or subscription notifications that the transaction can trigger.
• Confirm your user role permits the intended change and that accounting or fulfillment owners know how the result should be handled.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Preview the customer-facing amount, schedule, terms, product details, and payment method before submitting a controlled test.
2. 2Complete the test and confirm the order, transaction, invoice, estimate, or subscription appears with the expected status.
3. 3Verify the customer record, payment timeline, receipt, internal notification, and connected workflow all contain matching information.
4. 4Check the payment provider or connected accounting system to confirm the same amount, currency, identifier, and status were recorded.
5. 5Validate the next billing date, cancellation behavior, inventory effect, or fulfillment action when the configuration is recurring or product-based.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm test and live credentials are not mixed and that the selected product or price belongs to the connected provider account.
• Check required customer fields, currency support, payment-method availability, and any provider decline or validation message.
• Compare Adaptive AI and provider timestamps or identifiers when a payment exists in one system but not the other.
• Review connected workflows and notifications separately from the transaction when payment succeeded but follow-up did not run.
• Do not repeatedly submit a live charge while diagnosing; use logs and a controlled test to avoid duplicate billing.

Best practices

• Use consistent product, price, invoice, and subscription names that make reports and customer statements easy to understand.
• Document refund, cancellation, fulfillment, tax, and failed-payment responsibilities before accepting live transactions.
• Restrict payment-setting access to appropriate staff and review provider connections whenever administrators change.
• Test every new checkout or recurring schedule with the smallest safe test scenario before sharing it publicly.
• Reconcile platform and provider records regularly rather than relying on a single dashboard as the financial source of truth.