Skip to Content
DocumentationBlocksCustom Liquid

Custom Liquid Block

Use Custom Liquid for store-specific Liquid, markup, embeds, and small integrations that cannot be created with built-in blocks or app blocks.

Setup Order

  1. Confirm a built-in block cannot do itCheck available section, block, and app block options before adding custom code.
  2. Keep the snippet smallUse Custom Liquid for focused output such as a short embed, badge, message, or integration hook.
  3. Use trusted codeOnly add Liquid, HTML, scripts, or embeds from sources you understand and maintain.
  4. Preview the outputCheck desktop, mobile, and the surrounding section so the custom output does not break layout or keyboard access.
  5. Document the purposeKeep a merchant-side note of what the block does and where any external embed or script comes from.

Good Uses

UseWhy it fits
Small trust badgeA compact custom badge or message that does not need a full app.
Store-specific embedA focused third-party embed required by the merchant.
Conditional messageA small Liquid condition tied to product, collection, customer, or market data.
Integration hookA minimal element needed by a trusted app or external service.

Avoid

AvoidReason
Large page layoutsBuilt-in sections, Containers, and content blocks are easier to maintain.
Untested scriptsScripts can affect performance, accessibility, and checkout-adjacent journeys.
Broken markupUnclosed tags can affect surrounding sections.
Duplicated app outputApp blocks are usually easier to manage when an app provides one.

QA Checklist

StateWhat to confirm
Liquid outputThe block renders without Liquid errors.
LayoutThe output does not overflow, overlap, or break nearby blocks.
MobileThe custom output remains usable on small screens.
Keyboard accessAny interactive element can be reached and used with a keyboard.
External embedThe source is trusted and still loads in the target markets.
MaintenanceThe store team understands what the code does and where it is used.