Two clean deployment modes. No broad-platform integration story we can't back up. NetSuite sync is bidirectional, event-driven, and live in production today. Xero, MYOB, Abel and SAP connectors are built into your rollout — each one badged below so you know exactly what ships when.
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
Inbound- Customers and contact records
- Items / SKUs with attributes
- Vendors and supplier records
- Chart of accounts (read-only)
OpsUI → NetSuite
Outbound- 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
Inbound- Contacts (customers + suppliers)
- Items, tracked and untracked, per Xero’s inventory model
- Chart of accounts (read-only)
- Tax rates and currencies
OpsUI → Xero
Outbound- 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
Inbound- Customers and suppliers
- Item master records
- Chart of accounts (read-only)
- Tax codes and tax rates
OpsUI → MYOB
Outbound- 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
Inbound- Customers and suppliers
- Item / product master records
- Chart of accounts (read-only)
- Purchase orders and receipts
OpsUI → Abel
Outbound- 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
Inbound- Business partners (customers + suppliers)
- Item master records
- Chart of accounts (read-only)
- Purchase orders and goods receipts
OpsUI → SAP B1
Outbound- 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.
Connects to the systems you already use.
NetSuite, Xero, MYOB, Abel ERP, and SAP Business One on the finance side; NZ Couriers (live today), NZ Post, Mainfreight, Toll, DHL, and Australia Post on the carrier side. Each card carries its delivery tier: live today, or configured against your existing accounts during rollout. 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.
- §01
Rate selection
On order entryService tier and rate quoted live from the NZ Couriers API as the order is captured.
- §02
Label generation
At packCompliant carrier label prints from the pack station, no separate carrier console.
- §03
Live tracking
In transitCarrier tracking events flow back into the order timeline as they happen — no polling.
- §04
Manifest
End of dayDaily 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.
ERP for Xero. Keep Xero, add operations.
Bidirectional Xero sync via the Finance & Accounting module, wired into your tenant during rollout. Full Xero-specific landing, sync detail, and FAQ.
Shopify & WooCommerce: orders in, tracking back.
Store orders flow into pick/pack/ship; fulfillment and tracking flow back. Full platform-specific landing, sync detail, and FAQ.
Wired up in three steps.
Most NetSuite extensions are live in two to three weeks. Standalone deployments skip step 02 entirely.
- 01
Scoping call
Day 1 · 30 minWe confirm whether you're going standalone or extending NetSuite, and which entities map where (subsidiaries, locations, classes).
- 02
Connection & mapping
Week 1–2 · sandboxNetSuite SuiteScript is installed in your sandbox. Field mappings, custom records, and event triggers are configured against your real data.
- 03
Cut-over
Cutover day · liveSandbox is verified against your real data, 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.