# Add Custom Fields to Billing and Delivery Address Objects

**LFS version:** requires Limio for Salesforce v11.67 or later

**Limio version requirement**: requires Limio v88 or later

Limio for Salesforce Acquisition flow allows passing additional custom fields to the billing and delivery address objects to be included in the order payload. In order to do so, two string variables are exposed: `customBillingAddressFields` and `customDeliveryAddressFields`.

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

Use an Assignment element to populate these variables with values. Both `customBillingAddressFields` and `customDeliveryAddressFields` accept a **JSON string,** and the input is validated when a customer submits an order.

Example:

```
customDeliveryAddressFields = '{"custom_field":"custom_value"}';
```

In case of an invalid input formatting, the error message is displayed after clicking Submit Order:

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

**Note**: billing and delivery custom fields are validated consecutively, so in case both values are incorrectly formatted, the error message will reflect one error at a time. Please, make sure to check both inputs before re-testing.

Variables are added to the order in the very last screen element of the flow - Summary Screen - so make sure to assign values anywhere prior to this step.


---

# Agent Instructions: 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:

```
GET https://docs.limio.com/integrations/using-limio-for-salesforce/address-mandatory-fields/custom-address-fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
