Decide who owns each piece of data
The most important integration decision happens before any connection is built: which system is the source of truth for each kind of data. If the store and an inventory system both think they own stock levels, they will overwrite each other. If prices are edited in two places, they will drift apart.
| Data | Common source of truth | Flows to |
|---|---|---|
| Product details | Store, or a product information system for large ranges | Marketplaces, feeds, POS |
| Stock levels | Inventory or ERP system, or the store for simple setups | Store, marketplaces |
| Prices | Store or ERP, never both | Store, feeds |
| Customers | Store | Email marketing, accounting |
| Orders | Store | Warehouse, accounting, shipping |
| Invoices and tax | Accounting system | Reports |
We write this table for your business during planning, and every connection follows it.
Integrations we commonly set up
| Area | Typical connection |
|---|---|
| Payments | Payment gateway, wallets and buy-now-pay-later providers |
| Shipping | Carrier rates, label printing and tracking emails |
| Inventory | Stock sync with a warehouse, 3PL or inventory system |
| Accounting | Orders, refunds and GST flowing to your accounting package |
| Marketing | Customer and order data to an email or SMS platform, with consent recorded |
| Analytics | Sales and conversion tracking, with consent where it applies |
| Subscriptions | Recurring orders through a subscription app or platform feature |
| Multichannel | Product feeds to Google Merchant Center and marketplaces |
Apps, middleware or custom code
There are three ways to connect systems, and the right one depends on volume and complexity:
- Official apps. The quickest and cheapest when one exists and does what you need. We check reviews, update history and what data the app can access.
- Middleware. A connector service sits between systems and handles mapping and retries. Useful when several systems need to talk to each other.
- Custom integration. Code that uses each system's API directly. Worth it for unusual data, high volume or when no app fits, but it needs maintenance.
Marketing data and consent
Connecting your store to an email or SMS platform is one of the most valuable integrations and one of the easiest to get wrong. The Spam Act requires consent before sending commercial messages, accurate identification of your business and a working unsubscribe that is honoured within five working days. The ACMA says inferred consent is less reliable than express consent, and that it does not cover messages sent just after a purchase[1]. We pass a clear consent flag from checkout to your marketing platform so only people who opted in are marketed to. The Spam Act guide explains the rules.
Personal information moves with the data
Every integration that copies customer data to another system extends where personal information is held. Under Australian Privacy Principle 11, a covered business has to take reasonable steps to keep that information safe from misuse, loss and unauthorised access or changes, and the law has named technical and organisational measures as part of those steps since December 2024[2]. Many small businesses with turnover of $3 million or less are exempt from the Privacy Act, but there are important exceptions, including businesses that trade in personal information[3]. We keep integrations to the data each system needs and use access keys with the narrowest permissions available.
Feeds for Google and marketplaces
A product feed sends your catalogue to Google Merchant Center and marketplaces. Merchant Center free listings let products appear at no cost across Google surfaces including Search, Images, YouTube and the Shopping tab[4]. We set feeds up so titles, prices, availability and GST-inclusive prices match the store, which avoids disapprovals and confused shoppers.
How we deliver integrations
- Systems map. Every system, the data it holds and the source of truth for each field.
- Option review. Apps, middleware or custom code compared on cost, limits and maintenance.
- Build in staging. Connections built against test accounts or sandboxes where the provider offers them.
- Failure testing. What happens when a system is down, an order fails or stock goes negative.
- Monitoring and handover. Alerts for failed syncs, plus notes on how to check and fix common issues.
Questions
Can you connect my store to my accounting software?
Usually, through an official app or a connector. We check that refunds, discounts and GST map correctly, since those cause most accounting mismatches.
What if two systems both change stock levels?
We pick one system as the source of truth for stock and make the others follow it. That is the main way to prevent overselling.
Do integrations add monthly costs?
Often. Apps and middleware usually charge monthly fees. Every recurring cost is listed in the quote.
Can you connect a custom or in-house system?
If it has an API or can export files on a schedule, usually yes. We confirm that during the systems map before quoting.
Sources
Opened and checked on 3 November 2026. Each entry says what kind of source it is.
- Avoid sending spam. Australian Communications and Media Authority (ACMA), undated page. Regulator
- Chapter 11: APP 11 Security of personal information. OAIC, Australian Privacy Principles guidelines, updated 3 October 2025. Regulator
- Small business. Office of the Australian Information Commissioner (OAIC), updated 5 September 2024. Regulator
- Free listings for products. Google Merchant Center Help, undated page. Platform documentation