ESTAGE Support
IdeasMy tickets

Configuring the order form

Updated October 15, 2026

Use the order-form setup wizard to pick products, choose payment methods and checkout mode, and keep prices in sync with ESTAGE CRM.

After you've placed an order form on a page, click it in the live preview to open its setup wizard in the right-hand panel. The header shows a Configured / Not configured badge so you always know its state.

Quick vs. Advanced

The wizard has two modes:

  • Quick (default for new forms) — just pick your product(s) and click Create Form. Everything else is sensible defaults: Stripe, guest checkout, redirect to /thank-you.
  • Advanced — a step-by-step setup for full control over payment methods, checkout mode, and the confirmation step.

Existing forms open in Advanced so you can fine-tune them.

Step 1 — Choose products

Your products are pulled live from ESTAGE CRM. The picker is searchable:

  • Click a product to add it. It appears as a removable chip above the list.
  • Click it again (or the ✕ on its chip) to remove it.
  • Add multiple products — buyers will pick one of them at checkout. Order follows the order you added them.

Note

See "No products found"? You need to create products in ESTAGE CRM first — the form can only sell products that already exist there.

Product details — name, price, billing interval, currency, trial, image, description — come straight from CRM as a snapshot. You don't edit them in Genesis; you edit them in CRM and re-pull them.

Step 2 — Payment methods

(Advanced mode) Choose which gateways buyers can pay with: Stripe, PayPal, Razorpay, Square, Easy Pay Direct, Paystack. Each shows its status:

State Meaning
Connected Ready to use — tick it.
Not connected Connect it first in Settings → Payment Processing.
Not on product The gateway is connected, but this product doesn't support it upstream.

If your Business Details are incomplete, you'll see a banner — PayPal, Razorpay, Square, and Easy Pay Direct need them. Stripe doesn't. Select at least one method to continue.

Step 3 — Checkout mode

(Advanced mode) Decide how buyers identify themselves:

  • Guest checkout — collect name + email; an account is created automatically on purchase.
  • Require login — buyers sign in before paying.

Step 4 — Confirmation

Choose what happens after a successful purchase:

  • Redirect to URL — send buyers to a thank-you page or anywhere else. You can have the redirect open in a new tab: the current page stays where it is and still shows your confirmation message, while the destination opens alongside it.
  • Show confirmation message — display a success message in place.
  • Ask AI — let Genesis design a custom confirmation experience for you.

Saving a form updates its live wiring immediately — no republish needed for the change to take effect on the form itself.

You can also toggle "Show promo-code field" here to show or hide the coupon input on the form.

Generating the form

The final button generates everything:

  • Generate Form (new) or Update & Regenerate (existing) — saves your configuration and builds the live form on your page.

Keeping prices in sync

When you've changed a product's price or details in ESTAGE CRM, use the Patch Hook button (shown once a form is configured). It re-pulls the latest product data and prices from CRM and rebuilds the form from the current template.

Caution

Patch Hook regenerates the form's code from the template — any custom restyling the AI applied to this specific form is replaced. Restyle after your last Patch Hook, or re-apply it afterward. (See Restyling below.)

Deleting

The Delete button removes the order-form component from the page (with a confirmation).

Restyling the form

You can ask the AI to restyle the order form — change the product picker into cards, a dropdown, or tabs; restyle the coupon area; adjust colors and button labels. Genesis is free to change the look.

What it must not break is the wiring underneath — the connections that make the picker, coupon, and payment actually work. Genesis knows to preserve those, so feel free to ask for visual changes; just remember the Patch Hook caveat above.

Was this helpful? Still stuck? Write to the team