One integration framework — stated plainly, connector by connector

Two-way where it counts: Oracle EBS and Oracle Fusion

Both connectors import items, BOMs, routes, work orders, and inventory balances from the ERP, and write back in the other direction on two events: a work-instruction execution reaching Completed posts a work-order completion to the ERP's WIP transaction interface, and an inventory transaction of type Scrap, Adjustment, or Transfer posts an inventory transaction — deliberately excluding ordinary Receipts, which the ERP already owns. Both are real outbound HTTP calls against the ERP's REST or WIP transaction endpoints, not a queued intent that never fires.

Import-first, by explicit design: NetSuite and SAP S/4HANA Cloud

These two connectors import the same five record types as the Oracle connectors, but do not write back. That is a stated design choice, not a missing feature discovered later: a write-back request against either connector returns a clear, typed "not supported" response rather than being silently accepted and dropped. If your ERP is one of these two and you need write-back, say so in the demo — it is a roadmap conversation, not a configuration toggle.

CMMS: MaintainX, inbound today

If your maintenance technicians live in MaintainX, Qontiv ingests assets and maintenance work orders from it by webhook, with a conflict policy where your Qontiv record wins over a stale incoming update. Full detail — including the specific events handled and the echo-suppression mechanism — is on the maintenance and CMMS page. Stated plainly here too: this integration is inbound only today.

The governance layer, common to every connector

Underneath the four connectors is a shared framework that does not vary by vendor:

• Reliable outbound delivery. Outbound rows are claimed with row-level locking and a lease, retried with exponential backoff, and dead-lettered after ten attempts. A permanent 4xx error from the remote system fails the row immediately rather than retrying a request that will never succeed.
• Capability routing with priority. If more than one connector could serve the same capability, an admin sets a priority order per capability, enforced so two connectors can never collide on the same rank.
• Conflict governance, not silent overwrite. Two distinct conflict mechanisms exist: one flags disagreement between what a lower-priority connector reports and what was already accepted; the other flags a record that changed locally since the last sync. Both queue to an admin review screen rather than resolving themselves.
• Provenance tracking. Every accepted import records which connector supplied it and when — tracked per connector and record type today, not yet down to the individual field.
• Five dedicated admin surfaces for connector profiles, the capability-to-connector matrix, capability conflicts, sync conflicts, and integration health — not a single settings page hiding the detail an integration admin needs.

One more governance detail worth naming: reassigning which connector is primary for a capability that has been classified as safety-relevant under the EU Machinery Regulation requires an electronic signature to change, not just an admin click.

Regulatory mapping

Scope — what this does and does not do

• Write-back exists for two capabilities only, on two connectors. Work-order completion and inventory transaction write-back ship for Oracle EBS and Oracle Fusion. A third write-back capability, quality notifications, is explicitly not supported on either.
• No PLM connector ships today. The framework has a defined interface for PLM systems; no vendor connector has been built against it yet.
• DIY integration is always available. CSV import, the REST API, and webhooks work with any ERP or CMMS on every tier — see the developer platform.

Availability

Oracle EBS and Oracle Fusion are included in Professional. NetSuite and SAP S/4HANA Cloud (import scope) are included in Enterprise. The MaintainX CMMS connector ships with maintenance management, included in Professional.See pricing for the full tier ladder, or request a demo to walk your own ERP through it.