Connect one Shopify store safely

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

One Shopify store is connected with its myshopify.com subdomain and a public Storefront API token. The connection test succeeds without introducing a private Admin API credential.

Use the store subdomain and a public Storefront API token, test the connection and preserve the commerce boundary.

Before you begin

• An existing Shopify store and permission to create or retrieve a public Storefront token.
• A working ShopiPress installation whose candidate identity has already been verified.
• Outbound HTTPS from WordPress to the configured myshopify.com Storefront endpoint.
• No customer, order, payment or private Admin API credential in the test notes.

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

The exact candidate supports one store connection. A successful connection verifies Storefront reachability; it does not prove that every catalog record can be synchronized or that background automation exists.

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. Copy only the store subdomain expected by the field, not an arbitrary URL with paths or query parameters.
2. Enter the public Storefront token. Do not substitute an Admin API access token when a test fails.
3. Choose Test Connection and wait for an explicit success or error response.
4. Save only after the connection test succeeds and the displayed store identity is the one you intended.
5. Move to catalog discovery, inspect its summary and keep the first synchronization manual.

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 Home surface reports the connected store rather than Disconnected.
• Catalog discovery can request the source without exposing the token in rendered pages or screenshots.
• A buying action still resolves through Shopify rather than a WordPress transaction engine.

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

• Unauthorized response: recheck that the token is public, active and associated with the intended storefront.
• Store not found: normalize the myshopify.com subdomain and remove protocols, slashes and unrelated domains.
• Network error: confirm WordPress can perform outbound HTTPS and that a security layer is not blocking the Storefront endpoint.

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

The public token still deserves controlled handling because it scopes storefront access. Do not print it in tickets, screenshots, browser recordings or committed configuration. Restrict ShopiPress administration to trusted roles.

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

Connection changes no canonical decision by itself. Before publishing synchronized products, decide whether Shopify or WordPress is the primary product surface and verify the rendered response rather than relying on a settings label.

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.