Business software · 3 min read
Software integrations: a small-business checklist
A software integration passes information between systems so staff do not have to copy it manually. Before building one, decide which system owns each field, what triggers a transfer and how failures are handled. The difficult part is often keeping information consistent, not making the first connection.
By Raja Wahab, Co-founder, Fixby Studios · Published · 3 min read
Map the data before choosing a connector
Write down the records involved: contacts, jobs, orders or documents. For each important field, choose its source of truth. If two systems can update the same value, define which change wins and how conflicts are reviewed.
Use stable identifiers rather than names alone. Two customers can share a name, and a company can change its trading name without becoming a new customer.
Confirm what the existing products allow
Ask whether their supported interfaces can read and write the required fields. Check account-plan requirements, usage limits and permission scopes. A product having an API does not prove that every action shown on its screens is available through it.
Test one representative operation before committing to a large integration. Use a test environment or safe sample records rather than experimenting on live orders.
Define failure behaviour
| Event | Behaviour to agree |
|---|---|
| Same update arrives twice | Do not create duplicate records |
| Destination is unavailable | Retry safely and expose unresolved failures |
| Required field is missing | Hold the record for correction |
| Record changes in both tools | Apply a documented conflict rule |
| Access is revoked | Alert the owner and stop unsafe processing |
Do not confuse sent with completed
A request can leave one system without being applied successfully in another. Keep a visible status and enough history to investigate problems without logging unnecessary personal information. Staff need to know whether an item is waiting, complete or needs attention.
For an illustrative job-to-invoice connection, the same completed job should not create a second invoice when a request is retried. Agree how the job identifier is recorded and checked.
Reconcile periodically
Compare totals and a sample of records across both systems. A daily or weekly check may be appropriate depending on the operational risk and volume. The important point is to detect missing updates before a customer does.
Assign an owner
Document who responds to a failed connection, who controls the accounts and how provider changes are monitored. Include renewal costs and handover access in the project. A connection nobody owns can silently return a business to manual copying.
Start with one high-value transfer and expand once its normal and failure paths are understood.
Sources
Raja Wahab is co-founder of Fixby Studios, a Huddersfield studio building websites, SEO, social media and business software for small, owner-managed businesses across West Yorkshire.
Next step
Let's get your business seen.
Get a free Blueprint with a clear plan, honest pricing and no jargon.
Tell us which task takes too much time and we'll assess a focused software or automation project. Business software and automation
Prefer to talk it through? Contact Fixby Studios, email info@fixbystudios.co.uk or call 07737 067552.