platform/enterprise-integrations
Integrations don’t fail on connection. They fail on ownership.
Connecting two systems takes an afternoon. Deciding which of them is right about a weight when they disagree — and making sure neither silently overwrites the other at 3am — is the part that takes eighteen months and usually goes wrong.
Direction is declared per field, not per system · nothing is written back until you enable that field class
Every connector starts read-only until you enable a field class.
Request and response retained per write, per system.
Measured at the boundary, excluding third-party outages.
Conflicting values are surfaced, never resolved by last-write-wins.
Declared per field, because that is the only level it is answerable at.
“The ERP is the system of record” is true about price and meaningless about compatibility. Ownership has to be finer than the system.
SAP S/4HANA · NetSuite · Dynamics
Owns cost, stock and commercial terms
cost_price
ERP
read-only · never written back
stock_on_hand
ERP
read-only · propagated to channels
list_price
ERP
read · repricer may propose, never commit
supplier_terms
ERP
read-only
gtin
ERP
read · validated against GS1, conflicts surfaced
Five commitments about your systems.
Read-only until proven
Every connector begins read-only. Write scopes are enabled per field class, by you, after you have seen a dry-run diff of what would change.
Field-level ownership
System-level ownership is the wrong granularity and causes most integration disasters. Ownership is declared per field, so the ERP can own price while Aonex owns compatibility, without either overwriting the other.
Conflicts surface, never merge
When two systems disagree about a field neither definitively owns, both values are retained and reported. Silent last-write-wins is how catalogs quietly corrupt.
Your credentials, scoped
We write through credentials you issue and can revoke, with the minimum scope the integration needs. Every call is logged with request and response.
No lock-in surface
The graph exports in full at any time. If you leave, your enriched attributes, provenance and history come with you.
Enterprise integration pages usually lead with a connector count, because it is an easy number to make large. It is also close to meaningless — the count includes connectors nobody has run in production, and it says nothing about the only question that matters during an evaluation.
That question is: when your ERP and this platform disagree about a value at 3am, what happens? Our answer is that nothing happens, loudly. Both values persist, the conflict is raised, and no write occurs until a precedence rule you wrote says which wins.
Find out where your systems disagree.
Connect read-only to two systems that both hold product data. We will return the field-level conflict report — every attribute where they disagree, and which one has a traceable source behind it. Most teams have never seen this list.
Read-only credentials · No writes · Report in 10 working days