Skip to content
dvnt.io

Resources · glossary

System integration

Connecting two systems so they exchange data without retyping it by hand: a shop with a warehouse, a form with a CRM, payments with accounting. The cost usually lies on the side of the system you are connecting to.

Also called
  • system integration
  • API integration
  • software integration
  • data integration
  1. 01

    What the price depends on

    Not on how many fields have to be moved, but on what the other side makes available. A system with documentation and a ready interface connects in days; one without them needs workarounds — exchange files, exports, jobs run overnight — and those are what cause failures later.

  2. 02

    Two questions before the quote

    Does the other system’s vendor have documentation, and does it provide a test environment? Missing either one turns the quote into guesswork, because every detail only comes out during the work.

  3. 03

    What you cannot see at the start

    Request limits, error handling and the question of who fixes the connection when the other side changes its format without warning. An integration is a commitment for years, not a one-off task — and it has to be priced that way.

  4. 04

    When not to integrate

    When ten records a month are moved. Retyping them by hand then takes a few minutes, while a connection has to be maintained, monitored and repaired after every change at the vendor.

In practice

Related terms

  • APIAn agreed way for one system to ask another for data or tell it to do something. APIs are how a shop knows its stock levels and how a website sends a contact to the CRM.
  • WebhookThe reverse of a normal request: the external system notifies yours itself when something happens. That way a payment status shows up instantly, without polling every minute.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.