Cover: archived official product-page screenshot; capture date not independently confirmed.

Portable-power shoppers do not all enter a store with the same vocabulary. One person searches for a specific battery; another wants backup for a home and has not selected the equipment. On the Jackery US site, the visible navigation separates product type from scenario and offers an additional comparison route. These are observations of the US storefront on 17 November 2026, not evidence of the brand's internal data model, Shopify plan or conversion performance.

Build navigation around the customer's starting question

The product-type path is useful when a shopper knows the category: a power station, solar panel, battery pack or accessory. The scenario path begins with the job, such as home backup or outdoor use. On the reviewed site, the home-backup navigation also names different solution levels. The two paths serve different intents; neither should imply that every item in a scenario is automatically compatible with every other item.

For a Shopify implementation, use navigable collections or landing pages for both entry points, and then let a product detail page explain the specific model and its options. Maintain the relationships behind the page rather than pasting the same long list into every menu. Where a package is selected, identify its actual included products and conditions from the real catalog.

Put a boundary around scenario copy

Scenarios are a discovery aid, not an engineering guarantee. For example, a claimed transfer time alone does not establish that a particular medical device will operate uninterrupted. Do not use scenario tags as a compatibility engine or extrapolate a US product's price and service terms to the UK. Let the exact product, applicable region and current manufacturer documentation govern the content.

Translate names and service promises into decisions

The reviewed navigation contains both HomePower and Explorer names and several version suffixes. A customer may reasonably need help working out whether two names denote the same product, a newer version, or a different kit. An interface can put the full model name beside a short plain-language purpose, and provide a structured comparison of what the buyer receives. The potential confusion is a design hypothesis; the page alone does not show how many customers are confused.

Warranty and membership language also needs its own place in the information hierarchy. The site presents membership benefits and separately lists extended-warranty products. A merchant should distinguish the included warranty, optional paid coverage, eligibility and regional terms, and link to the current policy. Do not promise identical coverage across countries or assume that a membership benefit applies to every purchase.

When an existing customer adds a solar panel or cable, preserve the exact model and generation in the source record. A context-specific link to the relevant accessory can be useful, but the linked item's availability and the manufacturer's compatibility guidance still require checking.

A small Liquid display layer

The sample uses a product metafield custom.purchase_guide referencing a metaobject containing scenario_notes, model_notes and accessory_notes. Each is a merchant-verified multi-line text field. This keeps the scenario, the model and any accessory conditions separate; it does not implement navigation, a selector, purchase logic or compatibility checks.

{%- comment -%} Information display example; not production-ready. Display merchant-verified text only. This does not determine compatibility, electrical safety, medical suitability, inventory, delivery, or runtime. {%- endcomment -%} {%- assign guide = product.metafields.custom.purchase_guide.value -%} {%- if guide != blank -%} {%- assign scenario_notes = guide.scenario_notes.value -%} {%- assign model_notes = guide.model_notes.value -%} {%- assign accessory_notes = guide.accessory_notes.value -%} {%- if scenario_notes != blank or model_notes != blank or accessory_notes != blank -%} <section class="purchase-guide" aria-label="Product information"> <h2>{{ product.title | escape }}</h2> {%- if scenario_notes != blank %} <div class="purchase-guide__item"> <h3>Use cases</h3> <p>{{ scenario_notes | escape | newline_to_br }}</p> </div> {%- endif %} {%- if model_notes != blank %} <div class="purchase-guide__item"> <h3>Model and options</h3> <p>{{ model_notes | escape | newline_to_br }}</p> </div> {%- endif %} {%- if accessory_notes != blank %} <div class="purchase-guide__item"> <h3>Accessories and conditions</h3> <p>{{ accessory_notes | escape | newline_to_br }}</p> </div> {%- endif %} </section> {%- endif -%} {%- endif -%} 

Implementation boundaries and tests

The code is an information-display example, not an install-ready production component. It does not evaluate electrical compatibility, calculate runtime, verify certifications, check inventory, promise shipping or create a working configuration flow. Populate fields only after checking the specific model, market and manufacturer documentation. Shopify's admin or an app must create the definitions first; Liquid does not create metafields.

In a development theme, verify a missing reference, an empty entry, every field by itself and a fully populated entry. Empty values must not create empty headings or false defaults. Test special characters, line breaks, narrow screens, keyboard navigation and the theme's heading hierarchy. Verify actual availability, variant behavior and checkout with the real store integrations. No Shopify production-theme, checkout or physical-product test is claimed here.

The example assumes the reference is rendered in the correct template, that its metaobject has the named multi-line plain-text fields, and that the merchant has made the entry available to the storefront. escape treats content as text; newline_to_br retains its line breaks. See Shopify's metafield and metaobject documentation.

How to evaluate the design

Ask a test participant to reach an appropriate product once from a category and once from a situation. Then ask them what is included and which requirements they still need to check. Look for wrong turns and missing context; do not infer conversion gains without measured evidence. Preserve the manufacturer's terms when describing what a package includes.

Source: Jackery US HomePower product page. Its navigation and commercial details can change.