Otter Pro activation screen omits the Neve Agency plan requirement

[pirate-bot]

Summary

The Otter Pro license screen tells users with Neve Pro installed that a Neve Pro license can activate Otter Pro. Expected behavior is for the eligibility statement to identify the qualifying Neve plan. The current statement does not disclose that only the Agency plan is eligible, so users on other Neve Pro plans can reasonably expect their keys to work.

Customer context

• Product / area: Otter Pro license activation screen
• Version: Customer version not provided; the statement is present in inspected Otter Pro 3.2.3 source
• Environment: WordPress with Neve Pro and Otter Pro installed
• Integration / third party: Neve Pro licensing
• Reported error / symptom: The screen states that a Neve Pro license can activate Otter Pro, while a Neve Pro Personal key is not eligible
• Impact: Eligible-plan requirements are unclear during activation

Reproduction notes

1. Install and activate Otter Pro and Neve Pro.
2. Open the Otter Pro license activation panel.
3. Observe the statement that a Neve Pro license can activate Otter Pro.
4. Reproduction is source-confirmed for the display path when NEVE_PRO_VERSION is defined; plan variants were not executed locally.

Diagnosis

Conclusion

The defect is confirmed in current source. The activation screen displays an unrestricted Neve Pro eligibility statement, while the support-confirmed entitlement applies only to Neve Pro Agency. The customer report demonstrates the resulting expectation mismatch.

Where this likely occurs

• User-visible surface: Otter dashboard license activation panel.
• src/dashboard/components/LicenseField.js — LicenseField lines 78–86 renders “Neve Pro license can also be used to activate Otter Pro” whenever hasNevePro is truthy, with no plan qualifier.
• plugins/otter-pro/inc/server/class-dashboard-server.php — Dashboard_Server::apply_dashboard_data() lines 55–70 defines hasNevePro solely from the presence of NEVE_PRO_VERSION; it does not represent the installed Neve license tier.
• Git history: commit 155b15e63983fa5f8fe5ee0b80dafcad4ed6fb86 introduced the statement on 2022-04-30, and it remains present in inspected tag/version v3.2.3.

Engineering notes

The UI condition detects whether Neve Pro code is installed, not whether its license is an Agency entitlement. The inspected path therefore shows the same broad claim for Personal, Business, and Agency installations when NEVE_PRO_VERSION is defined. Actual entitlement validation occurs later through the licensing integration and is outside this display condition.

Test coverage status

No relevant unit or e2e coverage for LicenseField, the Neve eligibility statement, or plan-specific display behavior was found during inspection. The existing dashboard tests inspected by search do not reference this component or text.

What to verify or explore next

• May be worth verifying the activation panel with active Neve Personal, Business, and Agency licenses.
• May be worth checking whether localized or built dashboard assets contain a different statement in distributed packages.
• If reproducible in a release package, checking npm run test:unit and the dashboard e2e surface may establish a regression guard.

Unknowns / follow-up

• The customer’s exact Otter Pro version is unknown.
• The date or version when Agency-only entitlement became the active commercial rule is not established by the inspected repository history.

Confidence

Confidence: 99/100

The current Otter 3.2.3 source contains the reported unrestricted Neve Pro eligibility claim, and its activation endpoint passes SDK errors directly to the UI; the staff response independently confirms that only Agency is eligible and that the displayed error does not explain this restriction. No matching GitHub issue was found.

---

Source: HelpScout #3425841827
Generated by bug-report-triage (ID: bug-report-triage_6a88059c825450.33711998)