Publish with blocks and shortcodes

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

Synchronized products and collections are placed in WordPress pages with delivered blocks, public shortcodes or supported builders, while every buying path continues to Shopify.

Place synchronized catalog data in Gutenberg, themes and content areas using 17 blocks and 27 prefixed shortcodes.

Before you begin

• At least one verified synchronized product and collection.
• A theme or page template whose content width and typography are known.
• A selected rendering method: Gutenberg, shortcode, Elementor PRO or WPBakery PRO.
• A canonical and indexation decision for the WordPress product surface.

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

Builder presence does not prove identical attributes, controls, markup or output. Eleven public shortcodes have no dedicated component in any of the three builders, and CollectionProductsPerPage is builder-only in the exact candidate.

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. Choose the Add to my pages surface and decide whether a composed product or collection output or granular components fit the page.
2. Insert the delivered Gutenberg block or copy the exact prefixed shortcode into the intended content area.
3. For PRO builders, add the native component and compare its controls with the shortcode or block reference rather than assuming parity.
4. Preview the page at desktop and mobile widths, including variants, availability, price and empty states.
5. Follow the buying action through cart creation and confirm that checkout is hosted by Shopify.

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 rendered product identity and price match the synchronized record.
• The layout works with keyboard navigation and at 320 pixels without horizontal overflow.
• The buying link or cart action points to the intended Shopify commerce path.

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

• Blank granular component: confirm the page supplies the required product or collection context.
• Builder output differs: consult the coverage matrix and test the builder-specific renderer; do not treat conceptual coverage as markup parity.
• Buying fails: verify product and variant identity, the public Storefront connection and the Shopify cart response.

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

Do not paste tokens into page-builder fields or custom HTML. Treat user-provided CSS and builder access as privileged publishing capabilities.

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

Inspect the final URL, headings, internal links, canonical, robots and structured data. A visually correct builder preview is not proof that crawlers receive the intended HTML.

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.