A low-cost integration offer can make two business systems appear connected while leaving staff to resolve the awkward parts manually. For an Albany or Great Southern business, the useful question is what work remains before information can move accurately and somebody can act on it.
Use this checklist when comparing an offer to connect systems such as enquiry software, a job list or a stock record. It helps expose preparation, checking and support that may sit outside the headline price. It does not assume that a low-cost offer is unsuitable or that every manual step should be automated.
Check the exact information being connected
- Name the source system and receiving system.
- List the fields and attachments included.
- Identify which direction information moves.
- Ask what happens to existing records.
A statement that two products integrate may describe only a limited function. A connector might transfer a new contact but leave the enquiry history, supporting file and next action behind. Staff then need another way to find the context.
Ask the supplier to demonstrate the specific record your workflow requires, using invented information. A product logo in an integration directory is not evidence that every part of the task is covered.
Check preparation and matching work
- Identify who cleans inconsistent or incomplete records.
- Agree how the same customer or job is recognised.
- Check similar names and duplicate entries.
- Ask who verifies the initial transfer.
Information that looks tidy to a person may still lack a stable reference for matching between systems. If the connection relies on names or free-text descriptions, ask how a changed name or repeated enquiry is handled.
Separate supplier setup from internal preparation. The business may need to approve field meanings, resolve duplicates or decide which record is authoritative. These are real tasks even when they are not separately invoiced.
Check the meaning of transferred status
- Compare status labels in both systems.
- Define which event triggers an update.
- Check whether an update creates a customer message.
- Identify who may approve a consequential change.
Received, accepted and ready are different states. If one system treats a form submission as a confirmed job, a technically successful transfer may create an incorrect promise. The connection must preserve the business meaning, not merely copy a word.
State Records NSW’s system guidance considers integration pathways and information accuracy. It is a useful design reference here, rather than a claim that NSW government recordkeeping rules govern a private WA business.
Check failures and corrections
- Ask how a rejected or delayed transfer becomes visible.
- Find out whether repeat attempts create duplicates.
- Check how corrections move between systems.
- Assign a person to review unresolved exceptions.
A connector can move ordinary records successfully while failing on an attachment or missing field. Ask what evidence staff can inspect and which supplier investigates an uncertain result. An error log is useful only if somebody is responsible for reading and acting on it.
Use approved test facilities for failures. Do not corrupt a live customer record simply to create an exception. Keep a clear route for pausing the connection while an issue is investigated.
Also check work created before the connection was enabled. A supplier may support new entries without transferring earlier open items. Decide whether those records will be imported, completed through the old process or referenced another way. Keep their owners and promised actions visible so the transition does not leave a group of customers outside both workflows.
Check access, documentation and operating cover
- Confirm business control of the relevant accounts.
- Limit supplier and integration permissions to the task.
- Identify the owner of settings and connection credentials.
- Require instructions an authorised replacement can follow.
A low setup price can depend on one person’s ongoing knowledge. If that person is absent, staff may not know whether a missing item is delayed, rejected or never submitted. Handover instructions should explain the evidence and escalation route.
For teams working between Albany and other Great Southern locations, test the actual approved devices and connections. Confirm remote support hours in WA time and any circumstances requiring an on-site visit.
Check the full scope and continuing commitment
- Separate implementation from recurring connector charges.
- Include staff checking and exception work.
- Identify maintenance after either product changes.
- Check export, disconnection and replacement arrangements.
Business.gov.au’s quote guidance recommends clear descriptions, itemised costs and terms. Ask for written clarification of assumptions and exclusions rather than compare a narrow installation price with a broader managed service.
Record which questions are confirmed and which require further investigation. If a supplier says a missing function can be added later, establish the work and cost involved before counting it as part of the offer.
Ask an authorised colleague to follow one record across the proposed arrangement without the supplier narrating every step. Note where extra explanation is required.
A useful integration removes a demonstrated burden while leaving accurate, understandable records. Compare the whole task after the connection, including the work that people still do, before accepting a promise of effortless administration.