> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form.md).

# Modular Checkout Subcomponents in Form

## Adding a Subcomponent

To add subcomponents, you'll need the Form component. Follow these steps:

1\. Click on "Add Component".\
2\. Search for the Form component under Acquisition.\
3\. Click on the pencil edit button.\
4\. Select "Edit Subcomponents"

<figure><img src="/files/ZK8Ng3JvDxyFrpQ86stR" alt=""><figcaption></figcaption></figure>

See this article for more information on editing subcomponents: [Common customisations for Form subcomponents](/components/component-library/modular-checkout-components/common-customisations-for-form-subcomponents.md)

## Create your checkout

To create a working checkout, you'll need the following subcomponents:

1\. First Name\
2\. Last Name\
3\. Email\
4\. Phone\
5\. Billing Address\
6\. Delivery Address\
7\. Payment Details\
8\. T\&C Checkbox\
9\. Submit button

<figure><img src="/files/nKhcIVPF9CtfCnDBgd21" alt=""><figcaption></figcaption></figure>

## Managing Conditionality in Subcomponents

In release 94, we released a new feature to allow you to manage when your subcomponents should appear, based on certain conditions.

You can read more about that [here](/components/component-library/modular-checkout-components/managing-conditionality-in-subcomponents.md).

## Custom subcomponents

From release 102, for customers using the Limio Developer Experience to create custom components, it is now possible to create custom subcomponents.

This enables new workflows and means even more customisation is possible when developing a checkout flow. Whether it's inserting custom fields to collect user information or displaying information, it is now possible to deliver that easily with just one small change.

To read more about custom subcomponents, you can visit our [docs here](https://docs.limio.com/developers/custom-components/custom-subcomponents).

To learn more about the Limio Developer Experience, you can read more in the [Developers section](https://docs.limio.com/developers).

## Standard Subcomponents

[First Name Field / Last Name Field / Email Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponents-first-name-field-last-name-field-and-email-field)

[Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-field)

[Address Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-address-fields)

[Postal Code Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-postal-code-field)

[Payment Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponents-payment-field)

[Display Text Field](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-display-text)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.