Data Interoperability: Definition and Examples

Every Monday morning, the finance team at a retail chain spends two hours copying sales figures from the point-of-sale system into a spreadsheet. Then they match those numbers against warehouse stock data, even though the black t-shirt is recorded as “KH-01” at the register and “Plain Black Tee” in the warehouse.

This kind of work looks trivial, but it repeats every week and is easy to get wrong. One wrong number is enough to leave a store out of a bestseller or stuck with stock that rarely sells.

The problem goes well beyond retail. In PwC’s 2026 Digital Trends in Operations Survey of 767 operations and supply chain leaders at US companies, 89% said their technology investments had not fully delivered the expected results, and integration complexity was the reason cited most often.

What Is Data Interoperability?

Data interoperability is the ability of different systems to exchange data, understand what it means, and use it together without manual conversion. It comes down to two things: data can move between systems, and the receiving system understands what the data means.

The term combines “inter” (between) and “operability” (the ability to operate). Literally, it means data can be run and used across different systems.

Picture two people writing letters to each other. If a letter arrives but is written in a language the recipient does not read, the exchange still fails, however smoothly it was delivered. Computer systems work the same way. A point-of-sale app can send sales data to an inventory app, but if one system writes the date as 10/11/2026 and the other uses 2026-11-10, the result can flip between 10 November and 11 October.

That is why data interoperability is not just a matter of technical connections. It also covers agreements on formats, terminology, and rules for using data.

Data Interoperability vs. Data Integration

The two terms are often used interchangeably, but their focus differs. Data integration combines data from many sources into one place. Interoperability makes sure those systems understand each other every time data changes hands.

Moving data from five applications into one data warehouse is integration. Making sure those five applications use the same product codes from the start is interoperability. The two complement each other, because integration without interoperability keeps producing data that has to be cleaned again every time it moves.

The Four Levels of Data Interoperability

Interoperability is not achieved all at once. Organizations climb it step by step, and each level depends on the one below it. If a level is skipped, data usually still moves, but the results are confusing.

Technical Interoperability

At this level, data can already travel from one system to another over an agreed channel. The most common channel is an API, a set of rules that lets one application request or send data to another automatically and securely.

When a customer pays in an online store, for example, an API sends the payment status to the warehouse system and the shipping system at the same time. Goods can be packed within minutes of the payment clearing.

Syntactic Interoperability

At this level, both systems agree on the format and structure of the data, such as JSON, XML, or CSV. Rules for writing dates, numbers, and currencies are also fixed so nothing gets misread.

An e-commerce team, for example, might decide that all prices are written without thousand separators and always carry the currency code IDR. The accounting application then stops reading “1.500” as one point five instead of one thousand five hundred.

Semantic Interoperability

This level makes sure everyone understands the data the same way. The key is a data dictionary (a list of terms, definitions, and column formats) along with metadata that explains where each piece of data comes from and what it means.

A sales team might count an “active customer” as anyone who has bought this year, while the finance team counts only buyers from the last three months. Once the dictionary is agreed, both teams read the same number.

Organizational Interoperability

At the highest level, data policies and governance are aligned across teams or companies. Governance decides who owns the data, who may view and change it, and what the security rules are.

Salary data, for example, can be read only by HR and finance, while stock data is open to every branch. Industry standards such as FHIR in healthcare or EDI for business-to-business documents help align these rules across organizations.

Data Interoperability Under Indonesian Regulation

In Indonesia, data interoperability has a legal definition. Presidential Regulation No. 39 of 2019 on One Data Indonesiadescribes it as the ability of data to be shared and reused across electronic systems that interact with each other.

Its implementing rule, Minister of Communication and Informatics Regulation No. 1 of 2023, governs data interoperability within the Electronic-Based Government System (SPBE) and One Data Indonesia. There, the term is defined as the ability of electronic systems with different characteristics to share data in an integrated way.

The same presidential regulation requires data produced by central and regional agencies to meet data standards, carry metadata, follow interoperability rules, and use reference codes and master data. Two municipal offices in the same city, for example, need to write region codes the same way so their data can be combined.

These rules are aimed at government agencies. Private companies that regularly exchange data with agencies can use them as a reference when designing their own data formats and terminology.

Characteristics of Interoperable Data

From the outside, interoperable data can be recognized by four signs. Treat them as a simple checklist.

• Readable by other systems without manual conversion. An order file from the online store is read directly by the warehouse system, with no cleanup in a spreadsheet first.
• Clear metadata. Each piece of data comes with its source, update date, and column meanings. A “status” column, for example, is explained as holding paid or unpaid.
• Combinable with other data. Product codes in sales data and stock data are identical, so “KH-01” no longer has to be guessed as “Plain Black Tee”.
• Traceable in origin and changes. A record of who changed what is kept, so price change history stays visible when another system receives the data.

Why Data Interoperability Matters

Without shared rules, data scattered across many applications causes small, recurring disruptions that get more expensive as the business grows. Each disruption has a matching benefit once systems understand each other.

• Decisions. Without interoperability, reports are compiled by hand, so the numbers are stale by the time they reach management. A promotion gets approved based on last week’s stock when the item sold out yesterday. With interoperability, the sales team can see warehouse stock directly before promising a delivery date.
• Labor. Staff copy and match the same data again and again, like the admin who moves marketplace orders into the accounting system every day. When data flows automatically, their time shifts to work that needs judgment, and the admin only reviews a report that has filled itself in.
• Customers. When the CRM and the shipping system hold different addresses, parcels go astray. With synchronized data, errors like this disappear before they reach the customer.
• Automation and AI. A production scheduling system that cannot read the latest stock data produces a schedule that does not match the warehouse. Consistent data lets automation and AI work from correct numbers, and data that was locked in one application can be analyzed together, such as customer complaints combined with purchase history to find products that often cause problems.
• Audits. When history is spread across systems, auditors wait for files from three departments before they can examine a single transaction. When data movement is recorded cleanly, the approval history for a transaction can be pulled from one flow.

Common Obstacles When Implementing Data Interoperability

A tidy plan on paper almost always hits obstacles in the field. These are the four that come up most often.

Legacy systems with outdated formats. Old systems often have no API and can only export text files. The fix is to place a translation layer in the middle while planning a gradual replacement. A small script, for example, can convert the old register’s CSV file into JSON every night before sending it to the new application. The old register stays in use without having to be replaced now.

Data that is not clean. Sending dirty data to another system only moves the problem. Remove duplicates, empty fields, and inconsistent spellings before opening a channel for exchange. A customer recorded three times under different spellings and billed three times, for example, should be merged into one record first.

Team habits that are hard to change. Teams used to passing Excel sheets over WhatsApp need a clear reason to switch. Appoint one data owner in each division, then have that person show how many working hours were saved once the weekly report filled itself in. Evidence like this persuades better than a reminder.

Limited budget and priorities. Fixing every system at once is rarely realistic. Start by mapping the data sources, who owns them, and where the data flows, then pick the one flow that causes the most trouble. A clinic, for example, found patient data being rewritten three times at registration, the examination room, and the cashier. One digital form was enough to remove two of those rewrites.

Examples of Data Interoperability Across Industries

The principle is the same in many sectors; only the shape of the data differs.

The pattern is the same in all five sectors: people no longer have to rewrite the same data by hand.

Conclusion

Data interoperability is the ability of systems to exchange data and understand its meaning without manual intervention. The results show up quickly: reports finish faster and input errors drop.

It does not have to be rolled out all at once. Start with the one flow that causes the most trouble, then move up to the next level as needs grow.

FAQ

What is data interoperability? Data interoperability is the ability of different systems to exchange data and understand its meaning without manual conversion.

What is the difference between data interoperability and data integration? Data integration combines data from many sources into one place, while interoperability makes sure systems understand each other every time data is exchanged.

What are the levels of data interoperability? There are four levels: technical, syntactic, semantic, and organizational. Each higher level depends on the one below it.

FAQ