Make your existing systems agree on what happened next.
Connect the records and actions your team currently carries between tools. Canvo builds integrations around real stock, customer, order and finance rules, including what should happen when two systems disagree.
A system that fits the work.
Business systems integration moves validated information and actions between applications. An API is one way software can read or change another system. The important design choices are which record is authoritative, when updates happen, what a successful transfer means and how failures are reconciled.
What changes when the work gets complicated?
The last local unit sells
- What arrives
- A counter sale changes availability while the supplier feed still shows stock.
- What is checked
- Exact variant, stock ownership, reservations and supplier-feed age.
- What happens next
- Update the eligible sales-channel promise using source-specific rules; hold stale or ambiguous information.
- What finishes the work
- An explained availability state without treating supplier units as stock in your store.
An accepted quote must become delivery work
- What arrives
- Sales marks a customer quote as accepted in the CRM.
- What is checked
- Customer identity, accepted version, line items and existing downstream records.
- What happens next
- Create the authorised job or order and return its reference to the CRM; reconcile an uncertain write before retrying.
- What finishes the work
- Connected sales and delivery records without silently creating the same job twice.
Finance sees a different amount
- What arrives
- A channel settlement combines orders, fees and a refund.
- What is checked
- Order references, currency, payment status, fees and prior allocations.
- What happens next
- Apply approved matching rules and record the breakdown; route unexplained differences to finance.
- What finishes the work
- A supported reconciliation or a focused exception, with source records retained.
A record and rule map
Agree identifiers, field mappings, source ownership and update direction. Distinguish local stock, supplier availability and reservations.
A tested connection
Build the agreed reads and writes using available APIs, events or controlled imports. Validate records before changing the destination.
Reconciliation and recovery
Detect missing or conflicting updates, check partial success before retrying and give unresolved records a named owner.
How the work moves through the system
Read the source
Receive an event or retrieve the agreed records on a defined schedule.
Match and validate
Check identities, units, required fields, freshness and whether the change is authorised.
Update the destination
Write eligible changes with protection against duplicate events.
Confirm and reconcile
Check destination records and resolve uncertain outcomes before repeating an action.
Decide which system owns each fact.
Two-way copying is not a complete design. Different systems can own different fields, and some events must never overwrite a newer decision.
| Record | Example source of authority | Important distinction |
|---|---|---|
| Local stock | The agreed inventory record | On hand, reserved and available are different |
| Supplier availability | A dated supplier feed | Available to order is not owned local stock |
| Accepted price | The approved quote version | A later promotion may not change an existing agreement |
Separate an event from its business effect
Receiving an online order twice must not reserve stock twice. A timeout does not prove the first write failed.
Match the update rate to the promise
A scheduled supplier feed has a freshness limit. Agree how the business behaves between updates instead of promising universal real-time sync.
Use a native connector where it covers the work.
Custom integration earns its place when the remaining rules, records or exception paths do not fit the standard connection.
Check the actual platform capabilities
Shopify, Square, Xero and CRM connections depend on available access, plans and supported records. Naming two products does not establish a complete integration.
See the G3 commerce example
Our founder-owned business separates local and supplier availability, updates eligible catalogue records and imports online orders. Its scheduled paths illustrate the design; they are not a promise that every platform pair is already delivered.
Questions worth asking
Do we need to replace our CRM, accounting or shop software?
Usually the first step is assessing the existing tools. Use native features where suitable; scope custom connections for the remaining work. A missing API, restricted write access or poor source data can change what is practical.
Does every integration need AI?
No. Known identifiers, calculations and fixed routing usually need ordinary code. AI can help interpret an email or document, while explicit checks govern the records and actions that follow.
What does a systems integration cost?
The A$950 ex GST diagnostic is credited to implementation under the agreed scope. A tightly bounded first workflow starts at A$4,900 ex GST. More applications, historical data, conflicting rules and recovery requirements increase the scope; third-party subscriptions are separate.
Who looks after compatibility changes?
Implementation includes 12 months from acceptance for agreed workflow defects and minor compatibility changes within existing integrations. No Canvo subscription is required. Optional proactive care starts from A$490/month ex GST with separately agreed scope; covered repairs do not require that plan. Software, API, model and hosting costs are separate. The proposal records coverage and responsibilities.
Can you connect software without a usable API?
Possibly. A supported export/import path or vendor-approved connection may cover the required records. We check update frequency, identifiers, write permissions and how failed transfers can be detected before proposing it. If reliable access is unavailable, we may narrow the workflow or retain a controlled manual step rather than promise a connection that cannot be operated safely.
Does ongoing sync include migrating all our historical records?
These are separate scopes. Ongoing sync handles agreed changes from a defined starting point; a historical migration also needs mapping, duplicate handling and checks of existing records. If both are needed, the proposal should define the initial load, cutover, reconciliation and recovery plan so old records are not mistaken for new business events.
Bring one process. We’ll map the next step.
Start with the input, the result your team needs and an exception that keeps coming back. Estimate the value, then check the assumptions with George.
12 months of support from acceptance covers defects in the agreed implementation and minor compatibility changes to existing integrations. Optional proactive care from A$490/month ex GST and further development are scoped separately. Third-party software, hosting and API costs are separate.