> 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/product/legacy-features/how-to-configure-legacy-offers-legacy/how-to-collect-company-information-as-part-of-the-checkout-legacy.md).

# Collect Company Information (Legacy)

| **⚠️ This feature is for the legacy Limio checkout and is supported differently in Modular Checkout. Learn more about** [Modular Checkout](/product/checkout/overview-how-to-customise-the-limio-modular-checkout.md). |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Collecting company information occurs towards the end of the customer journey, and the details are filled out as part of the checkout:

## **Activating company information and tax ID in Limio**

**Campaign -> Offer -> Attribute tab -> Request Company Information**

To enable a customer to enter company details, select the 'Attributes' tab located on your offer pages under the campaign manager. Under this tab, there is an attribute which allows you to set the value of 'Request Company Information' to true:

You will now be able to collect the Company Name and Tax ID of your customers at the checkout.

## **Limio for Zuora**

If company name is collected on checkout this will be the account name otherwise, the account name will be first name + last name.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/product/legacy-features/how-to-configure-legacy-offers-legacy/how-to-collect-company-information-as-part-of-the-checkout-legacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.