feat(dashboard): Add phone number field to customer list query and search functionality

[TheHypnoo]

Description

After submitting a Feature Request (#4061) and discuss the situation on Discord (https://discord.com/channels/1100672177260478564/1450491606535901204).

I created a PR, including the option to search/filter and display the phone number from the customer section.

Breaking changes

There are no breaking changes.

Screenshots

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview	Jan 12, 2026 3:11pm
vendure-storybook	Ready	Preview, Comment	Jan 12, 2026 3:11pm

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The GraphQL customerListDocument was extended to include the phoneNumber field, and the CustomerListPage search/filter logic was updated to include phoneNumber alongside lastName and emailAddress, enabling search and filtering by customers' phone numbers.

Possibly related issues

• vendure-ecommerce/vendure issue 4061 — Changes add phoneNumber to the customers GraphQL result and include phoneNumber in the CustomerListPage search filter, matching the request to retrieve and filter customers by phone number.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main changes: adding phone number field to customer list query and search functionality.
Description check	✅ Passed	The description follows the template with all major sections completed: clear summary of changes with context, breaking changes statement, screenshots demonstrating the feature, and completed checklist items.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7abe03b and b5a48df.

📒 Files selected for processing (2)

• packages/dashboard/src/app/routes/_authenticated/_customers/customers.graphql.ts
• packages/dashboard/src/app/routes/_authenticated/_customers/customers.tsx

🚧 Files skipped from review as they are similar to previous changes (2)

• packages/dashboard/src/app/routes/_authenticated/_customers/customers.tsx
• packages/dashboard/src/app/routes/_authenticated/_customers/customers.graphql.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[TheHypnoo]

I have read the CLA Document and I hereby sign the CLA

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud