Critical UX Bug: Primary searched domain shows "available" but price is not displayed

[ekamran]

Title: Critical UX Bug: Primary searched domain shows "available" but price is not displayed

Description:
When searching for a domain using the GoDaddy Reseller plugin, the primary searched domain is correctly marked as "available", but its price is not displayed anywhere in the UI. At the same time, alternative domain suggestions (.xyz, .dev, .work, .io, etc.) display their pricing correctly.

This is a serious UX and conversion issue. The primary searched domain is the most important result and must display its price clearly. Showing availability without pricing prevents users from making a purchase decision and creates confusion.

Example:
Search query: codetrappers.ai

Result:

• Displays: "Congrats, codetrappers.ai is available!"
• Does NOT display: price for codetrappers.ai
• Displays prices correctly for alternative suggestions:
  • codetrappers.xyz – $18.99
  • codetrappers.dev – $18.99
  • codetrappers.work – $12.99
  • codetrappers.io – $76.99
  • codetrappers.tech – $76.99

This behavior is inconsistent and counter-intuitive. The primary searched domain should use the same pricing display logic as alternative domain suggestions.

Steps to reproduce:

1. Install and configure GoDaddy Reseller plugin (v2.2.16)
2. Use the domain search widget on the frontend
3. Search for any available domain (example: codetrappers.ai)
4. Observe the results

Actual behavior:

• Primary searched domain shows as "available"
• Price is NOT displayed
• No Select / Add to Cart option is shown alongside the primary domain
• Alternative domain suggestions display pricing and Select buttons correctly

Expected behavior:

• Primary searched domain must display:
  • Price
  • Select / Add to Cart button
  • Same UI structure as alternative domain suggestions
  • Consistent pricing retrieval and rendering

Impact:
Critical — This directly affects usability and conversion. Users cannot see the price of the domain they searched for, which breaks expected ecommerce behavior and may result in lost sales.

Environment:

• WordPress version: 6.9
• PHP version: 8.4
• Plugin version: 2.2.16
• Browser: Chrome
• Device: Desktop

Screenshot:
(attach screenshot showing codetrappers.ai available without price)

Additional notes:
This appears to be a logic or rendering inconsistency where pricing data is correctly retrieved and displayed for alternative domains but not for the primary searched domain. The primary result must use the same pricing retrieval and rendering mechanism as suggestions.

Priority: Critical
Type: Bug

[cberesford-godaddy]

Hi @ekamran - Thank you for reporting this issue here. We've looked into a potential cause and found the following:

The issue appears to originate in the domain-search npm library godaddy/domain-search rather than in the wp-reseller-store plugin itself.
Key observations:

• The wp-reseller-store plugin renders a container
  with configuration data attributes; the actual UI is rendered by the external domain-search library (currently v4.0.1)
• In the library's Domain.js component, there's a guard clause:

if (domain && listPrice) {
return (<div className="domain-result">...</div>);
}
return(<div></div>);

• If listPrice is falsy, the component returns an empty div.
• The likely scenario is that the GoDaddy Reseller API (/api/v1/domains/{plid}/) returns pricing data for suggestedDomains but not for exactMatchDomain, causing the primary result to render without price or Select button.

Suggested Resolution Path

• Confirm the theory - Inspect the actual API response from /api/v1/domains/{plid}/ to verify whether exactMatchDomain is missing listPrice/salePrice fields
• Determine fix location:
  • If API response is incomplete → Fix in API/backend
  • If API response has data but library doesn't use it → Fix in domain-search library
  • If library needs to make additional call for pricing → Fix in domain-search library
• Implement fix in godaddy/domain-search repo and publish new version
• Update wp-reseller-store to use the fixed library version

We have documented these as fix actions and will be prioritizing a fix for this. We'll keep you posted in this thread with updates. Thanks!