Integrations — CAD, PDM/PLM and ERP

Origeq is not another silo. It reads from the engineering data you already maintain and hands structured orders back to the systems that already run your business. Nothing is rebuilt, and nothing is ripped out.

This page is the detailed version of what connects where. If you are still working out what the product does, start with What is a 3D spare parts catalog? instead.

Getting your data in

The starting point is always a file your engineers already export.

STEP and native CAD. STEP is the common case and needs no preparation — upload the file and conversion plus part extraction happen automatically. Native SolidWorks and Inventor files are supported directly, so you do not have to introduce an export step into an existing engineering workflow.

PDM and PLM systems. Larger deployments connect a PDM or PLM system rather than uploading files one at a time. This matters when your assemblies are revised often: the catalog follows the source of truth instead of drifting away from it.

Batch upload and API. When you are bringing across an existing install base rather than a single machine, assemblies can be pushed in bulk through batch upload or through the API.

You do not need to clean up, simplify or re-author anything first. There is no manual preparation step.

Getting orders out

A part request is only useful if it lands where your team already works.

Email and RFQ. The default. Requests arrive as clean, structured messages naming specific part numbers and quantities — not a description someone has to interpret. This works on every plan and needs no integration at all.

ERP integration. On the Enterprise plan (the deployment our RFP page calls Origeq Portal), order requests can flow directly into your ERP, so a customer's selection becomes a line on an order without anyone rekeying it.

Payment gateways. Where you want customers to complete a purchase rather than raise a request, payment can be handled in the flow.

Fitting the rest of your stack

SharePoint. Documentation you already publish in SharePoint can sit alongside the 3D model, so a customer looking at a part also has the current manual and service guide.

Analytics. Catalog activity feeds your existing analytics tooling — which assemblies get opened, which parts get selected, where requests stall.

REST API and webhooks. This is the general answer to "do you integrate with X". The REST API and webhooks let you wire Origeq into systems we do not ship a named connector for. If you have an in-house ordering system or an unusual ERP, this is the path.

What we do not claim

Two things worth being direct about, because they come up in every RFP:

• We are not SOC 2 or ISO 27001 certified today. Origeq is built API-first following those practices, and certification is on the active roadmap — not something already held. See Security for the full position.
• Not every ERP has a named connector. Where one does not exist, the honest answer is the REST API plus scoped integration work, not a checkbox on a feature grid.

Start without an integration

Worth saying explicitly: none of the above is a prerequisite. Uploading a single STEP file requires no administrator rights, no integration and no IT ticket — you get a shareable link back in minutes. Integrations are what you add once the thing has proved itself on one assembly.

Your first 5 assemblies are free. If your setup is unusual, tell us about it and we will say plainly what fits and what does not.