Stop retyping. Let your systems work together.
An order shouldn't have to travel through inboxes and spreadsheets. Clear agreements about data and errors are what make a system integration truly useful.
Follow one order through your organisation
Take a fictional wholesaler. A customer orders online, an employee creates the customer in the accounting system and the planning team receives an email with the delivery details. When an address changes, someone has to work out which systems still need updating. An API gives software an agreed way to exchange data. With it you can, for example, pass an order on to your accounting system. The value lies in the whole handover: the right data ends up in the right place and employees can see whether it worked.
Decide which system is the source
If two systems are allowed to change the same data, you need to agree which change counts. For each type of information, record where it is managed. The CRM might lead for contact persons, for example, while the accounting system manages invoice status. Use a fixed identifier to link records; two customers can have the same name. Also agree how to handle empty fields, deleted records and different formats. An empty phone field in one system must not accidentally wipe a correct number in the other.
| Data | Managed in |
|---|---|
| Contact persons | CRM |
| Invoice status | Accounting |
| Linking records | A fixed identifier, not the name |
Choose a pace that suits the work
Not every change needs to be visible everywhere immediately. A daily report may be fine with a scheduled data transfer. For order processing, a faster update can matter. That choice depends on the process and on what the packages involved can do. Check in advance which data is available, which permissions are needed and how many requests a supplier allows. An API in the product description doesn't mean every action you want is supported. Investigate the specific handover before you base your whole way of working on it.
Design the failed handover too
An integration has to cope with a system that is temporarily unreachable or an order missing a required field. Decide which errors may be retried automatically and which need attention first. Prevent a retry from creating the same order twice, for example by checking a fixed order reference. Make visible what is waiting, what has been processed and what has failed. A message like ‘Something went wrong’ doesn't help much. The responsible employee must be able to understand which handover is stuck and what is needed to move on.
| Reference | Status | Details |
|---|---|---|
| ORDER-1041 | Processed | Passed on to accounting. |
| ORDER-1042 | Waiting | Accounting temporarily unreachable. New attempt scheduled. |
| ORDER-1043 | Failed | Required field missing. Needs attention from an employee. |
| ORDER-1041 | Skipped | Repeated attempt recognised by the order reference; not created again. |
What is waiting, what has been processed and what has failed, in one overview. That way the responsible employee sees which handover is stuck.
Give the integration only what it needs
An integration that reads order data doesn't automatically need access to every other part of a package. Determine which actions are needed and set up access rights accordingly, as far as the supplier supports it. Treat access keys like passwords and record who manages and replaces them. Be cautious too about the data you store in error messages. To investigate a failed handover, an order reference is often more useful than a full copy of all customer data.
Start with one handover and an owner
Choose a data flow that happens often and whose result is easy to check. Test with examples of a regular order, a duplicate submission, a change and an incomplete request. Agree who follows up alerts and who maintains the integration when a supplier changes something. Once it is in use, compare the number of manual corrections and the time to processing with the old situation. That shows you where the integration helps and where attention is still needed. Reliable automation gives your team overview, even when not everything runs by itself.
Custom softwareAn extra tab solves a lot. Until nobody knows which version is right and one colleague is holding the entire planning together. How to recognise a process that is ready for better software.
Read article
WebsiteYour visitor doesn't know your business yet. A clear promise, visible proof and a logical next step help far more than a homepage full of big words.
Read article