Skip to main content

Custom Fields

How to access on Fynd Platform


Sellers can create additional custom fields against the already existing objects in the Fynd platform. For example, a furniture retailer might want to showcase details such as material composition, dimensions, and assembly instructions for their products. This kind of information is specific to certain product categories and provides customers with detailed insights relevant to their purchase decisions.

How to Create Custom Fields?

  1. In the Custom Data Settings page, under custom fields select the required object where you want to create additional custom fields. You will get a list of existing custom fields. You can either edit the existing one or create a new one.


Figure 1: Custom Data Settings Page

  1. In the Create Custom Fields page, define the custom field by entering the details of the same:

    1. Custom Field Name: Enter a name for the custom field.

    2. Custom Field Type: Specify the type of the custom field, e.g., text, number, date, etc.

      1. Integer Number: Values accepting numbers like 1,2,3,-1 etc.
      2. Decimal Decimal: Values accepting decimal number values like 1.1, 45.3
      3. Single Line Text: Text accepting 255 characters
      4. Multi-Line Text: Text accepting 4000 characters
      5. Date: Date format DD/MM/YYYY
      6. Date-Time: Format DD/MM/YYYY - 00:00 AM/PM
      7. File: Formats .txt, .png, etc
      8. Dropdown: Input to be taken from predefined values
      9. True or False: Boolean input radio-button selection
      10. URL: Accepts URL link
      11. Product: Accepts products created on the Fynd Platform
      12. Custom Object: Accepts objects created in custom object section
      13. Custom JSON: Accepted free flow formatted json object

    For example, the following metafield content types and examples can be applied:

    Data TypeDescriptionList InclusionExample
    DecimalThis can be used for numeric values like processor speed or storage capacity.YesAdd the processor speed in GHz for laptops.
    DimensionUtilize this for whole number or decimal values with metric or imperial units.YesInclude screen resolution dimensions for smartphones.
    File ReferenceSupports file uploads for images or documents related to technical specifications.YesAttach images showcasing product features.
    IntegerIdeal for whole number values.YesSpecify the number of cores for a laptop processor.
    JSONSupports raw JSON data for structured information.NoCreate a structured table of technical specifications using JSON.
    Product ReferenceLinks to one or multiple products, suitable for cross-referencing related items.YesLink to related accessories or complementary products.
    Single Line TextPlain text with no line breaks, suitable for concise information.YesProvide a brief description of product features.
    True or FalseCreates a checkbox for a boolean value, useful for indicating product features.NoIndicate whether a device has a fingerprint sensor.
    URLSupports URLs, useful for linking to external resources or reviews.YesLink to detailed technical reviews hosted on specific websites.
    1. Description: Provide a brief description or purpose of the custom field.
    2. Namespace and Slug: These are used for identification and should be unique. The namespace is like a category or group, and the slug is the specific name for the field.


    Figure 2: Custom Field Details

    1. After defining the custom field, you can enter validation details:
      1. Minimum Value: If applicable, set the minimum value that the custom field should accept.
      2. Maximum Value: If applicable, specify the maximum value for the custom field.
      3. Placeholder: Provide a placeholder text that appears in the field to describe the field or to give an example.
      4. Accept Multiple Values: If the custom field can have multiple values, enable this option.
      5. Mark this Field as Mandatory: If the field is required, enable this option to indicate that users must fill it out.

The validation criteria for custom fields may vary depending on the specific custom field type chosen. The previous example is for an integer number, but different field types may have distinct validation requirements.