Read builder coverage without assuming parity

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

Separate conceptual component registration from controls, markup and runtime equivalence across Gutenberg, Elementor and WPBakery.

Coverage is conceptual, not behavioral parity. The inventory below identifies which public features have dedicated Elementor, Gutenberg and WPBakery components and which public shortcodes have none. CollectionProductsPerPage is the inverse gap: one component in each builder and no canonical public shortcode.

Before you begin

• Choose the builder that owns the page.
• Check whether the needed capability has a dedicated component or remains shortcode-only.
• Test the rendered output in that builder before claiming equivalence.

Scope and current limits

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.

Coverage is conceptual, not behavioral parity. The inventory below identifies which public features have dedicated Elementor, Gutenberg and WPBakery components and which public shortcodes have none. CollectionProductsPerPage is the inverse gap: one component in each builder and no canonical public shortcode.

Procedure

1. Choose the builder that owns the page. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.
2. Check whether the needed capability has a dedicated component or remains shortcode-only. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.
3. Test the rendered output in that builder before claiming equivalence. Consult the complete version-bound inventory rendered below and test the smallest representative example before reusing it.

Verify the result

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.

• Confirm the exact name or stable ID.
• Compare the declared context with the rendered page.
• Test empty, long and unavailable data states.
• Compare Gutenberg, shortcode, Elementor and WPBakery output only where the coverage matrix declares a component.

Common mistakes

• Do not infer an attribute, block control or builder component from a similar name.
• Do not count builder-only components among public shortcodes.
• Do not describe conceptual coverage as control, markup or behavioral parity.

Troubleshooting

1. Reconfirm the installed package version and edition.
2. Reduce the issue to one component, one known catalog record and one WordPress URL.
3. Compare the exact name, stable ID, context and output with the version-bound inventory below.
4. Identify whether the failing responsibility belongs to Shopify, ShopiPress or WordPress.
5. Preserve the rendered response and settings before changing configuration, then repeat the smallest safe test once.

Security and data

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

Reference components can change headings, links, product data and interactive controls. Inspect rendered semantics, accessibility, canonical behavior and the Shopify buying handoff on a representative page.

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

• Publish with WordPress
• Design and templates
• Google and SEO

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.