A PIM stores a market as “DE.” The commerce platform expects “Germany.” The translation tool wants “de-DE.” One product update needs all three, and a single mismatch keeps the product off the German site. A lookup table solves this. It is a simple table that matches an input value to an output value, so one system’s code becomes the value another system expects.
In integrations, a lookup table keeps those translations in one place instead of inside every workflow.
A lookup table has at least two columns: a key and the value you want back. You give it a key, and it returns the matching row.
The idea is common in computing. Spreadsheet users know it through VLOOKUP, and database teams use reference tables the same way. In integration work, lookup tables usually store:
Some teams call these mapping tables, crosswalk tables or reference tables. All of these names describe the same job.
A market lookup table might look like this:
| PIM market code | Commerce site | Locale | Currency |
| DE | Germany | de-DE | EUR |
| FR | France | fr-FR | EUR |
| GB | United Kingdom | en-GB | GBP |
| US | United States | en-US | USD |
When a product update arrives with the market “FR,” the flow looks up that row. It gets the site name, locale and currency in one step. The two-letter codes follow ISO 3166, the international standard for country codes, which makes them a safe shared key.
A second common example is an ID crosswalk:
| SKU | DAM asset ID | Commerce product ID |
| SKU-1042 | A-88213 | 550193 |
| SKU-1043 | A-88240 | 550207 |
This links one product across three systems. A product page update or an AI tagging flow can then find the right record in each one.
Teams usually translate values between systems in one of three ways.
| Approach | How it works | Main drawback |
| Hardcoded rules | Values are written into each flow or script | Every change means editing every flow |
| Lookup table | One shared table that every flow reads | Needs an owner who keeps it current |
| Master data platform | Values are managed in a full MDM system | More cost and setup than most integrations need |
Most teams start with hardcoded rules because they are quick to build. The cost shows up later. When a new market launches or a category is renamed, someone has to find every place the value lives. A shared lookup table turns that search into one edit.
Lookup tables are also a building block of wider metadata work. Metadata Management Across DAM, PIM and CMS shows how one maintained table keeps fields aligned across platforms.
A few habits keep lookup tables reliable as they grow.
In OneTeg, lookup tables live in the built-in Data Store. You create a table in the browser, add fields such as text, number or single-select, and mark the key column as a unique key. Large tables can be filled with a CSV import of up to 2 GB, and about 1 million rows load in roughly 13 seconds.
Any flow can use the table without a connection. Add a Data Store step, choose the Lookup row action, and set the field and value to match. The step returns the matching row. If there is no match, it returns an empty result instead of an error, so the flow can branch to a review path.
On large tables, a database index on the key field keeps lookups fast. Owners can share a table with other organizations at Read level, so a central team controls the values while other teams use them. The Data Store user manual walks through each step.
For the bigger picture, Why AI Automations Need a Built-In Data Store explains how lookup tables fit next to state and mappings.
A lookup table is a table that returns an output value for a given input key. In integrations, it translates codes, IDs and labels so one system’s values match what another system expects.
The terms are often used for the same thing. A mapping table usually links fields or values across systems, and a lookup table is the table a flow queries to get the translated value.
A crosswalk table links the identifiers one record has in different systems, such as a product’s SKU, DAM asset ID and commerce product ID.
That depends on the rule you set. Good practice is to send the record for review or stop the run, so a missing value never passes through silently.
Store them where every flow can read them and where the owners can update them easily. A data store built into the integration platform keeps them next to the flows, with no separate database to manage.
A lookup table is one of the simplest ways to keep integrations accurate. It turns scattered rules into one shared source, lets business owners keep values current and gives AI tools clean labels to work with.
Contact us to schedule a OneTeg demo and see how lookup tables in the OneTeg Data Store keep your integrations consistent.