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
Every system we work with

The systems we connect

The systems we work with most, and what our experience with each looks like. Any system with an API, a file feed or an EDI channel is within scope.

Platforms & runtimes

What we build on: Azure for a Microsoft estate, Cloudflare and Restate where flows must survive anything, AWS where the customer already runs it.

Cloudflare · Restate · Microsoft Azure · AWS · +1 more

ERP & accounting

Business Central is our deepest experience, back to Dynamics NAV. The rest of the NZ ERP landscape is connected 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 have built most: orders, stock, refunds and gift cards landing where finance needs them.

Shopify (incl. multi-store) · WooCommerce · Adobe Commerce (Magento) · BigCommerce

CRM & sales

CRM, ERP and finance kept in agreement, so sales and operations see the same customers, orders and invoices.

Dynamics 365 Sales · Salesforce · HubSpot · Pipedrive · +1 more

Warehouse & 3PL

Orders flowing to PeopleVox and ShipMonk without manual re-entry, and confirmations flowing back, in stacks we operate today.

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 without re-entry, ASNs and invoices back to specification, chargebacks avoided.

Foodstuffs eXchange · Woolworths NZ · The Warehouse Group · Mitre 10

Banking & payments

Payouts and bank feeds reconciled to the ledger through clearing accounts, at order level.

Stripe · Windcave · NZ bank feeds (ANZ · ASB · BNZ · Westpac)

Anything with an API

Custom APIs, CSV and SFTP feeds, EDI, webhooks, legacy databases. The full list links each system by name.

Every system we work with

Recent work

The shape of what we build

Customers are named only with their written agreement. The work below is anonymised.

All case studies

How we deliver

The terms every engagement runs on. The detail behind each is one link away.

The customer owns everything we build

Integrations run on a platform the customer owns, in code the customer owns, with current documentation of how data moves between the systems. If the engagement ends, everything keeps running and whoever comes next can take it over.

How our approach works

Fixed-price delivery, agreed before work starts

Work is scoped and priced as fixed packages with the scope written down, agreed before it begins. Anything new that arises during a project becomes its own package, so the agreed price is the price paid.

How pricing works

Continuous monitoring by Kori

Kori, our AI Integration Support Engineer, monitors every integration continuously, carries out first-line investigation and reports its findings in the open, in the working channel the customer shares with Inite.

Meet Kori

The ERP partner delivers the implementation

ERP implementation partners deliver the implementation and keep the client relationship; Inite delivers the integrations around it. The boundary is written into every scope, and the work runs in one working channel shared with the customer's other vendors.

How we partner

Designed and reviewed by solutions architects

A solutions architect designs every integration, and a second architect reviews every design before it is built. Building happens under that review, by engineers under NDA with no access to production systems, and all communication runs through the one working channel.

Meet the team

Built to not depend on any one person

Documentation, ownership and monitoring together mean that no integration depends on any one person at Inite or at the customer. More than one person is alerted when something fails, and any capable engineer can take over from the documentation.

Built to not depend on any one person

For finance

Reconciliation, not only synchronisation

A Shopify payout is not revenue. It is a settlement of orders, refunds, fees and gift cards that lands days after the sales it covers. An integration that only copies order totals across leaves month-end to be reconstructed in spreadsheets. Inite builds flows that post at order level, reconcile payouts through a clearing account, treat GST on refunds correctly and keep a log of every retry, so completeness can be evidenced.

The first step

Every engagement begins with a free assessment: an hour with a solutions architect on your systems and integration plans. You receive a written read of what is normal, what is at risk, what we would fix first and roughly what that takes.

Meet an integration architect