Should You Replace a System Because Your Team Enters the Same Data Twice

Retyping the same figures between inventory, settlement, and order channels? Check the connection before replacing anything. Three cases.

Digital Transformation··8 min read

Someone reads a figure off the accounting software and types it into the online store's admin screen. Before leaving for the day, someone else emails a spreadsheet to head office. In many companies this routine has run for years. When it becomes a burden, the first thought is usually "do we have to replace everything?"

If a machine can carry the data across those gaps instead, the existing programs can often stay as they are. The three situations below come up repeatedly in this kind of request.

Inventory Between Stores and Head Office

What it looks like today

Each store runs its own inventory program, while head office works from a spreadsheet that consolidates the results. A store employee sends in a stock count after closing, and a head office employee merges the files. By the time head office looks at the numbers, half a day has already passed. A stockout at one store, and surplus sitting unused at another, may not surface until the following day.

What to check before connecting

  • Find out whether the store program offers any way to get inventory data out. Check in this order: is there an API intended for external connections; if not, can the database be opened read-only; and if that is not possible either, can the program export a file at a set time?
  • Check whether item codes match across stores. If one store tracks a product by its manufacturer part number and another uses its own shorthand, a mapping table has to be built before anything is connected.
  • Decide which side's numbers are authoritative. Even with head office as the reference, there must be a rule for when a store counts physical stock and corrects its own figure.

What changes once connected

The retail inventory management system we built follows this structure. Stock that had been scattered across stores was consolidated around head office as the reference point and synchronized in real time. Head office staff now spend their time finding out why a number drifted.

Settlement Between Payment Providers, Banks, and the Ledger

What it looks like today

The settlement statements from the payment provider, the deposit records from the bank, and the accounting ledger each live separately. At month end, an accounting employee lines up all three and matches them one entry at a time. When an amount differs, the cause might be a fee deduction, a cancellation, or a delayed deposit, and each has to be traced. This takes several days.

What to check before connecting

  • Look at the data formats the payment provider and the bank can supply. Some payment providers can deliver settlement details on a schedule, and banks split between file delivery and lookup connections.
  • Confirm whether a shared key ties the three sources together as one record. If a payment or order number appears in all three, matching can be automated; if one lacks it, a separate rule must infer the match from amount and date.
  • Decide who finds out about entries that do not match, and how. Automatic reconciliation will not match every entry. The month-end workload only shrinks when unmatched entries appear in a list and the person in charge can record a reason and resolve each one on a screen.

What changes once connected

The fintech settlement system we built reconciles data from payment providers and banks and closes the daily settlement automatically. Work that piled up at month end is spread across each day, and the person in charge reviews only the entries that did not match.

Multiple Order Channels and Fulfillment

What it looks like today

The company's own site, an online marketplace, and phone orders each arrive through a different screen. Every morning the fulfillment employee downloads the order sheet from each channel, merges them into one, and then creates the shipping labels. Inventory is deducted separately in the warehouse program, so while an order comes in on one channel, the same product can sell on another, and orders occasionally exceed the stock on hand.

What to check before connecting

  • Confirm how each channel makes its orders available. Most sales channels provide an interface for retrieving orders. For phone sales, where a person enters the order, settle on a single entry screen.
  • Settle on one place as the inventory reference. If the warehouse program is the reference, the structure becomes one where each channel's sellable quantity is calculated from the warehouse figure and sent out. With two references, people end up arguing over which is correct after a mismatch.
  • Decide who gets to know when a single order stalls on its way from the channel to the warehouse. Orders do get stuck in the middle, whether from channel maintenance or a product code that does not map, so a notification has to reach the person in charge.

What changes once connected

The morning consolidation disappears, and an incoming order goes straight onto the fulfillment list. Orders exceeding stock become less frequent, because each channel's sellable quantity drops as sales occur.

The Order for Connecting in Stages

In all three situations there is more than one point to connect, and connecting them all at once makes it hard to find the one where the numbers drifted. Start with the connection that takes the most manual effort. Pick one, judging by how many hours a person spends on it each day and how costly a mistake would be. Build that connection first and keep its scope small. Then run it alongside the existing manual process for one to two weeks to confirm that the numbers match. Once they do, stop the manual process and move on to the next. If a problem appears, it is clear where to go back to. The same staged principle is covered in how to modernize a legacy system without replacing it.

When the connected product is updated and its data format changes, the connection breaks. Name who watches each connection and how they are alerted. This overlaps with what we covered in operating a service after launch.

When Replacing Is the Better Choice

Connecting is not always the answer. When a product has no way to release its data at all, or the data it can release does not match the actual unit of the business, the range that a connection can solve is narrow. When the manufacturer has ended support, a replacement schedule has to be set separately. Even then, organizing where data goes in and out gives the new system a path to take over.

Frequently Asked Questions

Q. Our software is old, and we do not even know whether it has integration features. How can we find out?

Product documentation or an inquiry to the manufacturer will answer most of this. If you share the product name and version, we can go through the available routes together in the consultation.

Q. Does the business stop while the connection is being built?

No. The existing manual process stays in place and staff continue working as usual, while the new connection runs beside it and its results are compared. Manual steps are reduced only after the numbers are confirmed to match.

Q. What happens when the numbers drift after the connection is live?

The mismatched entries are passed to the person in charge as a list, and which side's value wins follows a reference rule agreed in advance. Cases that are overwritten automatically are separated from cases a person resolves.

How Integrabbit Looks at Connections First

We at Cokee Corp. work under the name Integrabbit, connecting and improving existing systems. Replacing an existing system means more than the new software. It also means changing familiar routines, migrating data, training staff, and running two systems for a while. So when a request comes in about entering the same numbers twice, we first check whether the product in use can release its data. If a connection solves the problem, we build only that scope; if not, we explain why.

Whether to connect, replace part of the system, or rebuild all of it depends on the current state of the systems and your plans. Which of these fits is a judgment for the client, who knows the company's circumstances best, and our role is to organize the facts that judgment needs.


If you would like to map where figures are being carried by hand between the programs you run today, we can go through it together in the free 30-minute review.

Book a free 30-minute review

Related Posts