> ## Documentation Index
> Fetch the complete documentation index at: https://services.docs.growcrm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Order Forms: Collect Project Info Before Payment

> Attach a drag-and-drop questionnaire to any service to capture project briefs, file uploads, or preferences before a customer pays.

Some services need more context before work can begin — a project brief, a set of dimensions, a brand file, or a simple preference choice. A Custom Order Form is an optional questionnaire you attach to a single service. When a customer selects that service during checkout, the form appears immediately after their selection and before the payment step, giving you exactly the information you need to start delivery. This page explains how to enable a custom order form for a service, which field types are available, and where the submitted answers are stored once an order is placed.

<Note>
  Custom Order Forms are separate from [Checkout Forms](/checkout/forms). A
  Checkout Form is the public page that lists your services for sale. A Custom
  Order Form is the per-service questionnaire a customer fills in after choosing
  one specific service.
</Note>

## Enabling a Custom Order Form

Custom Order Forms are configured inside each individual service, not from the Forms list.

<Steps>
  <Step title="Open the service">
    Go to **Products & Services → Services** and open the service you want to
    attach a form to.
  </Step>

  <Step title="Go to the Form tab">
    Select the **Form** tab inside the service editor.
  </Step>

  <Step title="Enable the form">
    Set **Service Form Status** to **Enabled**. The drag-and-drop form builder
    appears below the toggle.
  </Step>

  <Step title="Build your form">
    Add fields from the available field types, configure their labels and
    options, mark any as required, and drag them into the order that makes the
    most sense for your customers.
  </Step>

  <Step title="Save the service">
    Save the service. The form is now live and will appear to customers the next
    time they select this service during checkout.
  </Step>
</Steps>

## Available Field Types

The form builder supports eight field types to cover a wide range of information-gathering needs. Add as many fields as you need — with one important exception noted below.

| Field Type            | Description                                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------------------ |
| **Header**            | A section heading to visually separate parts of a long form. No answer is collected from the customer. |
| **Text**              | A single-line text input, suitable for short answers like names, URLs, or codes.                       |
| **Number**            | A numeric input field for quantities, measurements, or other numerical values.                         |
| **Textarea**          | A multi-line text area for longer answers, such as project descriptions or instructions.               |
| **Dropdown (Select)** | A dropdown list from which the customer picks exactly one option you define.                           |
| **Checkbox Group**    | A group of checkboxes allowing the customer to select one or more options from a list you define.      |
| **Radio Group**       | A group of radio buttons from which the customer picks exactly one option.                             |
| **File Upload**       | Allows the customer to attach a single file to their order.                                            |

<Warning>
  You can only add **one File Upload field per form**. If you need customers to
  submit multiple files, ask them to archive their files into a single upload
  before checking out.
</Warning>

## Marking Fields as Required

Any field in your form can be marked as **Required**. When a field is required, the customer cannot proceed past the custom order form step until they provide a valid answer. Use required fields for information that is truly essential to fulfillment — keeping optional fields unmarked reduces friction for customers who may not have every detail ready at checkout.

## Where Answers Are Stored

Once a customer completes checkout, their form answers are saved with the order and surfaced in two places:

<CardGroup cols={2}>
  <Card title="Order Details Panel" icon="file-lines">
    Navigate to **Products & Services → Orders** and open the order. The
    customer's answers appear in the **Order Details** panel, so your team can
    reference them at any point during fulfillment.
  </Card>

  <Card title="Project Description" icon="diagram-project">
    If the service is configured to automatically create a project on checkout,
    the answers are appended to that project's description. Your team sees the
    brief the moment the project is created, without needing to open the order
    separately.
  </Card>
</CardGroup>

<Tip>
  Combine a Textarea field for the project brief with a File Upload field for
  reference assets — together they give your team everything they need to start
  work immediately after payment clears.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Checkout Process" icon="cart-shopping" href="/checkout/process">
    See exactly where the custom order form appears in the customer's step-by-step
    checkout journey.
  </Card>

  <Card title="Orders Overview" icon="inbox" href="/orders/overview">
    Learn how to view submitted form answers inside a completed order record.
  </Card>
</CardGroup>