# Custom fields in Rekaz: labels, types, choices and checkout visibility

Source: https://help.rekaz.io/en/articles/17060477-custom-fields-in-rekaz-labels-types-choices-and-checkout-visibility
Updated: 2026-09-22

Create a customer field when you need a specific piece of information beyond the standard customer details. Decide what answer you need before choosing the field type. A clear question, suitable answer format and sensible requiredness make the information easier to enter and use.

**Settings → Custom Fields**

## New Custom Field

Open New Custom Field to define another piece of customer information. A new form has no type or model selected, and Required and Show in checkout start off. Complete the label, type and model rather than treating the switches as the whole setup.

  

![Saved customer field with type and actions](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653967/ee1691fe9be448fe418fb5ea7c3c/07a4ep.png)

  

_Saved customer field with type and actions_

## Label

Write the question or short description that should identify the information, such as Preferred contact time. It should tell someone what answer belongs in the field without needing a separate explanation. A blank label prevents submission.

Keep the label consistent with the answer format. Preferred contact time with Morning and Afternoon choices is clearer than a vague label such as Additional information attached to the same choices.

## Language selector beside Label

Select English or العربية to enter that version of the label. Write both versions if you want the field to be understandable in both languages. Switching the selector does not translate your text or change the platform interface language.

Review the other-language text shown below the input when present. It helps you keep the two labels consistent, but you still edit each language separately.

## Type

Choose the format of the answer: String, Number, Date, List, Maps, Multi Select, Document or Image. String suits an answer written in words, Number suits a numeric value, and Date suits a calendar date. Maps, Document and Image are for a location, a file and a picture respectively.

Use List when the answer should be one of your named choices. Use Multi Select when several choices may apply. Both reveal an Options editor that you must complete. The other types do not use this choice list in the definition form.

Choose the type according to what you will do with the answer. A contact preference such as Morning or Afternoon is easier to keep consistent with a list than with unrestricted text.

  

![Eight field types: String, Number, Date, List, Maps, Multi Select, Document and Image](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653959/6733027e1468d3941833b6c7c6a4/scnmo3.png)

  

_Eight field types: String, Number, Date, List, Maps, Multi Select, Document and Image_

## Model

Select Customer to attach the field to customer information. This selection is required when creating the field. In this form, Customer is the available model.

The model becomes disabled when you edit an existing field. Check it before the first submission rather than expecting to move the saved field to a different model later.

## Required

Use Required when an answer is necessary for the field’s intended use. Leave it off for information that is helpful but not essential. A preference that a customer may not have is a reason to consider keeping the field optional.

Required and Show in checkout are separate switches. Required describes the need for an answer; it does not choose where the field is shown. Review both settings before saving.

## Show in checkout

Turn this on when you intend to ask for the information during checkout. Leave it off when the field is intended for use within your customer records rather than as a checkout question.

The Arabic interface labels this switch نشر على الموقع الإلكتروني. Review the question, translations and options before enabling it, since you are deciding whether customers should be asked for this information while completing an order.

  

![Field label, translation, type, locked model and independent switches](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653981/4e0e65252790fb964c9c14857486/xckttm.png)

  

_Field label, translation, type, locked model and independent switches_

## Add New Option

For List or Multi Select, add one row for each answer you want to offer. At least one option with text is needed, and every added row needs a value. An extra blank row prevents submission even when the earlier rows are complete.

Add separate choices such as Morning and Afternoon, rather than writing both answers inside one option. Each row represents one selectable choice.

## Option Text

Write a concise answer in each option row. Keep the options distinct so that someone can tell which one applies. The example Morning and Afternoon works with a question about preferred contact time because both are answers to that same question.

Review all rows after editing. Leaving a row blank is different from removing it: a blank row still participates in validation.

## Language selector beside each option

Each option has its own Arabic/English selector. Translate the same choice within its row: Morning and صباحًا belong together, while Afternoon and بعد الظهر belong in another row.

Changing the label’s language does not fill the option translations. Review every option in both languages before submitting a bilingual field.

## Trash icon beside an option

Use the trash icon beside the row you want to remove. Check the row’s text first, because each icon removes its own option. If you added a blank row by mistake, remove it rather than trying to submit it empty.

List and Multi Select still need at least one completed option. Removing an option in the open editor is an unsaved edit until you submit.

  

![Translate, add or remove choices and submit or cancel](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653960/0f7958f60b5fdf7e5ebe5484d8ae/j5mcgs.png)

  

_Translate, add or remove choices and submit or cancel_

## Field label / Actions → Edit

Select the field’s label in the table, or use Actions → Edit, to reopen its definition. Check the saved type, switches and translations before changing them. The model cannot be changed in the edit form.

Changing the type can hide the option editor when the new type does not use a list. Review the whole definition before submitting; changing the label alone and changing the answer format are different decisions.

## Submit

Submit creates the field or saves the open edits. Complete the label, type and model, plus all option rows for a list-based field. If a required message appears, correct that part of the form; scrolling may be needed to reach every field.

After a successful submission, the table shows the label, model and type. Reopen the field to verify the switches and translations, which are not all visible in the table.

  

![Label, Type and Model must be completed](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653969/3d05b99969f0c259d931afdcf6a0/j36t9d.png)

  

_Label, Type and Model must be completed_

## Cancel / Close

Cancel or Close discards the unsaved form edits. When you reopen an existing field, its saved type and options return. This is useful after inspecting another type without intending to change the field.

## Reorder

The dotted handle at the start of a row changes the field order. For keyboard control, focus the handle, press Space to pick up the field, use the Up or Down arrow to move it, then press Space again to drop it. You need more than one field for a change in order to be meaningful.

The new order saves automatically; there is no separate Save button for reordering. Wait for the update, reload the list, and confirm the order remains. Then open a customer’s edit form and check the Custom Fields section. The example shows City before District in both places.

Reordering changes the sequence of custom questions. It does not change their type, whether answers are required, or whether they appear in checkout. Those remain settings of each field.

  

![Example: City placed before District](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653970/6a2d44f362834d4039a97d188dd2/ur3v8e.png)

  

_Example: City placed before District_

  

![The same custom-field order in the customer form](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653973/a66fa5ed54a71b7246bb12570ecf/nceis0.png)

  

_The same custom-field order in the customer form_

## Show / page arrows

The table footer controls how many rows are shown and which results page you are viewing. Disabled page arrows mean there is no page in that direction. These controls navigate the definitions; they do not change field settings.

## Actions → Delete

Delete opens a confirmation that the item will be deleted. Check the selected row before opening it, since the confirmation uses a general warning rather than repeating the field label.

The final Delete button submits the deletion. Cancel closes the warning and keeps the field. Opening the confirmation alone does not delete it.

  

![Confirm or cancel field deletion](https://downloads.intercomcdn.com/i/o/aahcqj2g/2686653974/c2d4612650b11c9d98c8042ac862/qn2tmz.png)

  

_Confirm or cancel field deletion_