A written map of the systems and the data that moves between them
Which system holds what, which way each record travels, and where it must arrive — drawn up and agreed before anything is connected.
PLATE P.05 — INTEGRATION LAYER
Systems integration and automation for Australian businesses
Systems integration connects the software a business already runs — CRM, stock, payments, accounts, freight — so data entered once moves everywhere it is needed and nobody re-keys it. Ozwebnet builds integrations and automations from scratch in Adelaide, South Australia, for businesses across Australia. You receive the source code with the IP assigned to you, under one fixed quote staged against milestones.
GENERAL NOTES
02 / 08
What does systems integration actually connect?
The systems you keep. An integration layer sits between them and moves the data: an order in the store becomes a job in operations, a pick in the warehouse, an invoice in accounts. Nothing is replaced; what changes is that the copy-paste, the nightly export and the swivel-chair syncing stop.
SECTION A–A
03 / 08
Who needs systems integration?
- BUILT FOR
- Businesses re-keying the same data into three or four systems; stores whose warehouse and accounts do not talk; teams whose nightly CSV export is a job.
- REPLACES
- Swivel-chair syncing, nightly exports, copy-paste between logins.
- NOT FOR
- Two systems that already connect natively — we will say so.
SCHEDULE OF WORKS
04 / 08
What is included in a systems integration build?
Connections to each system
Each system you keep — CRM, stock, payments, accounts, freight — is connected through the data it exposes, in the direction the map says.
The rules for what moves, when, and what happens on a mismatch
What moves, when it moves, and what the layer does when two systems do not agree — written down and agreed before it is built.
Automations for the steps people currently do by hand
Re-keying and the nightly export are done by the layer the moment a record arrives — not by a person on Friday afternoon.
Logs you can read when something did not move
What moved and what did not is written down as it happens, so a missing invoice turns up the same day, not at month end.
Handover of the source code with the IP assigned to you
The layer is yours: the code, the rights, and a working system at every milestone along the way.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
STAGES
05 / 08
How is an integration built and priced?
An integration is priced by the systems it connects and the records that must move between them: one fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with records moving on their own; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →- 01 SURVEY
Discovery
We map the systems you keep and the records that must move between them.
- 02 BLUEPRINT
Specification
What moves, when, and what happens on a mismatch are specified in writing; the fixed quote is set here.
- 03 FORGE
Build
Connected system by system; each milestone ends with records moving on their own.
- 04 TEMPER
Testing
Every path checked with real records before launch.
- 05 DEPLOY
Launch
The layer goes live, and you receive the source code with the IP assigned to you.
DETAIL 1 — MAP
06 / 08
How does an integration layer move data between systems?
Each system keeps its own records and its own login. The layer sits between them, holds the map of what lives where, and moves each record along the pipes once it is entered — so an order taken in the CRM reaches stock, payments and accounts without a person re-keying it.
- THE SYSTEMS
- CRM, stock, payments and accounts stay as they are — the software you already run, each still the place its own records live.
- THE LAYER
- One piece of software between them: the map of what lives where, the rules for what moves and when, the log of what did.
- WHAT MOVES
- The record, entered once: an order becomes a pick, a payment and an invoice in the systems that hold them, without a person re-keying it.
REQUESTS FOR INFORMATION
07 / 08
Questions before you brief us
RFI-01Does integration mean replacing our current software?
No. It connects what you keep.
RFI-02Which systems can be connected?
Any system that exposes its data — most CRM, accounting, stock, payment and freight platforms do. We confirm each one at Survey.
RFI-03Do you work with businesses outside Adelaide?
Yes — this is our most remote-capable service; Australia-wide.
RFI-04How is integration priced?
One fixed quote, set in writing before the build and staged against milestones.
RFI-05Who owns the integration?
You do — source code delivered, IP assigned.
ISSUE
08 / 08
Start a brief for an integration.
One email is the whole front door. Tell us what you run or sell, what breaks today, and when you need it working. By appointment only.