Working with data in Liquid
On this page
The built-in Liquid objects cover the standard StoreConnect data model. When your store holds data in custom fields or custom objects, you have to map that data before a template can read it.
:::note Mapping makes data readable, but for a custom object you defined yourself it does not make the data sync. Those objects also need a record-triggered Flow to push their records to your store. See Sync custom objects using flows. Custom fields on built-in objects sync automatically. :::
These articles cover both halves of that job: making the data available, then confirming it arrived.
In this section
- Add custom data fields to your store — map custom Salesforce fields and objects so Liquid templates can read them
- Verify custom data is available in Liquid — confirm mapped data is reaching your templates, and diagnose it when it is not
- Display dynamic content using Liquid queries — fetch Salesforce records inside a template with the
querytag - Write custom data back from a template — save changes to mapped custom fields with the
updatetag, and the four preconditions that make it fail silently - Copy a custom field from a cart to an order — copy a value such as a gift message from the cart or a cart item onto the order at checkout, on the storefront and at the POS
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.