Shape products and collections

This guide applies to the ShopiPress version identified in the page header, officially published on Freemius. Confirm the installed version before applying the procedure. Later versions may change screens, defaults or service boundaries.

Expected result

Product and collection presentation uses the included FREE design workshop or the delivered PRO visual-design controls without changing Shopify’s responsibility for commerce.

Use the included visual workshop, default templates and delivered Pro controls without confusing preview locks with active engines.

Before you begin

• Representative synchronized products with images, long titles, prices, variants and availability states.
• A known WordPress theme and target page widths.
• The edition capability reference for the installed FREE or PRO package.
• A rollback point for design settings before making broad changes.

Prepare a rollback point and identify the authoritative Shopify record and the WordPress URL or administration surface that will prove the result. The test should be small enough to repeat without creating ambiguous catalog state.

Scope and current limits

FREE exposes a basic global product and collection workshop with preview. PRO adds the advanced editor, component customization, responsive controls, multiple templates and custom CSS. Saved presets and settings import or export are absent.

Keep the responsibility model visible throughout the task: Shopify remains the commercial source and checkout system; ShopiPress connects, synchronizes and renders the catalog according to delivered contracts; WordPress owns the publishing context. A successful WordPress result must not be interpreted as a transfer of orders, customers, payments or inventory authority.

Procedure

1. Open Design and select the product or collection surface you intend to change.
2. Adjust only a small set of global controls, then compare the preview with representative catalog data.
3. In PRO, separate component-level and responsive changes so each difference can be reviewed and rolled back.
4. Preview long text, missing images, sale prices, variant controls and out-of-stock states.
5. Publish only after testing the actual WordPress page, not only the Design preview.

Do not skip the review step between an administrative action and public publication. A successful control response is only one layer of evidence; the stored WordPress record, rendered page and Shopify commerce path must agree.

Verify the result

• The product and collection defaults remain usable without PRO controls.
• Responsive changes preserve reading order, focus and buying actions at 320 pixels.
• A downgrade does not delete saved PRO settings or catalog content.

Verify the result in the rendered WordPress page and in the authoritative Shopify surface, not only inside the ShopiPress administration screen. Use a representative product with price, availability, variant and collection data. Repeat the smallest safe operation when idempotence matters, and record any difference before broadening the test.

Common mistakes

• Preview and frontend differ: identify whether the theme, builder renderer or saved design setting owns the mismatch.
• A PRO control appears locked in FREE: treat it as contextual product information, not an active engine.
• Layout breaks on mobile: return to global defaults, then reintroduce changes one component and breakpoint at a time.

When a result is unexpected, stop broad actions and reduce the case to one record, one URL and one renderer. Preserve the failing response before changing settings or clearing caches so the diagnosis remains reproducible.

Troubleshooting

1. Confirm the package version and edition.
2. Reproduce the smallest safe case with controlled data.
3. Identify whether Shopify, ShopiPress or WordPress owns the failing step.
4. Compare the observed result with the delivered, partial or absent capability state.
5. Restore the test environment, repeat once and record whether the result is stable.

Security and data

Custom CSS is a PRO publishing capability. Limit it to trusted administrators, avoid remote imports and never embed credentials or customer data in styles or templates.

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

SEO consequences

Design can change heading order, text visibility, link labels and layout stability. Validate rendered semantic structure, accessible names and cumulative layout behavior after each template change.

Evidence to record

Record the installed version, edition, WordPress and PHP versions, active builder or SEO integration, exact URL, viewport and the ordered actions that produced the result. Capture only controlled catalog data. Redact the Storefront token, customer data, order information, private domains and any environment secret before an artifact leaves the validation workspace.

Related guides

• Installation
• Publish with WordPress
• Google and SEO
• Security and data

Version and product state

ShopiPress is officially published on Freemius. This guide describes the documented version. Purchase and download links will be added to this site once their destinations are configured.