{"title":"Register - Liquid Object Reference","slug":"register-liquid-object-reference","url":"https://support.storeconnect.com/articles/register-liquid-object-reference","url_markdown":"https://support.storeconnect.com/articles/register-liquid-object-reference.md","subtitle":null,"summary":"The Register object exposes a POS register to Liquid templates. It is available via current_register in POS contexts and from the registers collection on an Outlet.","type":"Developer_Documentation","video_url":"","keywords":"liquid, objects, Register, POS, current_register, template, storeconnect","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"## Description\n\nThe Register object exposes a POS register attached to an [Outlet - Liquid Object Reference](outlet-liquid-object-reference) to Liquid templates. It is available via `current_register` in POS contexts, and via the `registers` collection on an Outlet.\n\n:::note\n`current_register` is available in POS Liquid templates and sync scope filters only. It is not populated in web theme templates.\n:::\n\n## Attributes\n\n| Attribute | Type | Description |\n|-----------|------|-------------|\n| `active?` | Boolean | True if this register is active |\n| `connected?` | Boolean | True if this register is currently connected |\n| `data` | Map | Custom data fields for this register. Access via field API name (e.g. `data.lane_number__c`). |\n| `id` | String | Unique Salesforce ID (sfid) for this register |\n| `sfid` | String | **Deprecated** — use `id` instead |\n| `name` | String | Name of this register |\n| `outlet` | [Outlet - Liquid Object Reference](outlet-liquid-object-reference) | The outlet this register belongs to |\n\n## Boolean attribute convention\n\n`active?` and `connected?` use the Liquid predicate convention (trailing `?`). Use these forms in templates:\n\n\n```liquid\n\n{% if current_register.active? %}Active{% endif %}\n{% if current_register.connected? %}Connected{% endif %}\n```\n\n\nThe bare `active` and `connected` accessors (without `?`) still work but are deprecated and emit a console warning. Use the `?` form in all new templates.\n\n## Custom data\n\nCustom fields defined on the Register Salesforce object are accessible via the `data` map using the field API name:\n\n\n```liquid\n\n{{ current_register.data.lane_number__c }}\n```\n\n\n## Usage\n\n\n```liquid\n\n{{ current_register.name }}\n{% if current_register.connected? %}Connected{% endif %}\n\n{{ current_register.outlet.name }}\n\n{{ current_register.data.lane_number__c }}\n```\n\n\n## Related\n\n- [Outlet - Liquid Object Reference](outlet-liquid-object-reference) — the outlet this register belongs to\n- [Using global Liquid tags](liquid-how-to-global-tags) — global context variables including `current_register`"}