From protected ZIP to reviewed storefront output.

Quick start

Use this path when you want a safe first staging preview.

1. Install and activate the protected ZIP.
2. Start the trial deliberately or activate a paid licence.
3. Complete the six setup steps shown below.
4. Preview product, cart, checkout and post-purchase output on staging.
5. Resolve every Review required item before enabling customer output.

Requirements

Confirm the stack before you install.

1. Use a maintained WordPress, WooCommerce and PHP combination.
2. Confirm that WooCommerce pages and permalinks work before adding Notice27.
3. Back up files and database.
4. Use a paired staging site for theme, language, cache and checkout testing.

Keep in mind: The pinned browser evidence uses WordPress 7.0.2, WooCommerce 10.9.4 and PHP 8.2.32. Other combinations require a staging test.

Install the ZIP

Install the protected plugin archive without unpacking it.

1. In WordPress, open Plugins → Add New Plugin → Upload Plugin.
2. Choose notice27-eu-guarantee-2.1.0.zip.
3. Select Install Now, then Activate.
4. Open WooCommerce → EU Guarantee Notice.

Keep in mind: Do not rename files inside the ZIP or copy a download URL into a public page.

Start the free trial

The seven-day trial begins only when you choose to start it.

1. Request the protected installer using only your email address.
2. Install and activate the ZIP on that production site or on one linked staging site.
3. Open WooCommerce → EU Guarantee Notice.
4. Inside the plugin, confirm the production host, read the trial facts and explicitly select Start 7-day trial.

Keep in mind: No card is requested. Downloading, installing, activating or retrying does not start or restart the clock. One eligible production domain can use one trial on one site identity.

Activate a paid licence

Use the key shown in the customer portal after a verified purchase or manual issue.

1. Copy the licence key from the secure delivery or customer portal.
2. Open the Notice27 licence panel.
3. Paste the key and select Activate.
4. Confirm the production and paired staging activations in the portal.

Keep in mind: The key is a secret. Do not place it in screenshots, tickets, source control or public diagnostics.

The six setup steps

These labels match the production plugin exactly.

1. Start the deliberate 7-day trial or activate a paid licence
2. Confirm store, buyer, country, language and catalogue scope
3. Review products, variations, bundles and subscriptions
4. Review GARAN/commercial-guarantee records
5. Review digital-provider and software-update records
6. Preview placements and enable storefront output

Keep in mind: Progress records technical setup only. It is not a legal-compliance score.

Store profile

Record the merchant-controlled facts that guide later review.

1. Confirm the business model and catalogue types.
2. Record target countries and storefront languages.
3. Acknowledge that Notice27 does not decide applicable law.
4. Save the profile, then open product review.

Keep in mind: Common mistake: selecting every EU country when the store only targets a smaller set.

Countries, buyer and channel

Product identity alone does not settle transaction scope.

1. Record the target country.
2. Confirm whether the journey is consumer-facing.
3. Review the sales channel and transaction context.
4. Leave conflicting or missing facts at Review required.

Keep in mind: Notice27 does not infer national-law coverage from an IP address or store currency.

Languages and fallback

Choose how the packaged notice asset is selected.

1. Use automatic language selection or an explicit configured language.
2. Confirm the transaction language.
3. Preview the exact official asset.
4. Test language fallback and unsupported-locale behavior on staging.

Keep in mind: A fallback is a display rule, not a statement that the fallback language satisfies a legal requirement.

Products and variations

Review the item that the shopper can actually buy.

1. Scan the catalogue.
2. Open each product result.
3. Confirm the product class and evidence.
4. For variable products, review variation-specific differences before publishing.

Keep in mind: Common mistake: approving a parent product while one variation has different product or guarantee facts.

Bundles and subscriptions

Treat composed products as explicit line relationships.

1. Confirm the extension and product type on staging.
2. Map each bundle component or subscription line explicitly.
3. Review mixed outcomes rather than copying the container decision.
4. Verify cart and checkout rendering with the extension enabled.

Keep in mind: Extension-defined product types require a staging test; support is not implied by a generic WooCommerce label.

General EU legal-guarantee notice

Use the supplied notice artwork for a reviewed journey.

1. Confirm the product and transaction inputs.
2. Select the packaged language asset.
3. Choose compact, full or off for each supported surface.
4. Preview the official-information link and complete artwork.

Keep in mind: Notice27 does not redraw the official notice or claim that every product automatically needs it.

GARAN / commercial guarantee of durability

Use this only when a producer guarantee makes the separate workflow relevant.

1. Identify the producer and exact product or model.
2. Record duration, countries, languages and evidence.
3. Confirm that the producer made the required information available to the trader.
4. Review qualification inputs and publish only a resolved merchant-confirmed record.

Keep in mind: Notice27 can generate the configured label only from an exact, resolved merchant-confirmed record. It does not decide eligibility, certify a guarantee or turn a retailer promise into GARAN.

Goods with digital elements

Keep the good and its digital dependency in the same reviewed product context.

1. Confirm that the item is a good.
2. Record the digital element relevant to its function.
3. Review provider and update information separately.
4. Keep missing provider or update facts at Review required.

Keep in mind: Common mistake: treating every connected product as digital content or treating every software feature as irrelevant.

Digital content and digital services

Do not apply a consumer-goods conclusion to a different product class.

1. Classify content, service and goods elements separately.
2. Record unresolved or mixed cases.
3. Seek appropriate review for the applicable framework.
4. Enable only outputs supported by the reviewed facts.

Keep in mind: Notice27 makes no broad digital-content or digital-service coverage claim.

Software-update information

Record update information without promising what the evidence does not support.

1. Identify the provider or producer.
2. Record the update period or date representation.
3. Separate security and conformity-related update states.
4. Keep expired, missing or conflicting evidence blocked.

Keep in mind: The workflow records merchant-confirmed information; it does not decide how long updates are legally required.

Placement controls

Configure each supported surface independently.

1. Choose compact, full or off.
2. Select the supported hook or block area.
3. Set a bounded content width.
4. Preview desktop, mobile and no-JavaScript output.

Keep in mind: Do not enable a global placement merely to compensate for an untested theme hook.

Classic and Blocks carts/checkouts

Test the checkout technology your store actually uses.

1. Identify classic shortcode or WooCommerce Block pages.
2. Preview the matching Notice27 placement.
3. Test empty, single-item and mixed carts.
4. Confirm one notice and unobstructed checkout actions.

Keep in mind: Express checkout and heavily customized blocks require their own staging journey.

Order-received output

Show the Notice27 state recorded for the authorised order.

1. Place a fictional staging order.
2. Open the order-received page using the correct order key.
3. Confirm the recorded language and line decisions.
4. Verify that a guessed order identifier reveals nothing.

Keep in mind: The order output is not claimed as a legally sufficient durable-medium delivery.

HTML and plain-text email

Keep both email formats aligned with the recorded order state.

1. Enable only the reviewed Notice27 email output.
2. Send a staging email to an authorised test inbox.
3. Compare HTML and plain-text content.
4. Confirm the protected order-record link and expiry behavior.

Keep in mind: Do not paste customer emails or complete message sources into public support tickets.

Customer account records

Registered customers can revisit their authorised order state.

1. Open My Account → Orders.
2. Select an order owned by the signed-in customer.
3. Review the Notice27 section.
4. Open the protected customer order record when available.

Keep in mind: Guest access uses the WooCommerce order key; account access uses order ownership.

Protected downloads

Download access is purpose-limited and short-lived.

1. Sign in through the customer portal magic link.
2. Choose the entitled release.
3. Use the generated one-time download.
4. Verify the published checksum before archiving the ZIP.

Keep in mind: Never publish the protected URL. An expired link can be regenerated while the entitlement is active.

Signed plugin updates

Notice27 verifies release metadata and the archive checksum.

1. Back up the store.
2. Review the available version in WordPress.
3. Install on staging first.
4. Confirm settings, placements and health after the update.

Keep in mind: A current entitlement is required for protected future releases; a lapsed entitlement does not remotely disable the installed paid version.

Manual-review queue

Use the queue as a work list, not an error to hide.

1. Filter Review required results.
2. Open the recorded blockers.
3. Correct missing or conflicting merchant facts.
4. Re-run the affected preview before enabling output.

Keep in mind: Raw reason codes are diagnostic identifiers. The visible state remains Review required until the underlying facts resolve.

Setup health

Check technical readiness before customer output.

1. Review licence/trial state.
2. Confirm profile, catalogue, advanced records and placements.
3. Resolve stale or invalid records.
4. Recheck after theme, checkout, language or cache changes.

Keep in mind: Health is a technical implementation report, not a compliance certificate.

Reason codes

Use human labels first and codes only for support diagnostics.

1. Read Ready to display, Review required or Not configured.
2. Open Technical details only when troubleshooting.
3. Copy the non-sensitive reason identifier.
4. Explain the observed product and surface in the support request.

Keep in mind: Never include licence keys, order data, customer exports or credentials.

WPML

Defensive WPML language detection exists, but compatibility is not yet independently validated.

1. Configure WPML storefront languages.
2. Choose automatic Notice27 language selection.
3. Preview every active language.
4. Test product, cart, checkout and order language persistence.

Keep in mind: WPML is not a verified Lite 1.0.0 compatibility claim. Independent validation is planned for a later release.

Polylang

Notice27 can follow Polylang language resolution.

1. Configure Polylang languages and translated WooCommerce pages.
2. Choose automatic Notice27 language selection.
3. Preview every active language.
4. Test cart and transaction language persistence.

Keep in mind: Polylang 3.8.7 has been tested for Lite 1.0.0; still verify the exact theme and store combination on staging.

Cache and CDN

Vary cached output by the same context that selects language and product state.

1. Purge page and object caches after configuration.
2. Exclude customer account and protected record routes from public caching.
3. Test language variation and cart fragments.
4. Confirm that no stale notice survives a product decision change.

Keep in mind: Do not cache protected customer records or signed download URLs.

Theme testing

Placement hooks and spacing are theme-dependent.

1. Test with the production theme on staging.
2. Check product form, cart totals, order review and mobile actions.
3. Verify keyboard focus and artwork proportions.
4. Compare with a default theme if a hook is missing.

Keep in mind: Page builders and custom checkout templates require their own staging evidence.

Backup and rollback

Make every rollout reversible.

1. Back up database and wp-content.
2. Record the current plugin version and settings.
3. Update on staging, then production.
4. If needed, restore the prior ZIP and matching database backup.

Keep in mind: Do not delete preserved release archives until the new version has completed the store-specific verification window.

Uninstall and reset

Know whether you are resetting settings or removing data.

1. Export or record settings needed for rollback.
2. Use the plugin reset action only with an authorised administrator nonce.
3. Deactivate before deletion.
4. Confirm the intended retention of order-bound records under your store policy.

Keep in mind: A reset is not a legal retention decision. Keep records required by your store policy and applicable obligations.

Customer portal

Use a magic link instead of another password.

1. Open the customer account page.
2. Request a link for the purchase email.
3. Use the single-use link before it expires.
4. Review plan, entitlement, activations, downloads, transfers and support access.

Keep in mind: The same public response is shown whether or not an account exists.

Support checklist

Send enough technical context without sending secrets.

1. Include Notice27, WordPress, WooCommerce and PHP versions.
2. Name the theme, language plugin, cache/CDN and checkout type.
3. Describe the product, surface, expected result and observed result.
4. Use staging and include only redacted screenshots and non-sensitive diagnostics.

Keep in mind: Never send passwords, API keys, licence keys, complete card data, customer exports, database dumps or private certificates.

Staging and domain pairing

Evaluate first, then pair paid staging with the production site.

1. For the trial, install on one staging site and enter the production domain it represents.
2. For a paid licence, activate the production domain first.
3. Use the recognised staging-domain form for the paid paired site.
4. Keep staging inaccessible to shoppers and search engines.

Keep in mind: The trial stores one production-domain anchor and one staging site identity. A second staging site or reinstall cannot create a new clock.

After entitlement expiry

Separate installed-product behavior from service access.

1. The installed paid plugin remains active.
2. Existing merchant settings remain available.
3. Renew when future protected releases, new activations, transfers or support are needed.
4. Review the current renewal terms and pricing in the portal before choosing to renew.

Keep in mind: The installed paid version keeps working after the included period. An active entitlement is required for future protected releases, new activations, transfers and support.

Troubleshooting sequence

Isolate the smallest failing surface.

1. Check Setup health and the human-readable state.
2. Reproduce on staging with caches purged.
3. Compare classic versus Block checkout and a default theme.
4. Collect non-sensitive diagnostics, then contact support.

Keep in mind: Do not disable security controls, expose wp-admin or make a real purchase just to reproduce a display issue.