Connecting New Software to the Programs and Equipment You Keep

List the programs and equipment you want to keep

• Programs your staff already useAccounting in QuickBooks, appointments in Outlook or Google Calendar, and documents stored in your existing business accounts.
• Equipment used during the workBarcode scanners, scales, payment terminals, printers or machinery connected to the current system.

Record the product name and version for each program, and the model for each piece of equipment. Include the subscription or supplier where it affects access.

Ask staff to show you how each connection is used. A scanner may identify a product, a scale may supply a weight, and a calendar may show appointment details. These examples explain what the replacement needs to support.

Separate connections already in use from new ones you would like. That makes it easier to protect existing work while planning improvements.

Explain what people need from each connection

Describe the useful result before discussing how it will be built. Staff might need to see whether a customer has paid without opening the accounting program, or open a job and find its agreed appointment time.

Decide where information will be entered and where it can be changed. If staff can edit a customer’s address in two programs, agree how the other program will receive the correction.

Also explain how quickly updates are needed. A list prepared each morning may be enough for one task; another may need current information while staff are serving a customer.

Keep the first connection focused on information people actually need. Extra access should have a clear purpose.

Confirm the connection before relying on it

Ask the software supplier or developer to confirm support for your particular products, versions and equipment. A connection with one edition of a program does not establish that every edition works the same way.

Some products have an available add-on or built-in connection. Others provide a supported way for a developer to connect custom software. There may also be a file import option for tasks that do not need immediate updates.

Equipment needs the same attention. Ask for a demonstration using the actual model where practical, including the information it must read or provide. Find out whether an additional licence, provider account or approval is required.

In Klarity Car Wash, a working test of one existing hardware connection helped establish that the equipment could be kept. The case study shows why checking a necessary connection early can be useful.

Keep control of access to your information

Ask which information the connection can read or change, who is allowed to approve it and how access can be removed. Use the supported account-authorisation process rather than sharing a staff member’s password.

For example, Intuit’s guidance for connecting apps to QuickBooks tells users to review the permissions an app requests before authorising it. Ask the same questions about any program connected to your business records.

If a provider gives the connection broader access than the task needs, ask how that access will be protected and whether another approach is suitable. Staff access to the replacement should also reflect what each person needs to do.

Check changes, interruptions and repeated updates

• The information arrives correctlyA completed job is connected to the right customer, with the expected dates, references and amounts.
• Staff can tell when something needs attentionA failed update is visible, and trying again does not create a duplicate record.

Try a normal task, then change or cancel it. Confirm what staff see in both systems and which program keeps the final record.

Ask what happens when the internet connection drops or the other program is unavailable. Staff should know whether to wait, try again or contact someone for help.

Use test accounts or another agreed safe setup while checking connections. Practice should not send real customer messages, create live charges or operate equipment unexpectedly.

Agree who will look after the connection

Connected programs can change after launch. Agree who checks notices from suppliers, renews the relevant accounts and investigates a connection that stops working.

Keep a simple record of what is connected, which business account approved it and who to contact. Store access details securely rather than putting passwords in general project notes.

Include any subscriptions and ongoing maintenance in the replacement plan. A useful connection should remain understandable and supportable after the person who set it up has finished.

Your next step

Choose the connection your business depends on most. Write down the exact products or equipment involved, what staff need to see or do, and who manages the accounts. Ask for that connection to be confirmed before making it a requirement for launch.