CPQ / product configuratorOracle NetSuite

Epicor CPQ (KBMax) and NetSuite: sending configured orders and BOMs to the ERP

Epicor CPQ, formerly KBMax, is a visual 3D product configurator that generates BOMs and sends configured orders to the ERP. Its connector supports database read and write, web service calls and a REST API, and the vendor page lists Oracle and NetSuite as order-data targets. Treat NetSuite as a custom integration to scope, not a plug-and-play listing.

How Epicor CPQ (formerly KBMax) connects to Oracle NetSuite

Epicor CPQ Connector (database, web service, REST)

The connector can read from and write to a database, call web services and use REST APIs. For NetSuite this typically means calling REST or SuiteTalk endpoints, or a SuiteScript RESTlet that you control.

NetSuite side: RESTlet or SuiteTalk

A RESTlet that accepts a configured-order payload and creates a sales order with the right item, BOM and options gives you one place to enforce validation. This pattern is common practice, not a vendor-certified package.

What data moves

FromToDataWhen
NetSuiteEpicor CPQCustomer, price list and item master data for the configuratorScheduled sync or on-demand lookup
Epicor CPQNetSuiteConfigured sales order with selected options and generated BOMQuote accepted or order submitted
Epicor CPQNetSuiteCustom item or assembly records for one-off configurationsConfiguration requires a new part number
NetSuiteEpicor CPQOrder number and status back to the quoteOrder created in NetSuite

Setting it up

  1. 1Decide the configuration to item strategyChoose whether configurations map to existing assembly items, to a parent item with option lines, or to new items created per configuration.
  2. 2Model the product rules in CPQBuild the 3D model, options, rules and pricing logic, and define the BOM output structure.
  3. 3Build the NetSuite receiving endpointCreate a RESTlet or use SuiteTalk to accept the order payload, authenticated with token-based authentication.
  4. 4Configure the CPQ connectorPoint the connector at your endpoint and map configurator fields to NetSuite sales order, line and custom fields.
  5. 5Load reference dataSync customers, price levels and item IDs so that configurator output references valid NetSuite records.
  6. 6Test with edge casesTest unusual configurations, discounts, multi-currency quotes and BOM revisions in a sandbox before production.

What usually breaks

  • !Generating a new item per configuration can bloat the NetSuite item list and slow searches; set naming and cleanup rules early.
  • !BOM components in CPQ that do not exist or are inactive in NetSuite cause the order to fail or create incomplete assemblies.
  • !Price mismatches when CPQ pricing rules differ from NetSuite price levels and currency conversion.
  • !Retries after a timeout can create duplicate sales orders unless the endpoint is idempotent with an external ID.
  • !Engineering changes to CPQ rules do not automatically update open orders, so revision control matters.
  • !Custom fields and tax or shipping fields required by NetSuite but unknown to CPQ block order creation.

A private AI layer across both systems

Failed order triage

When a configured order fails to land in NetSuite, an assistant reads the CPQ payload and the NetSuite error, explains the cause, such as an inactive component, and drafts the fix for approval.

Quote to order reconciliation

Compare configured quotes to resulting sales orders and BOMs, flagging price, quantity or option differences before production release.

Questions for sales engineering

Let sales and engineering ask which configurations ship most often, or which options cause rework, with read-only queries over order and BOM data.

When something else fits better

  • For simple option-based products, NetSuite's native item options and matrix items may avoid a CPQ tool altogether.
  • NetSuite-native or SuiteApp configurators fit better if you want the configuration rules to live inside the ERP.
  • If you already run Epicor Kinetic as your ERP, the CPQ pairing is more direct and better documented.

Frequently asked questions

Does Epicor CPQ officially support NetSuite?

The vendor page says the CPQ Connector uses database read and write, web service calls and REST, and lists Oracle and NetSuite as order-data targets. That is a capability statement, not a packaged certified connector, so expect to scope the NetSuite endpoint and mapping yourself.

What does CPQ send to the ERP?

Configured orders and generated BOMs. The details, such as whether it creates items, assemblies or option lines, depend on how you design the integration and how your NetSuite manufacturing setup handles custom assemblies.

Can this run on-premises?

NetSuite is cloud-hosted, so the ERP side is not on-prem. Epicor CPQ is also delivered as a cloud service. A private AI layer that reads order and BOM data can still be hosted inside your own network.

Pairing documented at kbmax.com/why-manufacturers-should-integrate-cpq-with-epicor/ . Epicor CPQ (formerly KBMax) is a product of Epicor; Netray is independent and not affiliated with either vendor.