ERP integration

Released configurations land in ERP without anyone re-typing them.

Cadxor pushes configured items, BOMs, quotes, orders, dimensions, drawing and CAD links, lead times and status into the ERP you already run. Integrations are idempotent, logged and safe to retry.

See integrationsBook a demo
NetSuite first

A deep NetSuite story, without making NetSuite mandatory.

  • Create or update configured assembly items with Cadxor configuration ID and dimensions Built · dry-run
  • BOM members from the component revisions used Built · dry-run
  • Create estimates for the customer Built · dry-run
  • Attach drawing and CAD file references to the item Built · dry-run
  • Create or match the customer record Built · dry-run
  • Create sales orders from accepted quotes Roadmap
  • Launch a Cadxor configuration from a NetSuite transaction (SuiteScript button) Roadmap
  • Receive order status back from NetSuite Roadmap

Uses SuiteTalk REST with token-based authentication and externalId upserts. The NetSuite connector currently runs in dry-run mode in the demo workspace; live mode is enabled per customer during implementation.

# What a release sends (dry-run log excerpt)
PUT /record/v1/assemblyItem/eid:cadxor-CFG-00042-r2
{
  "itemId": "CFG-00042-R2",
  "custitem_cadxor_length_in": 40.0,
  "custitem_cadxor_overall_in": 41.0,
  "custitem_cadxor_material": "304SS",
  "member": { "items": [ ... ] }
}
PUT /record/v1/estimate/eid:cadxor-CFG-00042-r2-est
# idempotency key: cadxor:CFG-00042:r2:estimate
# retry → "unchanged", never a duplicate
Integration framework

Built for retries, audits and the next ERP.

Idempotent by design

Each operation has a key derived from the configuration number and revision. A ledger maps keys to remote records, so retries update rather than duplicate.

Logged and retryable

Every request and response is logged against the configuration, with an error queue and one-click retry for failed syncs.

Dry-run first

Review exact payloads and field mappings before a single record is written to your ERP.

Credentials stay secret

ERP credentials live in a secrets manager and are referenced, never stored in the application database or shown in logs.

Mapped, not hard-coded

Record types and custom fields are mapped per customer, so your ERP's naming conventions are respected.

Same pattern everywhere

Dynamics 365, SAP, Epicor, Acumatica, Odoo, Infor and Oracle follow the same operation model; webhooks cover the rest.

See Cadxor with your own product family.

Bring one configurable product line. We will map its components and rules and show you the generated package.

Book a demoTry the demo