Theme compatibility and limitations

Inheritance and fallback

Template lookup starts in the selected theme, follows its declared parentTheme chain and finally checks default. Parent themes must be installed; inheritance must not contain a cycle.

Omitting parentTheme does not disable the default fallback. Keep the default package installed, including when your theme supplies every template itself.

A child theme depends on its parent’s templates, markup and scripts. When updating NetSeller or a parent theme, review your overrides together with the parent changes. The manifest’s version identifies your theme release; it does not declare a supported NetSeller version range.

Data and forms

Fields depend on the page, customer permissions and shop configuration. Check availability flags and optional parents before reading nested values. Use prepared URLs, translated labels and formatted prices. Keep form field names, CSRF inputs and prepared validation messages when changing the markup.

See Shared data and the template reference for individual inputs. Themes must not query the database or call internal application services to fill missing data.

Reference-theme differences

Feature	Behaviour
Reservation expiry notice	The checkout model exposes checkout.reservation.expiresAt without a localized display label. The reference theme omits this notice.
Media custom fields	The reference theme uses a native file input. The browser supplies file-picker text; server-side upload validation still applies.

Updating your theme

Keep your theme in its own package and retain the previous release. Deploy updates to a development or staging shop first. Review pages affected by your overrides, including their empty states, validation messages and mobile presentation, before selecting the release for a live shop.

Follow Install and activate for deployment, cache refresh and rollback.