What a GoHighLevel Checkout Page Actually Builds

A GoHighLevel checkout page is built from a Two-Step Order element, not a single page template. HighLevel's own setup guide splits the two steps into separate jobs: step one takes contact and shipping information, step two handles payment and confirmation.

Products need to attach to the funnel step before that order element will show pricing. The usual build order is create the product under Payments, drop the Two-Step Order block onto the page, then configure each step.

What each step actually asks for

Step one behaves like a contact form wearing a checkout costume. You can toggle the company name field, change how strict the phone requirement is, and switch shipping on or off depending on whether anything ships at all.

Step two stays narrower by design. It only touches payment labels, headers, and the confirmation button text, and the same form accepts one-time purchases and recurring subscriptions side by side.

Cart Mode changes the page's shape further. Switching it on lets a buyer add several products and adjust quantities before moving into payment, instead of being locked to one item per checkout.

Stripe handles most of the payment processing here, though the order form also works with PayPal and other processors. One restriction is easy to miss, per HighLevel's product setup documentation: only recurring products import straight from Stripe, while one-time products have to be built inside Payments itself.

Order bumps and the one-click upsell

A bump offer is the checkbox that sits on the order form itself, adding a second product to the same purchase before the card gets charged. Building one takes a few steps, the ones HighLevel's order bump guide walks through in order.

• Create a form and add the Sell Products element to the canvas.
• Add the main product first, because bump products stay hidden without one attached.
• Add the bump product and set its headline, icon, and highlight color.
• Save the form, which locks the bump into that product's checkout flow.

Only one recurring product is allowed per form, whether that's the main product or a single bump, which keeps the billing logic from colliding. Every major processor GoHighLevel supports works with bumps the same way.

HighLevel's changelog entry on form upsells describes a newer piece: a Sell Products element inside a form can carry an upsell button on the next funnel step, accepted with one click since the card is already on file. It works with both normal and bump products, skipping the extra page a one-time offer usually needs.

Where this fits inside the funnel

A checkout page rarely stands alone. It sits between whatever drew the lead in and whatever happens after they pay, which is why how the rest of a GoHighLevel sales funnel moves a lead to close matters as much as the order form itself.

Starting from a template rather than a blank canvas saves most of this configuration. GoHighLevel's funnel template library ships several checkout layouts already wired for bumps, so the main work left is attaching the right product.

Carts still get abandoned mid-payment, and the follow-up sequence after that is often what actually recovers them, the same approach behind a cart recovery flow built on GoHighLevel and SMS for one ecommerce account.

Getting the product, the order form, and the automation sequenced correctly the first time avoids most of the rebuilding agencies end up doing later. That sequencing is exactly what GHL setup and configuration work is meant to get right from the start.

Cover photo by Ercan Şenkaya on Pexels