"Add us one more field" is the most frequent request store owners make of any platform. One needs fabric composition, another a best-before date, another a lead source. Turboshop answers with custom fields: fields the administrator creates personally, with no developer and no engine update. Here is the full picture: field types, step-by-step creation, checkout, catalog filters, feeds and the API.
What custom fields are and where they live
A custom field is a definition of your own field for one of three entities: product, order or customer. All definitions live in the admin's Custom fields section: the list shows the key, entity, field type and an activity toggle, and the field order changes by drag-and-drop — forms render fields in exactly that order.
Five field types
The type defines both how the field looks in forms and how it behaves in filters and the API:
- Text — an arbitrary string: supplier SKU, a note;
- Number — weight, warranty period, power;
- Date — best-before date, production date;
- Yes/no — a toggle: "fragile", "prescription required";
- Dictionary — a pick from a list of values, tree-shaped included: size chart, color range, product condition.
Creating a field step by step
In "Custom fields" click + Create:
- pick the entity — product, order or customer;
- enter the name — the key is auto-generated from it, and uniqueness is validated with a friendly hint;
- pick the field type (for a dictionary — link the value list);
- optionally set a group — fields are grouped in forms;
- enable the flags you need and save.
An important detail: once created, a field's type and linked dictionary are locked — an accidental type change cannot destroy already-entered values. That is your data protection.
A field is created once — then everyone uses it: managers in forms, shoppers at checkout, catalog filters and product feeds.
Where the fields appear
Product, order and customer cards gain a "Custom fields" tab — available right on the creation form, not only when editing. Filled values are stored with the record and visible to managers.
Order, groups and everyday convenience
Fields are ordered by drag-and-drop, grouped by meaning and rendered in forms exactly that way. The "+ Create" button is always visible above the fields widget, with a quick jump to the section next to it — a new field can be added without leaving the product card. The built-in admin help also has a dedicated custom-fields article with configuration examples.
Custom fields at checkout
Order fields flagged "show at checkout" are visible to the shopper right in the checkout form; a separate flag makes a field required. The store collects the data it needs before any manager call: another carrier's branch number, engraving wishes, delivery time. Required fields are validated as strictly as standard ones — an order cannot be placed without them.
Catalog filters and product feeds
Product custom fields work on the storefront too:
- the "Filter" flag renders the field as a catalog filter group: a dictionary becomes checkboxes, yes/no a toggle, a number a from–to range;
- the "Export" flag sends values into product feeds — Google Merchant, Prom and Rozetka — so marketplaces and product ads receive full attributes.
An end-to-end scenario: from checkout to CRM
Imagine a "Packaging wishes" order field shown at checkout. The shopper fills it in while ordering, the manager sees the value on the order's Custom fields tab, and an integration picks it up through the API along with the rest of the data — it reaches the CRM or accounting system without any manual copying. A field created once works at every stage.
API and accounting-system exchange
Custom field values are served and accepted through the REST API for products, orders and customers, so they work in 1C imports and any integrations — your fields behave exactly like standard ones.
Examples by niche
A few typical setups to borrow ideas from:
- clothing and footwear — a "Fabric composition" text, a "Size chart" dictionary, a size filter in the catalog;
- groceries and cosmetics — a "Best before" date, a "Sugar-free" yes/no toggle;
- electronics — a numeric "Warranty period", a "Condition" (new/used) dictionary with a filter;
- B2B — "Company registration number" and "Payment form" on the customer card;
- operational fields — "Order source", "Third-party carrier tracking number": managers only.
Tips to start
- begin with the two or three fields you genuinely miss daily — add the rest as needed;
- name fields clearly: the key is generated from the name and goes into the API and feeds;
- for attributes shoppers will filter by, pick dictionary, yes/no or number — those are the types that become filters;
- do not flag internal service fields for checkout — shoppers will never see them.
Frequently asked questions
Do I need a developer? No. Everything is created in admin forms within minutes.
Do shoppers see my internal fields? No — only fields with the corresponding flags reach the storefront and checkout; the rest are admin-only.
What happens to values if I disable a field? Data is kept — the field just stops showing; you can enable it back.
Can I change the type of an existing field? No, the type is locked at creation — that protects entered values. Create a new field of the needed type.
Is there a limit on the number of fields? No practical limit, but do not clutter the forms: dozens of fields make managers' work harder.
Summary
Custom fields close the biggest class of "individual customizations" with one standard tool: your own fields, checkout, filters, feeds and API. Follow the platform's progress in the "Updates" rubric — and try custom fields on your own store.