---
description: Guidelines of adding new fields for different plugins.
---

# Plugin Fields Configuration

[Payment Request](payment-request/payment-request-configuration), [Bulk Payment Request](bulk-payment-request), [ECommerce](e-commerce/e-commerce-configuration), and [Invoice](invoice) plugins,  all these plugins enable the customization of additional fields, which notably impacts the [Contact Information](../../payment/checkout-page/sections-analysis#contact-information) and '[Order Description](../../payment/checkout-page/sections-analysis#order-description) sections.

{% hint style="info" %}
The configuration settings for the Invoice plugin are sourced from Payment Request configurations
{% endhint %}

Adding Custom or Builtin fields can be done effortlessly by the following three steps:

**Step 1: Go** **to** Ottu Dashboard > Administration Panel > Payment Request, Bulk, or ECommerce> Fields&#x20;

**Step 2: Click** on **Add another Field** butto&#x6E;**.**&#x20;

**Step 3:** Complete the information below and proceed to save.

*   #### **Type:**

    The type of the added field can be categorized as either **Custom** or **Builtin**.
*   #### **Itinerary Display:**

    If checked, the new added field will be shown in the “schedule table” or “planning table” (itinerary table) within the invoice PDF.
*   #### **Display Section:**&#x20;

    It determines the placement of the newly added field on the checkout page. \
    Available options include [Order Description](../../payment/checkout-page/sections-analysis#order-description), [From](../../payment/checkout-page/sections-analysis#from).

{% hint style="info" %}
When neither the Order Description nor the From sections are selected, the default placement for the newly added field will be the [To](../../payment/checkout-page/sections-analysis#to) section. See [Constraints and Restrictions on Section Elements.](../payment/checkout-page/checkout-page-elements-configuration/checkout-page-elements-limitations)
{% endhint %}

*   #### **Is active?:**&#x20;

    It allows for the control and management of the newly added field on a site or platform, providing the ability to enable or disable its usage and visibility.
*   #### **Required?:**&#x20;

    It determines whether a newly added field is mandatory or optional.
*   #### **Validator:**&#x20;

    It imposes constraints or rules on the new field's value. It ensures that the provided value meet certain requirements or conditions specified by the validator.
*   #### **Field:**&#x20;

    A drop-down list of predefined fields. It is presented when the Builtin type is selected in the [Type](#type) parameter.
*   #### **Order:**&#x20;

    It determines the display positioning of the fields within the same section.
*   #### **Placeholder \[en]:**&#x20;

    It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In English).
*   #### **Placeholder \[ar]:**&#x20;

    It provides guidance or an example of the expected input, helping users understand what information is required or the format it should take. (Should be In Arabic).

{% hint style="info" %}
If the [Type](#type) is marked as “Custom”, the [Field](#field) parameter will disappear, and the following fields will be displayed for filling:
{% endhint %}

*   #### **Name:**&#x20;

    `HTML` field name utilized solely for backend validation. It will not be visible anywhere.
*   #### **Label \[en]:**&#x20;

    Custom field's label in English.
*   #### **Label \[ar]:**&#x20;

    Custom field's label in Arabic.
