Run standalone,
or extend NetSuite.
Two clean deployment modes — no broad-platform integration story we can't back up. NetSuite sync is bidirectional and event-driven; standalone is exactly what it sounds like.
Real-time, event-driven, both directions.
Updates propagate as events — not on a schedule. Order entered in NetSuite hits OpsUI within seconds; a fulfillment in OpsUI is a NetSuite item fulfillment within seconds.
NetSuite → OpsUI
- →Customers and contact records
- →Items / SKUs with attributes
- →Vendors and supplier records
- →Chart of accounts (read-only)
OpsUI → NetSuite
- →Sales orders and order updates
- →Inventory movements and adjustments
- →Receipts (PO and inbound)
- →Fulfillment and shipping events
Built on NetSuite RESTlets and SuiteScript event listeners — no SuiteFlow customization required, no third-party iPaaS in the path.
Bidirectional, built into your rollout.
Same event-driven pattern as the NetSuite extension, scoped to Xero's contact / item / invoice model. Wired against your Xero tenant during onboarding rather than installed from an app marketplace.
Xero → OpsUI
- →Contacts (customers + suppliers)
- →Tracked + untracked items
- →Chart of accounts (read-only)
- →Tax rates and currencies
OpsUI → Xero
- →Sales invoices and credit notes
- →Payment events and reconciliation hints
- →Stock count and adjustment journals
- →Customer record updates
Built on Xero's OAuth2 + accounting/payroll APIs and webhook subscriptions — no third-party iPaaS in the path. Per-customer tenant binding so multi-Xero ops never cross streams.
AccountRight or Business — both API surfaces covered.
Same event-driven shape as the NetSuite and Xero extensions, tuned for MYOB's AccountRight (desktop-style) and Business (cloud-native) APIs. Wired against your MYOB tenant during onboarding.
MYOB → OpsUI
- →Customers and suppliers
- →Item master records
- →Chart of accounts (read-only)
- →Tax codes and tax rates
OpsUI → MYOB
- →Sales invoices and credits
- →Payment events and remittance data
- →Inventory movements and adjustments
- →Customer record updates
Built against MYOB's AccountRight Live API for desktop-product customers and the MYOB Business API for cloud-native customers — the choice is driven by which product the customer runs, not by us.
A modern ops layer on a NZ-built ERP.
Same event-driven shape as the NetSuite, Xero, and MYOB extensions, tuned for Abel. Keep finance and manufacturing in Abel; run warehouse, picking, and dispatch in OpsUI. Wired against your Abel tenant during onboarding.
Abel → OpsUI
- →Customers and suppliers
- →Item / product master records
- →Chart of accounts (read-only)
- →Purchase orders and receipts
OpsUI → Abel
- →Sales orders and order updates
- →Invoices and payment events
- →Inventory movements and adjustments
- →Fulfilment and dispatch events
Built against your Abel tenant's integration surface — no third-party iPaaS in the path, no nightly batch jobs. The sync is scoped during onboarding against how your Abel install is configured.
A modern ops layer on SAP Business One.
Same event-driven shape as the NetSuite, Xero, MYOB, and Abel extensions, tuned for SAP Business One. Keep finance in B1; run warehouse, picking, and dispatch in OpsUI. Wired against your B1 company database during onboarding — no SAP EWM add-on required.
SAP B1 → OpsUI
- →Business partners (customers + suppliers)
- →Item master records
- →Chart of accounts (read-only)
- →Purchase orders and goods receipts
OpsUI → SAP B1
- →Sales orders and deliveries
- →A/R invoices and payment events
- →Inventory movements and adjustments
- →Fulfilment and dispatch events
Built against the SAP Business One Service Layer (HANA) or DI API (SQL) depending on your deployment — no third-party iPaaS in the path, no nightly batch. The sync is scoped during onboarding against how your B1 company database and add-ons are configured.
Ships with the systems you already use.
NetSuite, Xero, MYOB, Abel ERP, and SAP Business One on the finance side; NZ Couriers, NZ Post, Mainfreight, Toll, DHL, and Australia Post on the carrier side — all wired against your existing accounts. Click any system for the full integration detail.
"Live" means a direct integration shipping in production today. "Configurable" means the Shipping/Outbound module handles the workflow and the specific connector is confirmed during scoping against your existing account. "Built on rollout" means the connector is delivered during onboarding rather than as a self-serve product today.
Labels and tracking, built in.
Print labels and pull tracking events directly from the NZ Couriers API — no middleware, no manual reconciliation. The Shipping/Outbound module wires this in automatically.
- §01On order entry
Rate selection
Service tier and rate quoted live from the NZ Couriers API as the order is captured.
- §02At pack
Label generation
Compliant carrier label prints from the pack station, no separate carrier console.
- §03In transit
Live tracking
Carrier tracking events flow back into the order timeline as they happen — no polling.
- §04End of day
Manifest
Daily manifest auto-generates and submits to the carrier — no manual reconciliation.
Direct NZ Couriers REST API integration — the Shipping/Outbound module owns the wiring. No iPaaS, no FTP drops.
Wired up in three steps.
Most NetSuite extensions are live in two to three weeks. Standalone deployments skip step 02 entirely.
- §01Day 1 · 30 min
Scoping call
We confirm whether you're going standalone or extending NetSuite, and which entities map where (subsidiaries, locations, classes).
- §02Week 1–2 · sandbox
Connection & mapping
NetSuite SuiteScript is installed in your sandbox. Field mappings, custom records, and event triggers are configured against your real data.
- §03Cutover day · live
Cut-over
Sandbox is verified end-to-end, then production is enabled. Sync runs live from day one, with rollback ready if needed.
Run NetSuite already? Let's see your setup.
Walk us through your current NetSuite environment and we'll show you exactly which OpsUI modules slot in and what the sync covers.