Skip to main content
← Back to News
Article13 min readIerum Digital

How to Choose Tools That Integrate and Spot Data Inconsistencies

Online store workspace with invoices, a handwritten order checklist, shipments and calculations.

When you first started selling online, you probably didn't need many tools. A storefront, a payment provider and a way to keep track of orders were enough. Then came more customers, more products and new requirements. You added a system to manage inventory, another for invoicing, and perhaps a CRM to keep your sales conversations organized. Each tool arrived for a good reason: there was something your business needed to handle better at the time.

Over time, keeping everything connected can take more work than expected. An order appears in the store but takes a while to reach the management system. Someone checks invoices, somebody else reconciles inventory, and every now and then the team has to piece together what happened to a particular order. Perhaps this rarely happens in your business, or you've already established a routine that keeps it under control. Either way, when considering a new tool, it's worth asking whether it will make that coordination easier or add another task to your team's day.

The platforms you already use may still be exactly right for your business. Replacing them doesn't have to be the starting point. There are two useful questions to explore: what should you check before adding another service, and how can you tell afterwards whether information is moving correctly between systems?

Before adding a tool: how well will it work with what you already have?

Imagine you're considering an ERP because your catalogue has grown and your inventory spreadsheet is becoming difficult to maintain. You find several products with similar features. One advertises an API and an integration with your ecommerce platform. That sounds promising, but it still leaves important questions open. Perhaps the integration imports products but cannot update stock levels, or transfers new orders without handling returns.

The easiest way to evaluate those differences is to follow a process you already know. When a purchase comes in, your store records the products and payment. Depending on how you operate, stock might be reserved immediately or deducted when the order is prepared. If the customer cancels, the reservation may need to be released. If one product is returned, inventory and the relevant documents might need adjusting. A useful integration must support the processes you've chosen for your business, including the situations that don't follow the happy path.

Start by finding out what the API can actually do

An API lets other software interact with a service through operations defined by its provider. Some APIs let you read information, others let you create or update records, and some offer a narrower set of capabilities. Being able to retrieve an order does not mean you can register a return. Nor does it guarantee that you can store the identifier that the same order uses in your online store.

Before you subscribe, write down the actions you need and compare them with the documentation: retrieving orders and their items, checking status changes, recording transactions in the ERP, updating stock or retrieving an invoice reference.

And if you're already picturing hours spent reading technical documentation, there's some good news: today you can ask an AI agent to review it and compare a platform's capabilities against your requirements. Ask it to show where the documentation supports each conclusion and to flag anything it couldn't verify. You'll know what to ask the provider or test before making a decision.

A missing operation doesn't necessarily rule a product out. There may be a connector, an import process or a reasonable manual step that covers the gap. What matters is how often that situation occurs and how much work it creates.

Two systems can speak the same language and mean different things

You'll probably see formats such as JSON, XML or CSV in the documentation. They matter for transferring information, but the meaning of each field deserves just as much attention. In an online store, “confirmed” might mean payment has cleared; in a warehouse, it might mean someone has accepted the order for picking. One platform may include discounts and shipping in an order total while another represents them separately.

If both applications interpret those fields differently, copying a value can produce a technically valid but commercially incorrect result. That's why it's worth reviewing products and variants, statuses, quantities, taxes, currencies, dates and external references. A test order with a discount or partial return will often tell you more than a demo with one product and an uncomplicated payment.

What happens when an update doesn't arrive?

Some services announce changes through webhooks: notifications another application receives when an event occurs. Others require periodic checks for new information. The approach affects how quickly data is updated and how the system can recover missed changes after a connection interruption.

Imagine your ERP is unavailable for a few minutes while customers continue buying. Before choosing an integration, you should be able to find out how those orders will be recovered, how previously processed orders can be recognized and what usage limits the provider applies. It's also worth understanding how permissions are managed, who can revoke access and whether you can export your data if you eventually decide to switch providers.

You don't need to become an API specialist to ask these questions. If you work with a technical team or supplier, they provide a practical way to understand what you're getting before committing time and money.

What to checkWhat to ask
Access and pricingIs the API included in my plan? Are there restrictions or extra charges?
OperationsCan I read and perform the actions my process requires?
DataAre products, variants, statuses and external references available?
UpdatesHow are changes communicated, and how are missed ones recovered?
SecurityWhat permissions am I granting, and how can I revoke them?
PortabilityCan I export my data and its relationships if I switch providers?

After integration: how can you tell whether the data still matches?

Let's return to our store. The ERP is now in place, products are synchronized and orders are being recorded without manual copying. That saves time, but each sale now follows a path involving several systems. On a busy day, it can be difficult to know whether every order has completed that journey, especially when there are cancelled orders, pending payments or returns.

Consider a fictional transaction, order 18427. A customer bought two items and paid. The store shows a successful payment, the ERP has the corresponding order and inventory reflects a deduction of two units. While preparing an administrative reconciliation, however, someone notices that the invoice can't be found, even though the expected time for issuing it has passed. Nobody necessarily made a manual mistake: every platform might be online while one particular transaction remains incomplete.

SystemWhat we find
Online storeOrder WEB-18427, paid, 2 units
ERPOrder ERP-9362, recorded
InventoryMovement of -2 units
InvoicingNo invoice linked to the order

Illustrative example. We assume an invoice should have been issued and the expected time has elapsed.

Agree on what should have happened first

The missing invoice matters because we expected it to exist at this stage. In another business, or for another type of sale, it might be perfectly normal to issue it later. Inventory is similar: some companies reserve stock when an order is placed, others deduct it when payment clears, and others when goods are shipped.

To find meaningful discrepancies, describe these rules with the people who actually run the operation. At what point should a sale reach the ERP? What happens when a customer cancels? How much time can pass before the next system reflects the change? Clear answers make it possible to distinguish transactions that are still progressing normally from ones that need attention.

Which system should you trust?

That question eventually comes up when two screens show different answers. It depends on the type of information. The store may originate an order, the ERP may be responsible for available inventory, and the invoicing service may hold the authoritative record of issued invoices. Having one place where you can view all this information doesn't necessarily mean that place should control every record.

You may be considering HubSpot to organize customers, opportunities and part of your sales workflow. If it fits the way you operate, it can simplify a great deal. Before moving other processes into it, though, check which functions it actually supports and which are better handled by specialized systems. In some businesses, an internal application can coordinate these relationships; in others, connecting existing platforms is enough. Custom development is an option when the requirements justify it, not a prerequisite for a unified view.

The decision becomes easier when you separate three things: where a record originates, who is allowed to change it and where you need to see it. Those don't always have to be the same place.

Following one sale across its references

In our example, the online store identifies the purchase as WEB-18427 and the ERP records it as ERP-9362. When an invoice is issued, it may receive a reference such as INV-3021. The numbers don't need to match: each platform manages its own identifiers. What matters is retaining the relationship that proves these records belong to the same transaction.

Without those references, someone ends up comparing dates, customer names and amounts to reconstruct what happened. That may work occasionally, but it becomes unreliable when a customer makes two similar purchases or an order is split into multiple shipments. Saving external identifiers or keeping a mapping table makes everyday operations and later audits considerably easier.

Which inconsistencies are worth checking?

Once you know what should happen and how to trace each transaction, you can look for missing records, duplicates and contradictory values. A paid order may never reach the ERP; an inventory movement may be recorded twice; a return may be reflected in the store but not yet in stock.

Some differences are expected. If an event takes a few minutes to travel between systems, a report might temporarily find two different statuses. That's why a useful control checks more than values: it considers when each event occurred, how long the next step may take and when an investigation is warranted.

There are times when those delays matter much more. During events such as Black Friday or Cyber Monday, order volume can rise dramatically within a few hours. An integration that usually handles sales without difficulty might start building up a backlog, while the team answers customer questions, corrects stock and explains cancellations. For many retailers, those days account for a significant share of expected revenue. Well-prepared promotions and advertising offer little consolation if the business struggles to fulfill the orders they generate.

You can often spot the warning signs before they become a crisis. Measure how many orders arrive per minute, how long they take to reach the ERP, how many are waiting, what proportion fail or require retries and how long the team takes to resolve exceptions. If every major campaign brings cancelled orders or customers waiting for answers, look for the stage where work accumulates: checkout, synchronization, inventory, picking and packing, or customer service. Replacing everything is rarely a useful first assumption; understanding the actual limit comes first.

Those measurements can guide load tests, adjustments to order processing, additional capacity or even a more conservative promotion if the operation cannot handle the demand. They also help protect something a sales dashboard may not capture that day: customer trust. A campaign can generate impressive order numbers and still leave people disappointed if too many purchases cannot be fulfilled.

A first check you can make with the tools you already have

You don't need to build an auditing system to get started. Choose ten recent orders, including a cancellation or return, and look for their references in the applications involved. Check whether the expected records exist, whether quantities and amounts follow the agreed rules, whether there are duplicates and whether statuses were updated on time. When you can't determine what happened, note which reference or piece of information is missing.

This review helps reveal genuine difficulties before you invest in a solution. If the work is frequent or time-consuming, the same checks could become a scheduled query, file reconciliation, automation or dashboard. The right choice will depend on your volume and how your team works.

CheckWhat to verify
Missing transactionDid every expected record get created?
Cross-referenceCan the sale be linked to its ERP order and invoice?
Quantities and amountsDo values follow the rules for discounts, reservations and returns?
Status and timingDid the next step occur within the expected window?
DuplicatesDid one action create more movements than intended?

When something doesn't match, reconstruct it before correcting it

Suppose we find that missing invoice. We could try issuing it again, but we still don't know whether the original request never reached the provider, was rejected or succeeded while its response was lost. In the last case, a new attempt without safeguards could create a duplicate.

Operation logs help: identifiers, timestamps, responses and error details. Some providers support idempotency mechanisms so certain retries won't repeat their effects; how those mechanisms work varies by API. For payments and invoices, checking the real status and asking for human review can be safer than automatically repeating the action.

Making better decisions with the systems you already have

If you run your business with several tools today, each is probably there for a reason. You might discover that one integration needs improvement, that a few references should be organized or that a regular check would help. Or perhaps a platform no longer supports the way your business operates and replacing it makes sense. None of those outcomes should be assumed in advance.

The next time you evaluate a service, start by describing what you expect it to do alongside your existing tools and ask to see those operations tested. If your systems are already connected, reviewing a handful of real orders may show you where information gets lost, which differences are normal and which need attention. Both are manageable exercises that help you make decisions with more evidence and less reliance on sales promises.

After all, your reason for bringing those tools into the business hasn't changed: to stay organized, support growth and spend less time on repetitive work. The connections between them should help you achieve that too.

Further reading

  • Integrations
  • ERP
  • Ecommerce
  • Operations
  • Data

Share