Quick answer
To connect your website, CRM or ERP, list exactly which information should move between them. Decide where the correct record is kept, when updates happen and who handles failures. Include duplicate records and interrupted updates in the checks before accepting the work.
What information should move?
Name the exact systems, fields and record references. State whether information travels one way or both, what starts an update and how quickly it should arrive. Decide which changes each system can make.
An API is a way for software systems to exchange information. Check that the required API or another supported method is available, with the permissions, licence and usage limits you need.
What happens when records do not match?
Use sample records to explain duplicates, corrections and reversed payments. Identify which system has the correct version and who resolves a difference.
The phrase “integrated platform” may only describe features inside one product. Ask which outside systems will actually be connected.
Ask how failures are found and fixed
- Make failed transfers visible to the responsible staff member.
- Agree alerts and when a transfer can be retried.
- Check that a repeated update does not create another order, payment instruction or enquiry.
- Test missing fields, unavailable systems and denied access.
- Agree how credentials and personal data are protected.
- Name who maintains the connection when either system changes.
Check a retry after a lost confirmation
An update can succeed even if its confirmation does not reach the first system. Ask for a demonstration of a retry that does not repeat the business action.
After recovery, staff should be able to compare both sets of records and find differences. Use sample data separate from real customer records for testing.
Your planning worksheet
Use this table to prepare the same brief for each provider. Add the person responsible and the current status for each item. Enter costs only from written quotes, in HKD, with the billing period.
| Item to plan | Details to give the provider | What to check |
|---|---|---|
| Record transfer | Source, destination, identifier and editable fields | Document direction, trigger and expected result |
| Duplicate/correction | Matching rule, system with the correct records and conflict owner | A repeated transfer does not silently create duplicates |
| Fixing failed transfers | Who receives alerts, when to retry and how records are checked | Staff can find and recover a failed transfer |
Example project scenario
Illustrative planning example; not a completed customer project.
A website sends enquiries to a CRM. If the CRM is unavailable, the failure is recorded. A retry should not create a second enquiry. Staff use a shared reference to compare the records. These are requirements for the example, not results from a completed project.
Common questions
Do two APIs make a connection straightforward?
Not necessarily. Check the fields, permissions, usage limits and supported actions. Agree who handles failed or repeated updates and later service changes.
Is one successful transfer enough?
Include interrupted transfers, duplicates, missing fields and rejected access. Staff also need a way to find errors and check the records after recovery.
Who looks after the connection after launch?
Name the owner in the support agreement. Ask who monitors failures and updates the connection when either system changes.
Download the planning worksheet (CSV)
Find a provider through TechQuotations
TechQuotations connects Hong Kong buyers with IT service providers. Use your brief to discuss the work and compare proposals. You choose the provider and agree the terms directly. A request does not guarantee a quotation.
Explore suitable providers through TechQuotations