Arcadier allows Item schemas to be extended through structured configuration layers. In a marketplace environment, many listing configurations such as variants, selectable attributes, specifications, and metadata exist as structured attributes attached to the Item entity.
Custom Fields
Custom Fields extend the Item schema beyond standard attributes. They allow marketplace operators to define additional structured fields that merchants must populate during item creation. Since product schemas vary across industries and categories, Item Custom Fields are the primary mechanism for modeling vertical-specific requirements without modifying the core platform schema.
Custom Fields are typically used for:
- Industrial/technical specs (power rating, compatible systems, certifications).
- Service booking metadata (duration units, location rules, lead time, add-ons).
- Compliance and vetting (restricted category flags, document requirements).
Within the Item entity, configurations can therefore be understood as layered attribute storage:
- Core Item properties (Title, Price, etc.)
- Variant attribute tables (generate child Items)
- Custom Fields (structured metadata extensions)
- Custom Tables (advanced relational storage)
These fields are stored as structured attribute records attached to the Item entity and can be retrieved via API for use in search filtering, display logic, or validation workflows.
Custom Tables
Custom Tables provide relational or multi-record storage beyond single-field extensions.They function similarly at the architectural level: structured records associated with an Item, enabling relational storage and controlled data modeling.
Custom Tables are typically used when:
- An Item requires complex, repeatable structured data
- Multiple related attribute records must be stored per Item
- Advanced configuration modeling is required beyond standard variants or Custom Fields
Since Custom Tables operate in a quasi-database manner, they should be used in controlled and well-designed scenarios. They provide flexibility but introduce architectural responsibility.
| Note: Custom Tables operate in a quasi-database manner and are not directly exposed in the UI. Use them in well-designed, controlled scenarios. |