Custom Field Levels
Custom fields can be added at three levels:- Collab Level - Per creator-brand relationship
- Drop Level - Per drop/collection
- Product Level - Per product within a drop
Field Types
Text Fields
Short Form (Single Line Text)- Single-line text input
- Suitable for: Tags, labels, short descriptions
- Example:
cc-hero-header
- Multi-line text with formatting
- Suitable for: Descriptions, detailed content
- Example:
cc-cc-ken-long-form
Media Fields
Single Media- One image or video file
- URL string or Media object
- Example:
cc-ken-single-media
- Array of images/videos
- Array of URL strings or Media objects
- Example:
List of ken media
Nested Structures
Objects- Complex nested data
- JSON object structure
- Example: Custom metadata objects
- Lists of values
- Can contain objects or primitives
- Example: Media arrays, tag lists
Naming Conventions
Standard Pattern
Custom fields typically follow this pattern:cc-drop-short-form-2- Drop-level short text field #2cc-product-long-form-2- Product-level long text field #2cc-ken-short-form- Brand-specific fieldcc-hero-header- Semantic naming
Common Prefixes
cc-- CreatorCommerce prefixcc-drop-- Drop-level fieldscc-product-- Product-level fieldscc-creator-drop-product-- Product in drop (metaobject)
Collab-Level Custom Fields
Structure
Collab custom fields are stored in thecustom object:
Access in Liquid
Via Metaobject:Common Collab Fields
| Field | Type | Purpose |
|---|---|---|
cc-hero-header | String | Hero section headline |
cc-logo | Media | Creator/brand logo |
cc-coin | String | Short tagline/coin phrase |
cc-spring-content | Media[] | Seasonal content gallery |
| Brand-specific fields | Various | Brand-customized fields |
Drop-Level Custom Fields
Structure
Drop custom fields stored in drop’scustom object:
Access in Liquid
Via Metaobject JSON:Common Drop Fields
| Field Pattern | Type | Purpose |
|---|---|---|
cc-drop-short-form-{n} | String | Drop tag/label |
cc-drop-long-form-{n} | String | Drop description |
cc-drop-media-{n} | Media/String | Drop featured image |
cc-drop-long-media-{n} | Media[] | Drop gallery |
Product-Level Custom Fields
Structure
Product custom fields exist at two levels:- Enhancement Custom Fields - Creator content about the product
- Product Custom Fields - Product metadata in drop context
Enhancement Custom Fields
Product Custom Fields
Access in Liquid
Via Metaobject JSON:Common Product Fields
| Field Pattern | Type | Purpose |
|---|---|---|
cc-product-short-form-{n} | String | Product tag/note |
cc-product-long-form-{n} | String | Product description |
cc-product-singlemedia-{n} | Media/String | Product media |
cc-product-long-media-{n} | Media[] | Product gallery |
cc-creator-drop-product-enhancement-note | String | Creator’s product note |
Field Access Patterns
Safe Field Access
Always check for field existence:Nested Field Access
For nested structures:Media Field Handling
Handle both URL strings and Media objects:Array Field Iteration
For media arrays and lists:API Field Setting
Creating Collab with Custom Fields
Updating Drop with Custom Fields
Adding Product with Custom Fields
Field Naming Best Practices
1. Use Descriptive Names
2. Include Entity Context
3. Use Consistent Numbering
If you have multiple fields of the same type, number them consistently:cc-drop-short-form-1cc-drop-short-form-2cc-drop-short-form-3
4. Document Field Purposes
Create internal documentation mapping field names to their purposes.Common Patterns
Featured Content Pattern
Media Gallery Pattern
Tag/Label Pattern
Related Documentation
- Data Model Overview - High-level architecture
- Creator & Collab Data Model - Collab structures
- Drops & Products Data Model - Drop structures
- Shopify Integration Data Model - Metaobject fields