Order Forms & Checkout Pages

Order forms combine service selection, custom questions, and checkout in a shareable form. They can have several steps and can be embedded on your website. A service also has its own direct checkout page when you only need to sell that service.

Access

Open Order Forms in the team navigation. Permissions are view_order_forms, create_order_forms, edit_order_forms, delete_order_forms, and manage_order_form_submissions. Configure a supported payment provider for paid checkout.

Services offered in the builder come from eligible catalog services. Check that each service is published, active, and configured for catalog visibility before building your form.

Create a form

1. Choose Create Order Form and enter a title and optional description.
2. In Build, add steps and drag or add fields into them.
3. Add service-selection fields and configure the services and pricing options you want to offer.
4. Add the inputs and content needed for the brief. Configure labels, options, and required fields in the field editor.
5. In Settings, choose what a successful purchase should create.
6. In Form Conditions, add any show/hide rules.
7. Preview on desktop and mobile, then save a draft or publish.

Available field groups include service fields, inputs, and content. Use the builder's supported fields for items such as text, choices, uploads, signatures, rich content, images, and FAQs. Backlink catalog fields depend on module access.

Choose purchase behavior

The settings distinguish these outcomes:

• Add to stock only: Record the service purchase as allowance the client can use later.
• Add to stock and create a request: Record the purchase and create work from the submission.
• Create lead: Collect an inquiry through the lead flow, with an optional thank-you URL and message.

The builder prevents stock-only behavior when a link catalog field requires request creation. Check the chosen behavior when testing; a successful purchase does not always mean a request should be created immediately.

For forms designed to collect inquiries rather than payments, see Leads & Intake Forms.

Conditional fields

A condition watches a field and compares its value using contains, equals, or not equals. Choose show or hide and the target field.

Test each branch, including the effect on required inputs. Keep labels clear so clients understand which information they need to supply.

Checkout and confirmation

Clients can open a published public form without first signing into the portal. Checkout collects the contact and billing information needed for the purchase and uses the payment options configured for the workspace.

Check service quantities, recurring tiers, add-ons, taxes, and coupons that apply to your form. Payment completion and the configured service behavior determine which purchases, subscriptions, and requests are created.

Do not treat a manually changed submission status as proof that a payment succeeded or was refunded. Verify the associated financial record and provider when investigating payment issues.

Publish and share

Forms have Draft and Published states. Draft forms are not publicly available. Publish the completed form, then copy the link from its detail page.

The public checkout path is /order/checkout/{form-slug} on the workspace's domain. Use the generated link so it includes the correct workspace or custom domain.

For one service's direct checkout, use /services/checkout/{service-slug}. This is a separate flow from an order form.

Embed on your website

Open the form's embed-code action and copy the generated iframe or widget code. Paste that code into the relevant part of your website, then test the embedded form and checkout on desktop and mobile.

The generated widget uses the workspace host's /js/embed.js with the form's URL and ID. Copy the current code from the app so those values are correct.

Manage forms and submissions

Open a form to review its details, preview, share link, embed code, analytics, and recent submissions. Use Edit, Duplicate, Publish, or Move to Draft as needed. A duplicate starts as a draft.

Open Submissions to inspect the client's submitted values and related records. Supported manual submission states are Pending, Processing, Completed, and Cancelled. These are submission states, distinct from a payment provider's transaction status.

Deleting a form moves it to the recycle bin. Restore it if needed. Permanent deletion also removes related submissions, so review and export the information you need first. See Archive & Recovery.

Troubleshooting

• Form not loading: Check published status, the copied URL, workspace domain, and whether the form was deleted.
• Service missing: Check service availability and catalog settings.
• No request after purchase: Check service behavior; stock-only purchases intentionally leave request creation for later.
• Payment incomplete: Review provider setup and the payment record before asking the client to retry.
• Wrong fields: Review the builder, selected services, required flags, and conditions.
• Embed problem: Copy fresh generated code and test the public URL directly before troubleshooting your website.