VLOOKUP Formula in Excel With Example

Seeing sample data next to the formula and the result it produces is often the fastest way to understand VLOOKUP. This page lays out a small sample dataset, the exact formula used against it, and what gets returned, so you can compare each part directly against your own spreadsheet.

Once the example is clear, the final section shows the same match performed in Turbo Excel Lookup, for situations where the sample data below is cleaner than what you're actually working with.

Placed in C2 of Sheet1, this formula takes the Customer ID in B2 ("C-204"), searches for it in column A of the Customers sheet, and returns the matching value from column B. The result in C2 is "Daniel Osei". Notice the Customers sheet isn't sorted by Customer ID, which is fine here because FALSE forces an exact match rather than relying on sort order.

Copying this formula into C3 with a locked range (Sheet2!$A:$B) correctly returns "Priya Nair" for Customer ID C-118, demonstrating that the row order in the lookup table doesn't matter for exact-match VLOOKUP.

In Turbo Excel Lookup, this exact scenario is a two-file, single-key lookup: Orders as the Base File, Customers as the Lookup Table, Customer ID matched to Customer ID, with Customer Name ticked as the column to return. The app produces the same C-204 → Daniel Osei and C-118 → Priya Nair results, but also shows a match-rate statistic - useful once your real order sheet has thousands of rows instead of two, some of which may not have a corresponding customer record.

Building on the Orders and Customers example, suppose a third order arrives with Customer ID "C-350", which doesn't exist anywhere in the Customers sheet. Copying the same locked formula into that row returns #N/A rather than a name, correctly signaling that this customer record is missing rather than silently leaving the cell blank or guessing at a value.

This is a useful property of exact-match VLOOKUP - it fails loudly rather than quietly, which is generally the safer behavior for financial or customer-facing data. In Turbo Excel Lookup, the same missing customer would show up in the Unmatched export and be reflected in the match-percentage statistic, making it just as visible but without needing to scroll through the sheet hunting for #N/A manually.

If a formula built the same way as this example still returns unexpected errors on your own data, the most likely causes are hidden characters copied in from another system, a lookup column that isn't actually the leftmost column selected, or a data type mismatch between what looks like the same value in both sheets. Checking these three specific possibilities, in that order, resolves the majority of cases that don't match the clean behavior shown in the example above.

The Customer ID and Customer Name column names used in this example are placeholders - when adapting the same structure to your own data, only the column letters and the col_index_num need to change, while the overall formula shape (lookup_value, locked table_array, column number, FALSE) stays identical regardless of what the columns are actually named. Recognizing this - that the formula's structure is independent of the specific field names involved - makes it much faster to adapt a worked example to a new, unrelated dataset.

A worked example with concrete sample data, checked against the formula's actual output, is the clearest way to confirm a VLOOKUP formula is behaving correctly before applying it to real, larger data. Keep this pattern in mind as a quick sanity check for any new lookup formula you build.