Your systems are fine. The gaps between them are the problem.
Orders re-keyed by hand, stock that doesn't match, a month-end that drags. Inite is a New Zealand integration and automation team: we connect Shopify, Dynamics 365 Business Central, Xero, warehouses, 3PLs and EDI channels, as code you own, watched around the clock, at a fixed price.
An hour on your systems with a solutions architect. No cost, no pitch, and you keep the notes.
Technology we connect and build on
- Cloudflare
- Restate
- Microsoft Azure
- AWS
- Power Platform
- Dynamics 365 Business Central
- Oracle NetSuite
- MYOB Acumatica
- Xero
- SAP Business One
- Shopify (incl. multi-store)
- HubSpot
- Stripe
Is your stack the kind we connect?
These are the systems we meet most, and what our experience with each actually looks like. If it has an API, a file feed, or an EDI channel, it's in scope.
Platforms & runtimes
What we build on: Azure when your world is Microsoft, Cloudflare and Restate where flows must survive anything, AWS when your team already lives there.
Cloudflare · Restate · Microsoft Azure · AWS · +1 more
ERP & accounting
Business Central is where our experience runs deepest, back to the Dynamics NAV days. We connect the rest of the NZ ERP landscape to whatever surrounds it.
Dynamics 365 Business Central · Oracle NetSuite · MYOB Acumatica · Xero · +5 more
E-commerce
Multi-store Shopify into one ERP is the pair we've built most: orders, stock, refunds and gift cards landing where finance needs them.
Shopify (incl. multi-store) · WooCommerce · Adobe Commerce (Magento) · BigCommerce
CRM & sales
Keeping CRM, ERP and finance telling the same story, so sales sees what ops sees.
Dynamics 365 Sales · Salesforce · HubSpot · Pipedrive · +1 more
Warehouse & 3PL
Real customer stacks: orders flowing to PeopleVox and ShipMonk untouched by hands, and confirmations flowing back.
PeopleVox · ShipMonk · CartonCloud
Shipping & freight
Consignments, labels and tracking created from the ERP and written back to it, across the NZ carrier landscape.
Mainfreight · Starshipit · NZ Post · GoSweetSpot
Retail & EDI
Supplying the supermarkets means EDI: orders in untouched, ASNs and invoices back correctly, chargebacks avoided.
Foodstuffs eXchange · Woolworths NZ · The Warehouse Group · Mitre 10
Banking & payments
Payouts and bank feeds reconciled to the ledger through clearing accounts, not just imported and hoped for.
Stripe · Windcave · NZ bank feeds (ANZ · ASB · BNZ · Westpac)
Anything with an API
Custom APIs, CSV and SFTP feeds, EDI, webhooks, legacy databases. Breadth is the point, and the full list has links so you can check we mean the same systems.
Recent work
The shape of what we build
Clients are named here only with their sign-off; here's the shape of recent work, anonymised.
The questions you're probably already asking
Anyone who's been burned by an integration project has a list. Here's ours, answered up front.
"What happens if we part ways?"
You own everything we build
Every connection we build belongs to your business, along with plain documentation of how it works. If we ever part ways, everything keeps running, and whoever comes next can pick it up without us.
How our approach works"Fixed price until the variations start."
Fixed price, pay on delivery
Work comes as same-size, fixed-price packages with the scope written down, agreed before it starts. Anything new mid-project becomes its own package, not a variation.
How pricing works"We'll still find out from customers."
An AI engineer on watch, 24/7
Kori, our AI Integration Support Engineer, watches every flow and reports in a chat your team can see. When something fails at 2am, we find out first, and you can watch the investigation happen.
Meet Kori"They'll fight my ERP partner for territory."
We never touch the ERP implementation
Your Business Central partner stays your partner; we make the ERP talk to everything else. The boundary goes in writing, and we work in the same shared chat as your other vendors.
How we partner"And who actually does the work?"
Designed and reviewed by our architects
Our architects design every integration and review every change before it ships. Building happens under that review, by an experienced team of contractors under NDA with no access to your production systems, and all communication runs through the one shared chat.
Meet the team"What happens if you get hit by a bus?"
Nothing lives in anyone's head
Plenty of NZ businesses run on integrations that live in one contractor's head. Here, everything is documented, more than one person is alerted when something fails, and any capable engineer could take over from the documentation alone.
Built to not depend on any one personFor the person who signs off month-end
We reconcile, not just sync
A Shopify payout is not revenue. It's a lump of orders, refunds, fees and gift cards that lands days after the sales it settles. If your integration only copies order totals across, month-end becomes spreadsheet archaeology. We build flows that post at order level, reconcile payouts through a clearing account, treat GST on refunds correctly, and leave a log of every retry, so completeness is something you can evidence, not something you hope for.
If that paragraph reads like your month-end, we should talk.
One hour on your systems. You keep the notes.
Bring a description of what you run and where it hurts. You'll get a practitioner's read: which parts are normal, which are dangerous, what we'd fix first, and roughly what that takes. In writing, yours to keep, whether or not we ever work together.
Meet an integration architectNo cost. It's how we meet the businesses we end up working with.