Factory OS / MES ERP design-partner tier

Connect ION Factory OS to NetSuite with AI

Plenty of hardware companies run both: ION Factory OS for build execution and traceability on the floor, NetSuite as the corporate ERP for purchasing, inventory valuation, and financials. The pairing works — until someone needs an answer that spans the seam. Which NetSuite POs feed the parts that WO-88 is waiting on? Does NetSuite item availability agree with what ION thinks is on the shelf? Traditionally that means a SuiteScript project, a saved-search export, or a data warehouse — each one a multi-week commitment with its own maintenance tail.

bomrail takes a different approach: it does not move data between ION and NetSuite at all. Both systems get wrapped in typed, read-only MCP tools behind one hosted endpoint, and the joining happens in the AI agent’s reasoning, at question time, against live records. When the answer arrives, each fact carries its source — this quantity from ION, this receipt status from NetSuite — so you can verify rather than trust.

For teams mid-migration between the two systems, this is especially useful: agents can compare records across both and surface disagreements (quantity mismatches, orphaned POs, items that exist in one system only) as a daily question instead of a quarterly cleanup.

What becomes answerable

bomrail exposes both systems as read-only MCP tools. These are the joins an agent can make on demand:

Purchase orders & receipts

NetSuite POs and receipt status lined up against the ION work orders consuming those parts.

Item availability

NetSuite per-location availability compared with ION on-hand and reservations — disagreements surfaced explicitly.

Vendor bills

Bills pending approval in NetSuite tied back to what ION received, for a grounded approve/hold decision.

Item masters

The same part in both systems: cost and preferred vendor from NetSuite, revision and demand from ION.

Shortage chains

From a blocked ION work order to the specific NetSuite PO line and its expected receipt date.

Example: chasing a shortage across the seam

A build is blocked. In ION, WO-88 shows two line items short. Someone asks the agent: "What is blocking WO-88 and when does it unblock?" The agent reads the work order from ION, identifies the short parts, queries NetSuite for open PO lines on those items, and answers: one part arrives Thursday per the NetSuite receipt schedule; the other was never ordered — the requisition is still pending approval in NetSuite.

The second half of that answer is the valuable one. A sync tool would have faithfully replicated the missing PO as missing; the agent instead noticed the gap between demand in one system and absence in the other, and pointed at the pending requisition as the cause.

Frequently asked questions

Do we need SuiteScript or a NetSuite consultant for this?

No. bomrail connects to NetSuite using token-based authentication against a read-only role that you create and control. There is no SuiteScript to deploy, no bundle to install, and no customization to maintain through NetSuite upgrades.

How is this different from a data warehouse with a BI layer?

A warehouse answers pre-modeled questions from replicated data on a refresh schedule. bomrail answers arbitrary questions from live data with no pipeline to build or maintain. They are complementary: warehouses for dashboards, bomrail for the questions nobody modeled in advance.

Can agents see NetSuite financials they should not?

Agents can only reach what the connected NetSuite role permits. Most teams scope the role to purchasing, inventory, and vendor bills, excluding GL and payroll entirely. bomrail adds its own audit trail on top, logging every tool call.

We are migrating from ION to NetSuite (or the reverse). Does this still help?

Yes — arguably most during migration. Because bomrail reads both systems live, agents can diff records across them and flag drift daily, which turns migration validation from a big-bang reconciliation into a continuous check.

Related

Run ION and NetSuite?

That stack puts you at the front of the design-partner queue: white-glove setup, founder access, locked-in pricing — for honest feedback.

Apply for early access