Skip to content

feat: add one-click Google merchant search for card expenses#93739

Merged
arosiclair merged 7 commits into
Expensify:mainfrom
samranahm:78486/one-click-merchant-search
Jun 23, 2026
Merged

feat: add one-click Google merchant search for card expenses#93739
arosiclair merged 7 commits into
Expensify:mainfrom
samranahm:78486/one-click-merchant-search

Conversation

@samranahm

@samranahm samranahm commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Add a “Google [merchant name]” link below the merchant field on card-imported expenses in MoneyRequestView, to match Expensify Classic behavior. The link uses the original transaction.merchant recapitalized via Str.recapitalize and opens Google search. It's hidden for non-card expenses and while SmartScan is in progress.

Fixed Issues

$ #78486
PROPOSAL: #78486 (comment)

Tests

  1. Import or create a card expense (company card, personal card import, or Expensify Card.
  2. Open the expense and navigate to the expense details view.
  3. Verify that a "Google [merchant name]" link appears below the "Merchant" field with an external-link icon.
  4. Verify that the merchant name in the link uses proper capitalization to match Expensify Classic behavior
  5. Tap the link and verify it opens a Google search using the capitalized merchant name.
  6. Verify that tapping the link does not navigate to the merchant edit screen.
  7. Edit the merchant name on the same expense, reopen the expense details view, and verify that the Google link still uses the original "transaction merchant rather than the edited display name.
  8. Open a non-card expense (manual, distance, or per diem) and verify that no Google search link is displayed.
  • Verify that no errors appear in the JS console

Offline tests

Same as test

QA Steps

Same as test

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android.Native.mp4
Android: mWeb Chrome
Android.mWeb.Chrome.mp4
iOS: Native
IOS.Native.mp4
iOS: mWeb Safari
IOS.mWeb.Safari.mp4
MacOS: Chrome / Safari
macOS.Chrome.mp4

@samranahm samranahm requested review from a team as code owners June 16, 2026 19:04
@melvin-bot

melvin-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@melvin-bot melvin-bot Bot requested review from flaviadefaria and gijoe0295 and removed request for a team June 16, 2026 19:04
@melvin-bot

melvin-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown

@gijoe0295 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Comment thread src/components/ReportActionItem/MoneyRequestView.tsx Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e99da25c09

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/ReportActionItem/MoneyRequestView.tsx Outdated
@codecov

codecov Bot commented Jun 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 93.84% <ø> (ø)
...c/components/ReportActionItem/MoneyRequestView.tsx 73.09% <87.50%> (+0.38%) ⬆️
... and 9 files with indirect coverage changes

@trjExpensify

Copy link
Copy Markdown
Contributor

Running translations for you.

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 4408a5b2abe..e6e0d613993 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -315,7 +315,7 @@ const translations: TranslationDeepObject<typeof en> = {
         plusMore: ({count}: {count: number}) => `+${count} weitere`,
         merchant: 'Händler',
         googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
-        searchOnGoogle: ({merchant}: {merchant: string}) => `${merchant} bei Google suchen`,
+        searchOnGoogle: ({merchant}: {merchant: string}) => `Suchen Sie ${merchant} auf Google`,
         change: 'Ändern',
         category: 'Kategorie',
         vendor: 'Anbieter',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index d5c7ce89af8..90f65537567 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -270,7 +270,7 @@ const translations: TranslationDeepObject<typeof en> = {
         plusMore: ({count}: {count: number}) => `+${count} más`,
         merchant: 'Comerciante',
         googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
-        searchOnGoogle: ({merchant}: {merchant: string}) => `Buscar ${merchant} en Google`,
+        searchOnGoogle: ({merchant}: {merchant: string}) => `Busca ${merchant} en Google`,
         change: 'Cambio',
         category: 'Categoría',
         vendor: 'Proveedor',
@@ -1755,7 +1755,6 @@ const translations: TranslationDeepObject<typeof en> = {
                 }
             },
             [CONST.NEXT_STEP.MESSAGE_KEY.WAITING_TO_MARK_AS_DONE]: (actor, actorType, _eta, _etaType) => {
-                // eslint-disable-next-line default-case
                 switch (actorType) {
                     case CONST.NEXT_STEP.ACTOR_TYPE.CURRENT_USER:
                         return `Esperando a que <strong>tú</strong> lo marques como listo.`;
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index e981b58c513..917b5a3325f 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1,6 +1,7 @@
 /**
  *   _____                      __         __
  *  / ___/__ ___  ___ _______ _/ /____ ___/ /
+ * / (_ / -_) _ \/ -_) __/ _ \`/ __/ -_) _  /
  * \___/\__/_//_/\__/_/  \_,_/\__/\__/\_,_/
  *
  * This file was automatically generated. Please consider these alternatives before manually editing it:
@@ -864,7 +865,7 @@ const translations: TranslationDeepObject<typeof en> = {
         beginningOfChatHistory: (users: string) => `Cette discussion est avec ${users}.`,
         beginningOfChatHistoryPolicyExpenseChat: (workspaceName: string, submitterDisplayName: string) =>
             `C’est ici que <strong>${submitterDisplayName}</strong> soumettra des dépenses à <strong>${workspaceName}</strong>. Utilisez simplement le bouton +.`,
-        beginningOfChatHistoryPolicyExpenseChatTrack: 'C\u2019est ici que vous suivrez vos dépenses',
+        beginningOfChatHistoryPolicyExpenseChatTrack: 'C’est ici que vous suivrez vos dépenses',
         beginningOfChatHistorySelfDM: 'Ceci est votre espace personnel. Utilisez-le pour vos notes, tâches, brouillons et rappels.',
         beginningOfChatHistorySystemDM: 'Bienvenue ! Procédons à la configuration.',
         chatWithAccountManager: 'Discutez avec votre gestionnaire de compte ici',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 8dfa965c6a8..c6493f22b81 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -315,7 +315,7 @@ const translations: TranslationDeepObject<typeof en> = {
         plusMore: ({count}: {count: number}) => `+${count}件`,
         merchant: '加盟店',
         googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
-        searchOnGoogle: ({merchant}: {merchant: string}) => `Googleで${merchant}を検索`,
+        searchOnGoogle: ({merchant}: {merchant: string}) => `Google で ${merchant} を検索します`,
         change: '変更',
         category: 'カテゴリ',
         vendor: 'ベンダー',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 0e376bf17c4..ef90451f923 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -314,7 +314,7 @@ const translations: TranslationDeepObject<typeof en> = {
         showLess: 'Pokaż mniej',
         plusMore: ({count}: {count: number}) => `+${count} więcej`,
         merchant: 'Sprzedawca',
-        googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
+        googleThisMerchant: ({merchant}: {merchant: string}) => `Wyszukaj w Google: ${merchant}`,
         searchOnGoogle: ({merchant}: {merchant: string}) => `Wyszukaj ${merchant} w Google`,
         change: 'Zmień',
         category: 'Kategoria',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 2fc9ce39a61..95a11d5ad3f 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -315,7 +315,7 @@ const translations: TranslationDeepObject<typeof en> = {
         plusMore: ({count}: {count: number}) => `+${count} mais`,
         merchant: 'Estabelecimento',
         googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
-        searchOnGoogle: ({merchant}: {merchant: string}) => `Pesquisar ${merchant} no Google`,
+        searchOnGoogle: ({merchant}: {merchant: string}) => `Pesquise ${merchant} no Google`,
         change: 'Alterar',
         category: 'Categoria',
         vendor: 'Fornecedor',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 14130787ffd..454321becbb 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -315,7 +315,7 @@ const translations: TranslationDeepObject<typeof en> = {
         plusMore: ({count}: {count: number}) => `+${count}个`,
         merchant: '商户',
         googleThisMerchant: ({merchant}: {merchant: string}) => `Google ${merchant}`,
-        searchOnGoogle: ({merchant}: {merchant: string}) => `在 Google 上搜索${merchant}`,
+        searchOnGoogle: ({merchant}: {merchant: string}) => `在 Google 上搜索 ${merchant}`,
         change: '更改',
         category: '类别',
         vendor: '供应商',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@samranahm

Copy link
Copy Markdown
Contributor Author

Thank a lot @trjExpensify, I'll update the translations shortly.

@trjExpensify

Copy link
Copy Markdown
Contributor

@gijoe0295 - can you jump on the review of this today? We had another customer request for it today.

@gijoe0295

gijoe0295 commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-06-23.at.01.31.08.mov
Android: mWeb Chrome
Screen.Recording.2026-06-23.at.01.28.44.mov
iOS: HybridApp
Screen.Recording.2026-06-23.at.01.20.55.mov
iOS: mWeb Safari
Screen.Recording.2026-06-23.at.01.23.36.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-23.at.01.18.29.mov

Comment thread src/components/ReportActionItem/MoneyRequestView.tsx Outdated
Comment thread src/components/ReportActionItem/MoneyRequestView.tsx Outdated
@gijoe0295

Copy link
Copy Markdown
Contributor

Open a card expense that is still scanning and verify that no Google search link is displayed.

I think this step is hard to reproduce for QA team so please remove it

@samranahm samranahm requested a review from gijoe0295 June 22, 2026 22:59
@samranahm

Copy link
Copy Markdown
Contributor Author

@gijoe0295 All yours.

@gijoe0295 gijoe0295 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@melvin-bot melvin-bot Bot requested a review from arosiclair June 23, 2026 08:41
@arosiclair arosiclair merged commit 7d3ae15 into Expensify:main Jun 23, 2026
35 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @arosiclair has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.4.18-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review complete — docs update needed.

This PR adds a user-facing Google [merchant name] link below the Merchant field on card-imported expenses (company card, imported personal card, or Expensify Card), which opens a Google search for the merchant in a new window. That behavior wasn't documented anywhere in App/docs/articles, so I drafted a help site update.

What I changed: Added a concise FAQ entry to the Edit Expenses article (docs/articles/new-expensify/reports-and-expenses/Edit-Expenses.md) — the article that documents the Merchant field in the expense detail view — explaining where the link appears, what it does, that it uses the originally imported merchant name (even after the displayed merchant is edited), and that it's hidden for manual expenses and while a receipt is scanning. I followed HELP_AUTHORING_GUIDELINES.md, HELPSITE_NAMING_CONVENTIONS.md, and TEMPLATE.md (single # FAQ section, question-based ## heading, link label bolded with exact UI text).

Draft help site PR: #94379 (labeled HelpDot)

⚠️ I couldn't assign the draft PR to samranahm — that account has read-only access on Expensify/App, and GitHub only allows assigning users with triage/write access or higher. I've @-mentioned them in the PR body instead so they're notified.

@samranahm, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.18-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants