Shopify Plus Liquid customisation is not permission to change a theme without boundaries. Advanced theme work should define data ownership, component scope, performance budget, accessibility, localisation, upgrade, and rollback. For a cross-border store, the larger risk is dynamic content changing price, stock, market, language, or pre-checkout information without acceptance.
Theme and data boundaries
Document the responsibility of sections, snippets, templates, metafields, and app blocks. Liquid can present data and conditional logic; sensitive business rules or complex calculations should not be hidden in a template. Dynamic output needs null, access, translation, currency, and market fallbacks so one market does not leak into another.
Performance and upgrades
Record key templates, third-party scripts, media, fonts, and app blocks. Measure page tasks rather than chasing a score outside its environment. Before an upgrade, create a theme copy and diff, then sample browsers and devices for product, price, stock, search, SEO, language, and accessibility regressions.
| Dimension | Define | Evidence |
|---|---|---|
| Component | Section, snippet, block | Template matrix |
| Data | Null, market, language, currency | Variant sample |
| Performance | Script, media, task | Page measure |
| Release | Version, approval, rollback | Theme copy |
SEO and GEO
Theme output should preserve one title, description, canonical, language, and structured-data graph, while visible FAQs answer actual features. State theme, market, component, and upgrade limits; do not promise a perfect score or ranking. Use headless and services as architecture context.
Acceptance
Test home, collection, product, search, cart, market, language, currency, mobile, keyboard, slow network, and theme rollback; record third-party script and app-block effects.
FAQ
Can Liquid implement every business rule?
Do not put all complex, sensitive, or cross-system logic in the theme; separate presentation from system ownership.
What breaks most often in dynamic output?
Null data, market, language, currency, access, and asynchronous states can cause errors or leakage.
What should be backed up before a theme upgrade?
Theme copy, diff, app-block settings, scripts, test samples, and a rollback owner.
How should performance be accepted?
Compare real page tasks across devices, networks, and third-party scripts instead of promising one score.
How does Liquid content support GEO?
Name components, data, markets, languages, upgrade limits, and keep FAQs and structured data aligned with visible facts.