Lookup & Reference
Join Two Tables with INDEX & MATCH (Relational SKU Enrichment & Team Review)
Perform SQL-style left joins between an order transaction log and a SKU master catalog—pulling Category and Unit Price regardless of column order while flagging unmapped SKUs.
Relational left-join mechanics: why INDEX + MATCH survives master-table column insertions
In relational terms, enriching an Orders fact table from a Products dimension table is a Left Outer Join on SKU_ID. Hardcoding VLOOKUP column numbers (2, 3, 4) silently pulls the wrong attribute whenever someone inserts a column into the Products catalog.
Pairing MATCH($B2, $G$2:$G$5, 0) for the row key with MATCH(D$1, $G$1:$I$1, 0) for the attribute header creates a 2D relational join that adapts automatically to reordered columns and flags missing catalog keys explicitly via IFERROR(..., "UNMAPPED_SKU").
| SQL Join Concept | Spreadsheet Equivalent | Unmatched Key Behavior |
|---|---|---|
| LEFT JOIN ON Orders.SKU = Catalog.SKU | MATCH($B2, $G$2:$G$5, 0) | #N/A caught by IFERROR |
| SELECT Catalog.Category, Catalog.Unit_Price | INDEX($G$2:$I$5, row_idx, MATCH(D$1, $G$1:$I$1, 0)) | Header-driven attribute projection |
| WHERE Catalog.SKU IS NULL | COUNTIF(D2:D5, "UNMAPPED_SKU") | Counts orphan order lines |
Header-Driven Two-Table Join Formula
Match SKU_ID down $G$2:$G$5 and match the target column header (D$1 or E$1) across $G$1:$I$1.
=IFERROR(INDEX($G$2:$I$5, MATCH($B2, $G$2:$G$5, 0), MATCH(D$1, $G$1:$I$1, 0)), "UNMAPPED_SKU")Master-Catalog Governance & Owner-Controlled Sharing in Arte Sheets
When merchandising and finance co-edit shared order workbooks in Arte Sheets, analysts can submit new catalog rows via Suggest-mode proposals and @mention catalog stewards in comments, while only the document owner can confirm AI Assistant share_document role changes before external fulfillment partners view the joined schedule.
=SUM(F2:F5)Try the example
Use the original values or change them to test your understanding.