Make Ominity fit your business
Add the details your business needs to its existing records, so your team works with information that reflects the way you operate.
Your business.
Your fields.
Shape Ominity around the way your business works. Extend existing products, customers, and other supported records with your own fields, validation, and relationships.
Available in Content and Commerce
⠿
TitleText
Required⠿
Stock limitNumber
0–999⠿
GalleryMedia
Multiple⠿
BrandRelation
Brands Add a field Text, number, media & more
Built around
the way you work.
Give every value a clear purpose
Choose typed fields and validation for specifications, contact details, media, and relationships.
Use the data across your experiences
Edit values in the admin and deliver the relevant information to your frontend through a configurable API contract.
Extend the records.
Keep the business connected.
Custom fields belong to an existing model. Add the information your team needs directly to the product, customer, or other supported record it describes.
Products
Give your catalog the details buyers need.
- Material
- Organic cotton
- Care instructions
- Wash at 30°C
Customers
Keep the context behind each relationship.
- Industry
- Architecture
- Preferred contact
Other business records
Add the information your supported models need.
- Internal reference
- NS-204
- Supporting file
- Project brief.pdf
The right value.
The right guardrails.
A specification is a number. A contact detail is an email. A connected record is a relation. Choose a field type that expresses what the information actually means.
TextNumberBooleanEmailPhoneMediaRelationJSONColorLink
Set required values, minimum and maximum constraints, and supported patterns so the data stays useful as your team works.
Define a business field
Stock limitA number on the product model
- Type
- Number
- Required
- Yes
- Minimum
- 0
- Maximum
- 999
42 is within the configured range.
Useful in the admin.
Ready for your frontend.
The same field can support your team’s editing workflow and the websites, shops, or apps connected to Ominity.
Decide what the API can do.
Configure the field’s response, write, and filter behavior to match your integration.
- Responses
- Include or omit the field
- Updates
- Allow API edits or keep it read-only
- Write once
- Set a value, then preserve it
- Filtering
- Exact or partial matching
One field. The right language.
Localize the values that need a translation. The API uses the request language and your configured language hierarchy.
EN · DefaultOrganic cotton
NL · TranslationBiologisch katoen
Keep inherited content where it works. Override the value when a language needs something different.
Explore localizationFrom the first step
to a useful result.
Custom fields is part of a connected platform. Here is how it fits into your project.
Extend
Choose the existing model and field type.
Constrain
Set validation and API behavior.
Use
Edit and deliver the value in the right language.
Put it to work
in your next project.
Product specifications
Give product records the specifications, media, and additional information your catalog needs.
Explore solutionsCustomer attributes
Extend the customer record with information specific to your service or business relationship.
Explore solutionsProject-specific data
Connect additional typed values and related records without creating a separate data silo.
Explore solutionsA closer
look.
Talk to us about the capability and the setup your project needs.
Is this the same as a custom content type?
No. A custom content type defines a new structure. Custom fields add information to an existing model.
Can fields be localized?
Localized field values follow the request language and the instance’s language hierarchy when delivered through the API.
Available in Content and Commerce
Check the edition, plan allowances, and any extension requirements for your instance.
Compare plans