The properties

Grouping in Liquid works because every product added from a builder carries identifying properties. They're written when the shopper adds the box to the cart, and every value is plain text. Bundle SKU is the only one a shopper can see; every other name starts with an underscore. This page is the reference; the template pages use them.

The ones you should read

The ones that may or may not be there

These exist for the app's own pricing and merging logic, and which ones a line carries depends on the builder's Show products as individual lines in the cart setting. Read them only as fallbacks, and always guard with != blank.

Getting the bundle's name

No single property always holds the name. A merged box ordered with the current format doesn't carry it on the line at all — the name lives in the app's Cart Transform configuration instead — so templates resolve it in this order:

Each template page implements this chain for you — you don't have to write it yourself.

In the email, Order Printer and theme snippets, a merged box ordered today ends at the fallback. To show its real name in an email, on an invoice or in your theme, map _bundle_builder_id to a name yourself. The builder's ID is the last part of its address in the app. Paste this right after the snippet's _bundle_name lookup, inside the same if block, and use your snippet's own variable names (line and bundle_name in emails, line_item and b_name in Order Printer):

{% case line.properties._bundle_builder_id %}
  {% when "65f1c2a4b3d8e9a1f2c3d4e5" %}{% assign bundle_name = "Coffee Box" %}
  {% when "65f1c2a4b3d8e9a1f2c3d4e6" %}{% assign bundle_name = "Tea Box" %}
{% endcase %}

Reading a property in Liquid

Two syntaxes, both valid. Use the bracket form when the name has a space, like Bundle SKU:

{{ line_item.properties["Bundle SKU"] }}
{{ line_item.properties._bundle_id }}

To print a row's properties yourself, skip the ones you've already displayed in the header, and every property whose name starts with an underscore. A loop over line_item.properties includes those — Dawn filters them with this same first-character check:

{% for property in line_item.properties %}
  {% assign first_char = property.first | slice: 0 %}
  {% unless property.last == blank or first_char == '_' or property.first == 'Bundle SKU' %}
    {{ property.first }}: {{ property.last }}
  {% endunless %}
{% endfor %}