Skip to content
digitapulia.com
Fixed-price engagements

Audit of an existing integration

The integration is there, but every week something breaks.
What we do
We analyse the errors, the lost data and the weak points of an integration built by someone else.
How we do it
We start from what you already know: what breaks, when, and what your team does when it happens. Then we read the integration: its code or its configuration, its error logs and the data on both sides. We follow real data from one system to the other and see where they get lost, duplicated or changed on the way, what happens when one of the two systems does not respond, and who finds out when something fails. We write down what we find, each point with its cause, and the plan to repair it, with the price of each repair.
What you receive
A written diagnosis and a repair plan with its prices.
What changes for you
You no longer fight fires blind: the errors we find have a written cause, and the repair has an order and a price before it starts. With the diagnosis in hand you decide whether to repair it with us, with whoever built the integration or with another supplier.
What we need from you
Read access to the integration, to its error logs and to the two systems it connects; the examples of errors your team remembers; and, if it exists, the documentation from whoever built it.
Who it is for
Operations and IT
How you buy it
At a fixed price: the price is written down before we start and we give it to you when you ask.

Example use cases

These are examples: they do not describe a real client.

  • An importer of Italian wines in Mexico, whose online store sends its orders to the ERP

    The situation

    A supplier connected the online store to the ERP and no longer works with the company. Almost every week an order fails to reach the system, and customer service finds out when the customer asks why nothing has arrived. Each time someone copies the order by hand, and no one knows how many have been lost without anyone noticing.

    What we do

    We follow several weeks of orders from the store to the ERP. The ones that get lost have something in common: they carry a product variant the ERP does not recognise, and the integration drops them without telling anyone. We also find the lost orders no one had seen. The diagnosis explains the cause, and the plan proposes two repairs, each with its price: that those orders come in with the right variant, and that any rejected order alerts customer service.

  • A logistics company in Italy with an office in Colombia, whose warehouse system passes its stock movements to the accounting system every night

    The situation

    Every night the integration passes the warehouse movements to the accounting system. When the connection drops halfway, movements that had already gone through show up again the next day, and the accounting team at the Colombian office has to find and delete the duplicates by hand before closing the month.

    What we do

    We read the configuration and the logs of several nights. The integration does not remember how far it got: when it drops, it starts again from the beginning. The diagnosis explains it with the nights when it happened, and the plan proposes the repair with its price: that each movement carries a mark that stops it from going through twice, and that a dropped connection picks up from where it stopped.

Frequently asked questions

Does it work if another supplier built the integration?

Yes, that is what it is for. We read what someone else built from the side of the people who use it, and the diagnosis is yours.

Does the integration have to be rebuilt?

Not always. The diagnosis says, point by point, what can be repaired and what cannot. If a part has to be rebuilt, the plan says so and explains why.

Who carries out the repair?

You decide. The plan is written so that any team can follow it, and it includes the price of each repair if we do it.