Skip to content
All integrations
Built on rollout · Abel ERP
Abel ERP logo
Built on rollout

A modern ops layer on a NZ-built ERP.

Abel runs finance and manufacturing for plenty of NZ producers. OpsUI adds the warehouse and dispatch layer on top — orders, inventory, invoices, and master data sync both ways, so you keep Abel as the system of record instead of ripping it out.

What you get

Abel ERP stays finance. OpsUI runs the floor.

  1. §01

    Orders both ways

    Sales orders, order updates, and fulfilment events sync in both directions between Abel and OpsUI.

  2. §02

    Customers & suppliers

    Master records stay in lockstep so the floor and finance see the same customers and suppliers.

  3. §03

    Items & inventory

    Item master, stock counts, and movements propagate between OpsUI and Abel.

  4. §04

    Invoices & financials

    Invoices and payment events flow back to Abel, which stays the system of record for finance.

  5. §05

    Conflict resolution

    Field-level rules decide which system wins when a record is edited on both sides.

  6. §06

    Built per rollout

    Abel installs vary, so the connector is wired against your tenant during onboarding rather than shipped as a self-serve download.

What flows where

Both directions, no manual reconcile.

Abel ERP → OpsUI

  • Customers and suppliers
  • Item / product master records
  • Chart of accounts (read-only)
  • Purchase orders and receipts

OpsUI → Abel ERP

  • Sales orders and order updates
  • Invoices and payment events
  • Inventory movements and adjustments
  • Fulfilment and dispatch events
Technical detail

Built against your Abel tenant's integration surface — no third-party iPaaS in the path and no nightly batch. Because Abel installs differ, the sync is scoped to how yours is configured during onboarding.

Frequently asked

The honest answers.

  • Do I have to replace Abel ERP?

    No. Abel stays your system of record for finance and manufacturing. OpsUI adds the warehouse, picking, packing, and dispatch layer and syncs back to Abel — so you avoid a costly, risky ERP migration.

  • Is the Abel connector live and self-serve today?

    It is delivered during your rollout rather than as a self-serve download, because Abel installs differ and the sync is scoped to yours. The rest of OpsUI runs in production today and can run standalone alongside Abel in the meantime.

  • What kind of businesses run Abel?

    Abel is a New Zealand-built ERP common in local manufacturing, food production, and wholesale/distribution — exactly the operations that benefit from a dedicated warehouse and dispatch layer on top.

Running Abel ERP? Let’s wire it in.

Walk us through your current Abel ERP setup and we’ll show how OpsUI fits on top — warehouse, picking, and dispatch, syncing back to Abel ERP.