Omnikyo/Help Center
Guide

Metafields (custom fields)

Metafields let you add extra fields to your products — for example "care instructions", "material" or "fit size" — so you can store and show information beyond the standard product fields.

বাংলায়: মেটাফিল্ড হল নিজের সংজ্ঞায়িত করা কাস্টম ফিল্ড যা প্রতিটি প্রোডাক্টে এক্সট্রা তথ্য রাখতে দেয়। যেমন ফেব্রিক টাইপ, কেয়ার ইন্সট্রাকশন বা সাইজ। একবার সংজ্ঞা তৈরি করলে সব প্রোডাক্টে সেই ফিল্ড যোগ করা যায় এবং গ্রাহকদের সামনে দেখানো যায়।

Where to find it: Sidebar › Catalog › select the Metafields tab

What a metafield is

A metafield is an extra field you define once and then fill in on each product. It has a Namespace (a group name like "Custom" or "Details"), a Field Name (the internal key, like care_instructions), a Field Type (text, number, date, color, and 10 others), and optional Validation Rules (min/max length, required date range, and so on).

Once you create a metafield, it appears as a section in the Custom fields card on every product editor. You can fill in different values for each product. If you pin a metafield, shoppers see its value in the specification table on the storefront.

Every metafield belongs to one owner type (the scope). Metafields for Product can store values; those for Variant, Collection, Customer or Order can be created but cannot be filled.

Create a metafield

To add a new custom field:

  1. Open Catalog › Metafields tab.

  2. Select New metafield.

  3. The modal shows five steps:

    1. Basic Information
    • Namespace (required): choose from Custom (your own fields), Details (product specs), Shipping (delivery info), Inventory (warehouse data), SEO (search engine), or Social (marketplace). A tooltip explains each.
    • Field Name (required): use lowercase letters, numbers and underscores only (spaces become underscores). The full key appears below as custom.material_type or details.care_instructions.
    • Description: explain what the field is for (not shown to shoppers).
    1. Field Type — 14 tiles. Choose one:
    • Single Line Text — short text, max 255 characters.
    • Multi Line Text — longer text.
    • Rich Text — formatted text with styling.
    • Integer — whole numbers.
    • Decimal — numbers with decimals.
    • True/False — yes/no toggle.
    • Date — calendar date without time.
    • Date & Time — specific moment.
    • Color — colour picker with hex codes.
    • URL — web link.
    • JSON — structured data (advanced).
    • Dimension — length × width × height with unit (cm, m, mm, in, ft).
    • Weight — weight with unit (kg, g, lb, oz).
    • Rating — star or numeric rating.
    1. Apply To — choose the owner type. For now, only Product fields can store values.

    2. Validation Rules (optional, shown for some types):

    • Single/multi-line text: min and max character count, regex pattern with error message.
    • Integer/Decimal/Rating: min, max, step value. Decimal also: decimal places (precision).
    • Date: earliest and latest allowed date.
    • Dimension/Weight: unit selection (automatically set).
    • Rich Text, True/False, Date & Time, Color, URL, JSON: no validation options.
    1. Advanced Options (click to expand):
    • Pin to top — show this field first in the Custom fields card and first in the storefront specs table.
    • Required — the field must have a value before you can save the product. An amber box shows the warning.
    • Position — a number; lower numbers show first (when not pinned).
  4. Select Create metafield. Toasts show "Metafield created" or an error like Metafield "care_instructions" already exists in namespace "custom".

You must have the Create Products permission to create a metafield.

Fill in custom fields on a product

When at least one metafield is defined for Product owner type:

  1. Open a product editor (Products › click a product).
  2. Scroll to the Custom fields card (below Organisation).
  3. The card shows two groups: Pinned Fields (if any) and Other Fields.
  4. For each field:
    • If it is required, a red badge shows.
    • The input type matches the field type: text box, number spinner, date picker, colour picker, stars for rating, weight with unit dropdown, dimension with three boxes and unit, and so on.
    • Hover over the field name and select the X button to Clear value (removes the filled-in value).
  5. Select Save. If a required field is empty, red text says "This field is required" and saving fails.

In the Bulk editor (Products › Bulk editor), each metafield appears as a column so you can edit values for many products at once.

The interface only saves non-empty values. If you clear a field and save, the old value stays in the database (the clear action does not delete it).

Pinned fields on the storefront

When you pin a metafield, its value appears to shoppers as a row in the Specifications table on the product description block (if the block setting Show specifications is enabled). The rows are ordered by the metafield Position number (lowest first). Up to 50 pinned fields can appear.

Unpinned fields are never shown to shoppers.

Edit or delete a metafield

To edit a metafield:

  1. Open Catalog › Metafields.
  2. Find the field and select Edit (the pencil icon).
  3. Change any field except the Namespace and Field Name (the full key cannot change after creation). You can update field type, validation rules, description, flags and position.
  4. Select Save changes. Toast shows "Metafield updated".

If you edit the Field Type (for example from Single Line Text to Integer), the old values are preserved but may not display correctly until products are re-saved with the new type.

To delete a metafield:

  1. Open Catalog › Metafields.
  2. Find the field and select the trash icon.
  3. Confirm: Delete this metafield? — "Values stored in it on every product are removed too." → Delete.
  4. The server refuses deletion if any product has a value stored in this field. You must first clear the value from every product, then try again. Toast: Cannot delete metafield — "Cannot delete metafield definition that has values. Delete the values first."

You must have the Delete Products permission to delete a metafield.

Metafield field types and validation rules

Every field type has different input behaviour and validation options available:

Field TypeInputMax charsValidationNotes
Single Line TextText box255Min/max length, regex pattern + error messageFor names, SKUs, codes
Multi Line TextLarger text boxunlimitedMin/max lengthFor longer descriptions
Rich TextEditor with bold, italic, linksunlimitednoneFor formatted content; not validated on input
IntegerNumber spinner—Min, max, stepWhole numbers only
DecimalNumber box—Min, max, precision (1–4 decimals), stepFor measurements and prices
True/FalseToggle (Yes/No switch)—noneBoolean on/off
DateDate picker—Min date, max dateCalendar date, no time
Date & TimeDate and time picker—noneSpecific moment
ColorColour picker7 (hex)noneHex colour codes
URLURL text box2048+noneWeb link or file path; not validated on input
JSONText editor (monospace)unlimitednoneFor structured data; not validated on input
DimensionThree boxes (L, W, H) + unit—Unit: cm, m, mm, in, ftLength × width × height in chosen unit
WeightNumber + unit dropdown—Unit: kg, g, lb, ozWeight in chosen unit
RatingStar picker (1–5 or 1–10)—Min, max (e.g., 1–10 stars), stepInteractive star rating

Validation rules are stored but not enforced when you enter values in the product editor — only the Required flag stops a save.

Questions people ask

Can I rename a metafield?

The namespace and field name cannot be changed after creation. The full key (namespace + name) is permanent. You can change the Description, Field Type, Validation Rules, Pin, Required flag and Position, but not the identity.

Can I delete a metafield?

Only if no product has a value in that field. Clear the value from every product first (or bulk-edit to empty), then delete the definition. There is no bulk "delete all values" action — you must clear each product individually or use the bulk editor.

Do shoppers see all custom fields?

No. Only pinned product metafields appear on the storefront, in the specifications table. Unpinned fields are stored but hidden from customers.

Why are collections, customers and orders listed?

Metafield definitions can be created for these owner types, but the dashboard has no form to fill in their values and the server refuses to store them. Only product metafields are usable today.

Other ways people ask this

  • custom field kinboo
  • metafield create korbo kivabe
  • বিশেষ ফিল্ড যোগ করব কীভাবে
  • product e extra information add korbo
  • pinned field dekhabe na keno
  • custom field clear korleo save thakbe
  • validation rule set korbo kivabe
  • product specification dekhate parchhi na keno
  • field type badlate parchhi
  • metafield duplicate hocche error
  • সংজ্ঞায়িত ফিল্ড ডিলিট করতে পারছি না কেন
  • namespace kinbo
  • required field banate hobe
  • field type badlale puran value kemne hobe

Checked against the product on 2026-10-02.