Handle tokens, packages and optional telemetry

This guide describes Fy2Press 1.0.0. Screens can change in later versions, so check the version shown on the Plugins screen before you follow it.

Expected result

Administrators can explain what Fy2Press reads from Shopify, what it stores in WordPress, which optional services are involved and which sensitive data must never enter evidence or page content.

Keep public and private credentials distinct, limit administrator access and understand optional Freemius data flow.

Before you begin

• The version’s product and commercial authority records.
• An inventory of WordPress administrators allowed to manage the connection.
• The Shopify public Storefront token and intended catalog scopes.
• A decision about optional Freemius opt-in and premium licensing.

Plan a way back before you start: a backup or a staging copy, the Shopify product you will compare with, and the WordPress page that should show the result. Start with a small test that you can repeat.

What this covers

The version shown uses a public Storefront token for catalog and cart requests. It does not make WordPress the system of record for customers, orders, payments or checkout, and it sends no plugin-usage telemetry or licensing request directly to Pagup. Some display components can request Shopify data between manual runs. On a merchant site, two first-party cookies retain the cart for seven days: fy2press_cart_ contains an encrypted and authenticated Shopify cart reference (HttpOnly); fy2press_has_cart_ contains only a script-readable 1, with no ID or secret. Both use SameSite=Lax and Secure on HTTPS. Clearing or blocking them may interrupt cart continuity; it does not cancel a Shopify order. An integration can supply optional email or phone fields when creating a cart; those fields pass through WordPress to Shopify. Standard buttons must not be described as automatically collecting them. Conversely, stating that the plugin can never process these fields would be inaccurate.

Remember who does what: Shopify keeps products, inventory, orders, payments and checkout; Fy2Press brings the catalog into WordPress and displays it; WordPress hosts your pages and editorial content. Nothing in this guide moves orders, customers or payments to WordPress.

Steps

1. Document the Shopify store endpoint and confirm that the credential is a public Storefront token.
2. List the WordPress post types, taxonomies and options created or updated by this version.
3. Review the Freemius opt-in and licensing path separately from Shopify catalog requests.
4. Verify that support, logs, screenshots and video contain no token, customer, order, payment or private address data.
5. Test downgrade and uninstall behavior in a test environment before deciding what operational cleanup is acceptable.

Review the result before you share a page publicly. A success message is a good sign, but the public page and the Shopify buying path must agree too.

Check the result

• Catalog records are identifiable as WordPress product posts and taxonomy terms.
• Cart and checkout requests remain associated with Shopify.
• Optional services are described as optional and no public commercial flow is inferred from source configuration.

Check the result where visitors will see it: open the public WordPress page, not only the Fy2Press screen, and compare a representative product with Shopify, including its price, availability, variants and collection. Repeat a small change once to confirm that the behaviour is stable.

Common problems

• A private credential appears in evidence: stop distribution, remove the artifact and rotate the credential when exposure cannot be ruled out.
• A service is contacted unexpectedly: capture the destination and triggering action, then compare it with the documented service boundary.
• Content disappears during lifecycle testing: restore the database and verify the scoped uninstall and non-destructive downgrade contracts.

When something unexpected happens, stop large operations and try again with one product and one page. Keep the exact error message before you change settings or clear caches.

Troubleshooting

1. Confirm the plugin version and edition (FREE or PRO).
2. Reproduce the problem with one test product.
3. Decide whether the issue comes from Shopify, Fy2Press or your WordPress theme.
4. Compare the result with what your edition includes, as described in the edition guide.
5. Restore your test setup, try once more and note whether the result repeats.

Security and data

Apply least privilege to WordPress administration, protect backups and logs, and never treat a public Storefront token as permission to disclose it casually. Public does not mean irrelevant to abuse prevention.

If you ask for help, note the plugin version, the WordPress and PHP versions, your theme or page builder, the page address and the steps you followed. Use test products, and remove tokens, customer data, order details and private addresses from screenshots before sharing them.

Effect on search

Privacy and security choices affect what can be rendered and indexed. Keep private test environments noindex, prevent internal templates from entering sitemaps and ensure public structured data contains no administrative or credential material.

Information for support

If you ask for help, note the plugin version, the WordPress and PHP versions, your theme or page builder, the page address and the steps you followed. Use test products, and remove tokens, customer data, order details and private addresses from screenshots before sharing them.

Related guides

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

Version and availability

Documentation for Fy2Press 1.0.0. The free plugin is available on WordPress.org. PRO is sold separately through Freemius, our licensing and payment provider.