Duplicate matches

Handle Multiple Lookup Matches for the Same Key

Marcus, a customer success lead, reviews accounts with multiple support tickets and chooses how duplicate matches should appear.

Problem

Marcus prepares a weekly customer health review. The account list has one row per customer, but the support export can have several tickets for the same Customer ID. He needs to decide whether to keep only one ticket, expand every ticket into its own row, or combine values into one cell.

Demo Files

Main file: Customer Health List

Customer ID	Customer Name
C-102	Acme Supply
C-118	Northstar Co
C-204	Bright Labs

Lookup file: Support Ticket Export

Customer ID	Ticket ID	Ticket Status	Created Date
C-102	T-1001	Open	2026-05-01
C-102	T-1004	Closed	2026-05-03
C-118	T-1007	Waiting	2026-05-06

Recommended Options

Use first match when you want VLOOKUP-like behavior.
Use last match when the newest row appears later in the lookup file.
Use expand when every matching lookup row should become its own output row.
Use combine when you want all duplicate values kept in one cell.

Result Preview

Result preview: Expand into multiple rows

Customer ID	Customer Name	Ticket ID	Ticket Status	Created Date
C-102	Acme Supply	T-1001	Open	2026-05-01
C-102	Acme Supply	T-1004	Closed	2026-05-03
C-118	Northstar Co	T-1007	Waiting	2026-05-06
C-204	Bright Labs	No match	No match	No match

What This Shows

Duplicate handling is where SheetMatch is more flexible than a basic VLOOKUP formula.
For Marcus, expand creates a clean review list where each customer stays in place and related tickets appear next to that customer.