Using Predefined Values in Order Tag Filters

Before configuring the filters, ensure the following prerequisites are met:

• The following mutations are enabled in the manifest:

  • `createSetting`

  • `updateSetting`

• The user has a role with the necessary permissions:

  • `SETTING_VIEW`

  • `SETTING_CREATE`

  • `SETTING_UPDATE`

Identify the predefined values you want to use in the

`tag1`

`tag2`

`tag3`

Common use cases for tags include grouping orders by:

• Brands – Filter orders based on associated product brands.
• Regions – Organise orders by geographical locations.
• Sales Channels – Differentiate orders from various sales platforms (e.g., online store, marketplace, retail).
• Payment Methods – Categorise orders by the payment method used (e.g., credit card, PayPal, bank transfer).
• Purchase Order Reference – Track and filter orders using specific purchase order numbers.

To configure the filters, create a new setting at either the ACCOUNT or RETAILER level with the following details:

• Name: Use the pattern:

  • `fc.order.options.tag1`

  • `fc.order.options.tag2`

  • `fc.order.options.tag3`

• Context: Choose either ACCOUNT or RETAILER, based on your requirement.
• Context ID: Provide the corresponding context ID (e.g., the retailer's ID if using the RETAILER context).
• Value Type: Set this to JSON.
• Value: Enter the predefined options in JSON format as shown below:

1{
2  "options": [
3    {
4      "value": "NIKE",
5      "label": "Nike"
6    },
7    {
8      "value": "ADIDAS",
9      "label": "Adidas"
10    },
11    {
12      "value": "PUMA",
13      "label": "Puma"
14    }
15  ]
16}

Once configured, the

`tag1`

`tag2`

`tag3`

• For easy selection, three or fewer values are displayed as a radio button group.
• Four or more values appear in a dropdown menu for better usability.