Review and synchronize the catalog

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

The current manual run discovers the Shopify catalog, shows a reviewable summary and creates or updates WordPress product posts, collection terms and product-tag terms without claiming scheduled automation.

Discover products, collections and tags, inspect the summary and launch the current manual synchronization workflow.

Before you begin

• A tested Shopify connection and a recoverable WordPress database snapshot.
• Permission to create or update ShopiPress product posts and taxonomies.
• A small validation set whose product, collection, tag, variant and availability values are known.
• A decision about which synchronized content may become public after review.

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

Manual full-catalog synchronization is classified partial. Scheduled jobs, webhooks, queues, resumable runs, multilingual catalog synchronization, media mirroring and metafield or ACF mapping 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. Start discovery and wait for the source summary before writing WordPress records.
2. Compare discovered counts and representative records with the Shopify source.
3. Start the manual synchronization only after the review summary is coherent.
4. Inspect created and updated product posts, collection terms and product-tag terms in WordPress.
5. Run a second controlled synchronization and verify idempotent updates and the documented soft-delete or restore behavior.

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

• A representative product preserves its Shopify identity, handle, variants, price and availability data.
• Collections and product tags resolve to the intended WordPress taxonomies.
• A repeated run updates existing records instead of silently duplicating the catalog.

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

• Discovery is incomplete: stop before writing and investigate Storefront permissions or pagination.
• Counts differ after sync: compare the review summary, WordPress statuses and source records before rerunning.
• A product is missing after deletion or restoration: inspect the soft-delete state and invalidate the relevant cache before concluding the record is lost.

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

Synchronization writes catalog content, not customer or order data. Record evidence using fictional or controlled catalog records and remove tokens from logs and screenshots.

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

New product and taxonomy URLs may enter archives and sitemaps. Keep them unpublished or noindex until canonical source, archive policy, rendered robots, schema and internal-link behavior are verified.

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.