Dictionary-style objects

What’s New with Dictionary-style Objects

You can now pass structured data directly into Clerk without breaking it into multiple flat fields.

This makes product and category data easier to maintain and far more flexible at render time.

• Send nested objects, arrays, and key-value dictionaries
• Use dictionary-style data in Products and Categories syncs
• Access the data instantly in Liquid-style templates

Key takeaway: Structured data unlocks cleaner syncs and more flexible frontend logic.

What You Can Do with Structured Product Data

Dictionary-style objects shift complexity away from integrations and into reusable data structures.

This enables faster iteration on design and logic without touching your product feed.

• Render complex product attributes dynamically
• Reuse structured data across multiple templates
• Reduce brittle custom fields and naming conventions

Current Limitations to Be Aware Of

Dictionary fields are currently designed for display and logic—not decision-making.

They are ignored by systems that rely on indexed, comparable data.

• Dictionary data does not power filters or facets
• Search ranking ignores dictionary fields
• Merchandising rules and segmentation do not use them

This ensures performance stability while broader support is rolled out.

How to Start Using Dictionary-style Objects

If you already send structured data internally, you can now forward it directly to Clerk.

No schema redesign or flattening required.

• Include dictionary-style objects in your next sync
• Adjust front-end templates to consume the data
• Validate output across product and category views

If you run into edge cases, reach out via Clerk support.

What’s Coming Next

Dictionary-style objects are the foundation for richer data usage across Clerk.

Feedback from early adopters will guide how these fields evolve.

• Expanded support in search and recommendations
• Potential use in segmentation and logic
• Improved tooling around structured data

Your implementation feedback directly shapes the roadmap.

TL;DR

• Clerk now supports dictionary-style objects in product and category syncs
• You can send nested, structured data without flattening
• Data is available immediately in Liquid-style templates
• Dictionary fields are display-only for now
• Early usage helps shape future functionality