Quick answer
In WooCommerce Subscriptions 9.2, inspect gifting on the individual product rather than looking for the old enabled-for-all default. Check a small selection of existing products and a new product. Do not bulk-enable the entire catalog simply because one product lost its gift option.
Separate the three questions
Start with the shopper complaint. Is the gift option missing before checkout, does the wrong recipient receive access, or can the recipient no longer manage something on My Account? These are different operations. Product eligibility controls whether gifting is offered; account permissions determine what the buyer or recipient can do afterward.
Write down the affected product, its product type, the public URL, the installed Subscriptions version, and whether the complaint also occurs on a standard product template. A custom purchase widget can hide a valid option. Check one ordinary product page before treating the entire database as incorrectly migrated.
Understand the changed default
The 9.2 advisory describes a move to per-product gifting metadata and a bulk-edit control. A background migration preserves the previous enabled-for-all behavior on existing products without an explicit value. Products without a value otherwise default to off. This is a configuration migration, not a reason to expect every future product to inherit the old storewide choice.
Keep a record of what the store intended before updating. If that record is unavailable, ask the merchant which product families should support gifts. Do not infer the commercial policy from whichever product happens to work today. Restricted memberships, physical deliveries, and digital access may have different operational requirements.
Use a three-product sample
Choose an existing product that previously followed the global default, an existing product with a deliberate exception, and a newly created product. Work on staging first, with gateway test mode and contained customer notifications. Record the product IDs, observed settings, and whether the public gift controls appear.
For each example, compare the product editor with the shopper page. When the editor is correct but the page is wrong, test the standard template and relevant page cache. When both are wrong, investigate configuration and migration evidence. These comparisons identify the layer needing attention without an indiscriminate database update.
- Keep the excluded product as an explicit negative test.
- Use fictional buyer and recipient details in the test store.
- Check an uncached visitor session as well as the administrator view.
- Do not assume recipient access implies buyer-level subscription permissions.
Review background work before repeating it
Ask the site maintainer to inspect the update and background-processing evidence for the installed version. Record whether work is pending, failing, or complete. A pending operation and a completed migration with an intentional exception should not receive the same fix.
Avoid repeatedly downgrading and upgrading in an attempt to rerun migration. Also avoid changing serialized options or product metadata in bulk without a reviewed selection and backup. The supported product controls are easier to audit, and the selection itself is often the most important part of the change.
Apply a narrow catalog correction
If the business policy is clear and the correct products are identified, use the supported per-product or bulk-edit controls on a small staging selection. Preserve the before state and review the selected product IDs before applying the operation. Do not rely only on a category name that may contain unrelated products.
Repeat the three-product sample afterward. The positive example should offer gifting, the excluded example should not, and the new product should follow its intended explicit setting. Confirm the resulting buyer and recipient records in the test purchase flow without using a live card or sending a real fulfillment request.
Hand over a usable release record
Document the chosen gifting policy, the affected product set, and the evidence that public behavior matches the editor. Include who is responsible for configuring new subscription products. Otherwise the same question will recur when the next product is added.
After deployment, inspect the first legitimate gift orders through normal operations. Do not manufacture live charges to prove that migration worked. If something differs, preserve the order and recipient evidence, then isolate the affected configuration instead of resetting the entire store.
Illustrative diagnostic worksheet, not results from a customer site.When to bring in help
Ask for WooCommerce troubleshooting support when products disagree with the documented policy after migration. Bring three product IDs, the old storewide setting, and a redacted public-page comparison. That allows a developer to distinguish incomplete migration from a deliberate product override without changing the whole catalog.
Related troubleshooting
Compare subscription versions across your sites.
Helpful references
Subscriptions 9.2 developer advisory.