All articles

Engineer-to-Order, Configure-to-Order and Make-to-Order in Epicor Kinetic: How Each Shapes Your Quote-to-Job Setup

What each production mode asks of Kinetic, from the first quote to the job on the floor, and the setup decisions to make before go-live.

Gonzalo Nuñez

Gonzalo Nuñez

Chief Technology Officer


Engineer holding a tablet with a 3D exploded assembly view while an operations manager adjusts a custom machine frame on a manufacturing floor, with configured units and stocked parts bins in the background.

When a manufacturer evaluates Epicor Kinetic, the question of engineer to order versus configure-to-order versus make-to-order surfaces early and shapes the setup decisions that follow. The mode is not a label you apply after go-live. It determines what Kinetic must hold before a quote can go out: a finished method, a set of configurator rules, or an estimate built with engineering. Get that wrong in discovery and the system is configured around the wrong assumptions.

The sections below take each mode in turn, identify the Kinetic capabilities Epicor describes for it, and name the setup decisions an implementation has to resolve.

Why Your Production Mode Is an Implementation Decision

Every production mode places the moment of product definition at a different point relative to the customer order. That placement is what drives the implementation work.

With make-to-stock, the product is fully defined before any order exists. The BOM, the routing, the cost, the inventory position: all of it is in place before a customer calls. With make-to-order, the design is standard, but the job does not start until the order arrives. With configure-to-order, the product takes its final shape at the time of the order, within a set of rules the plant has already built. With engineer-to-order, the product is designed for the order: the BOM and the routing do not exist in their final form until engineering releases them.

The implementation implication: Kinetic needs different things from each of these before a quote can go out. For MTO, it needs a standard Method of Manufacturing (MoM) that sales can price from. For CTO, it needs configurator rules that produce a priced, manufacturable configuration on demand. For ETO, it needs an estimating structure that sales and engineering can build together, and a path for that estimate to become the job's method once the order is won.

Deciding which mode applies to which product family is a discovery-phase task, not something to revisit after go-live. Epicor describes Kinetic's production management as catering to make-to-order, configure-to-order, engineer-to-order and make-to-stock needs, including mixed-mode operations, so a plant that runs standard assemblies alongside custom-engineered products can run both models in the same system. But each family needs its own setup path, and those paths are built in sequence: methods first, then rules, then the estimate-to-job flow.

Make-to-Order: Standard Methods, Jobs Tied to Orders

For a make-to-order manufacturer, the product design is stable. What changes order to order is the quantity and the delivery date. Kinetic's implementation task for MTO is to get the methods right before go-live, because the method is what the quote prices from and what the job runs against.

The Method of Manufacturing

Epicor describes its Product Management capability as controlling "the process to ensure the right product is built using the right bill of material, routing, and specifications." The Method of Manufacturing (MoM) holds the bill of material (BOM) and the bill of operations (BOO) or routing for single and multilevel assemblies. Epicor notes that method accuracy supports both costing and scheduling, and that BOMs and BOOs are built with indented tree structures and drag-and-drop Method Management.

For MTO, that means every part that gets quoted needs a method behind it. If the method is missing or wrong, the quote price is wrong, and the job inherits the error.

Jobs and Order Changes

Epicor describes Job Management as covering planning, costing and tracking, with the ability to compare costs, link orders to jobs, and ensure that no order changes get missed. That last point matters in practice: a customer change on an open order has to reach the job. The setup decision is how that path works in your plant.

The Repetitive Side: Make-to-Stock and Kanban

A mixed-mode plant running both MTO and high-volume repetitive production can use Kinetic's Lean Manufacturing capability for the repetitive side. Epicor describes Kanban as supporting "manufacturing without work orders," which is a different flow from the job-based MTO model. Both can run in the same system; the setup defines which products follow which path.

Setup decisions for MTO: which parts carry a standard method; whether all methods are built new or migrated from an existing system; how a customer change on an open order reaches the job before it ships.

Configure-to-Order: The Configurator Rules Are the Product

For a configure-to-order manufacturer, the product does not exist as a finished design until a customer chooses their options. The design space is defined in advance, through rules. The rules are the product, and building them is the central implementation task.

How the Kinetic Configurator Works

Epicor describes the Kinetic configurator as supporting "on-the-fly configuration of highly customizable and dimensional products via a straightforward question and answer evaluation." Once a configuration is sold, manufacturing details flow to procurement and production. Epicor's Sales Management page states that "with product rules guiding the configuration process, anything configurable can be manufactured."

The configurator is integrated with the ERP, so a configured price and a configured set of manufacturing details move together. The question-and-answer structure is what sales uses at quoting time. The rules behind it are what engineering and operations have to build and maintain.

What the Setup Requires

The implementation work for CTO is not in the BOM or the routing in the traditional sense. It is in the rules: which options are valid in combination, how a configured price is calculated from those options, and what a completed configuration produces downstream. That downstream output is what becomes the job's method when the order is won.

The scope of the configurator, which products it covers and which it does not, is a decision that shapes the entire setup.

For products that fall outside the configurator's scope, or for configurations that need CAD output or visual presentation, the next section covers those options. For questions about who should own the rules and how to structure them before go-live, the Catalog to CPQ session covers that ground directly.

Setup decisions for CTO: which products enter the configurator and which do not; which options and combinations become rules; how a configured price is built; what a configuration produces for procurement and production.

Engineer-to-Order: When Every Quote Is a Project

Engineer to order is the mode where the product does not exist until the customer's requirements define it. There is no standard method to price from, no rule set to run through. Sales and engineering have to build the estimate together, and that estimate has to be structured carefully enough to become the job's method when the order is won.

Estimating and Quotation Management

Epicor describes its Estimating and Quotation Management capability as generating and tracking customer or prospect RFQs "from the time of receipt until an order is placed," with estimates that produce "more accurate pricing and lead time forecasts." Sales and engineers collaborate on estimates "based on customer needs and real-time data." The estimate is where ETO quoting lives in Kinetic, and it is the bridge between what the customer asked for and what the plant will build.

Epicor describes accurate estimates as covering "quoting through to production with specifications in the Method of Manufacturing (MoM)," supporting single and multilevel assemblies with BOM and bill of operations (BOO) or routing. Method accuracy supports both costing and scheduling. That means an ETO estimate is not just a price: it is the beginning of the production record.

Engineering Review and Approval

The engineering workbench is where engineers manage modification, review and approval of assemblies. That handoff from estimate to released method is a setup decision: when does engineering release the method, and what triggers the job?

The Quote-to-Job Path

For ETO, the path from a won quote to a running job is the critical flow to design in discovery. How the estimate is structured, when engineering releases the method, and how a change after the quote reaches the job before production starts: these are the decisions that determine whether the system supports the work or fights it.

See how TCP implements Epicor Kinetic

Setup decisions for ETO: how an estimate is structured so it can become the job's method; when engineering releases the method; how a won quote becomes an order and a job; the path for work that changes after the quote.

When the Kinetic Configurator Is Not Enough: Epicor CPQ and Aleran

The Kinetic configurator handles question-and-answer configuration within the ERP. For products and sales channels that need more, Epicor and its partners offer two directions.

Epicor CPQ

Epicor states that Epicor CPQ extends the configurator's capabilities, and describes it as "a one-stop-shop for manufacturers of engineer-to-order (ETO) products." What it adds, as Epicor describes it: visual configuration in 2D, 3D and augmented reality; a no-code rule engine built by dragging blocks; CAD files generated from the configuration (AutoCAD, SolidWorks, PTC Creo); auto-generated BOMs and production documents; and quotes as MS Word or PDF with images, BOMs and pricing, pushed to CRM, ERP or PLM systems via REST APIs.

The signals that point toward Epicor CPQ are practical: buyers or sales reps who need to see the product visually before committing; configurations that require a CAD file per order; or proposals that need to carry images, BOMs and pricing in a formatted document.

Aleran

Aleran Connected Commerce unifies CPQ and digital commerce for manufacturers of configurable products. Aleran describes its platform as built for complex products, with automated quoting and ordering and integration with the ERP. It complements Epicor CPQ for manufacturers selling through more than one channel.

The signal for Aleran is channel reach: selling through more than one channel alongside the ERP-native flow.

For a deeper look at when CPQ extends the configurator and how to structure product data before that decision, the Catalog to CPQ session covers those questions directly. Aleran's capabilities are on the Aleran platform page.

The setup question here is not which tool wins. It is whether the Kinetic configurator alone covers the products and channels in scope, or whether a CPQ layer needs to be designed into the implementation from the start.

Where AI Fits: Reading the RFQ Before the Quote

Before any mode-specific work begins in Kinetic, someone reads the customer's request. That request arrives as a PDF, a scan, a photograph, a spreadsheet, a Word file or plain email text. The reading step happens before the estimate, before the configurator, before the method. It is where information enters the system.

Fluent describes its quote entry automation as reading those incoming RFQs, resolving customer, parts, units and revisions against live Epicor data, and drafting the quote for a person to review and process into Kinetic. The draft is a starting point for the person who knows the job, not a replacement for the method, the rules or the estimate. It feeds them.

Fluent's guide offers a comparison of quoting software types and where AI agents fit relative to CPQ and ERP-native quoting. To see the agents build a Kinetic quote live on November 19, the webinar runs at 2 PM ET.

Decisions to Make Before Kinetic Goes Live

The mode analysis above points to a set of decisions that have to be resolved in discovery, before configuration begins. Working through them in order keeps the implementation from having to reverse course.

  1. Production mode per product family. Which families run MTO, which run CTO, which run ETO, and which run MTS? A mixed-mode plant needs a clear answer for each family before any setup work starts.
  2. Standard methods to build or migrate. For MTO families, which parts carry a standard Method of Manufacturing? Are those methods built from scratch, migrated from an existing system, or some combination? The MoM is the foundation the quote and the job both depend on.
  3. Configurator rules and pricing to build and test. For CTO families, what options and combinations become rules? How is a configured price calculated? What does a completed configuration produce for procurement and production? Rules need to be tested against real orders before go-live.
  4. Estimate structure for ETO and the quote-to-job path. How is an ETO estimate structured so it can become the job's method? When does engineering release the method? How does a won quote become an order and a job?
  5. The path for changes after the quote. For both ETO and MTO, a customer change on an open order has to reach the job. The path for that change is a setup decision, not a default.
  6. Whether a CPQ layer is needed. Does the Kinetic configurator cover the products and channels in scope, or does the implementation need to design Epicor CPQ or Aleran in from the start?
  7. Where RFQs are read and by whom. Before the estimate or the configurator runs, someone reads the customer's request. Is that a manual step, or does an AI agent draft the quote for review?
  8. BOMs and routings in the data migration. Items, BOMs and routings are part of the migration scope alongside customers, suppliers and open orders. The accuracy of the migrated methods determines whether the first live quotes price correctly.

When Ternova, a family-owned manufacturing group headquartered in El Salvador, went live on Epicor Kinetic Cloud with TCP, the guiding principle was to use most of Kinetic out of the box and customize only what was truly needed. That principle applies directly to configurator rule scope and method design. For a fuller view of the phases involved, the Epicor Kinetic implementation guide covers discovery through go-live.

TCP is an Epicor Platinum Partner and has built quote-to-job flows for engineer-to-order manufacturers and configurator rules and pricing for configure-to-order manufacturers. Watch Fluent's AI agents build a Kinetic quote live on November 19 to see how the RFQ reading step fits into the full flow.

If your quotes are still built in spreadsheets before anyone touches Kinetic, TCP can set up the methods, rules and estimates your production mode needs, so the quote and the job run on the same data.

See how TCP implements Epicor Kinetic

Frequently Asked Questions

Epicor describes Epicor CPQ as supporting configuration and buying by sales reps, dealers, distributors, partners and web visitors, with unique pricing workflows for dealers and distributors. Aleran Connected Commerce addresses the channel side: Aleran describes customer portals that reflect roles within a customer account and supports multi-storefronts for manufacturers selling through more than one channel. For manufacturers whose channel partners need to configure and price independently, the combination of Epicor CPQ for configuration rules and Aleran for commerce and portal access covers both the quoting and the ordering side of the channel workflow. More detail is on the Aleran platform page.

Configure-to-order (CTO) selects options within a set of rules the manufacturer has already defined. The product design space is fixed; the customer chooses within it. Engineer-to-order (ETO) designs the product for the specific order. There are no predefined rules that produce the final BOM and routing: engineering builds them from the customer's requirements. In Kinetic, CTO relies on configurator rules built before go-live; ETO relies on an estimate that sales and engineering build together for each order, which then becomes the job's Method of Manufacturing once the order is won.

Make-to-stock (MTS) builds to a forecast and holds finished goods in inventory before any customer order exists. The ERP manages inventory levels, replenishment and demand planning. Make-to-order (MTO) builds after the customer order arrives, against a standard design held in the Method of Manufacturing. The ERP creates a job tied to the order and tracks it from order through production. Kinetic also supports Lean Manufacturing with Kanban for repetitive production, which Epicor describes as "manufacturing without work orders," giving mixed-mode plants a separate flow for high-volume MTS lines alongside job-based MTO production.

Part on the fly is a process Epicor describes as supporting products only made once. Epicor lists it among its make-to-order capabilities, alongside configure price quote for customer-driven configurations. It applies to one-off engineered designs: a product built to one customer's specification that the plant does not expect to build again. Epicor also publishes material on the advantages of a job-centric ERP with part on the fly. Whether a one-off design runs as a part on the fly or carries a standard part record is a decision to settle when methods are planned in discovery.

Epicor describes the engineering workbench as the place where engineers manage modification, review and approval of assemblies. It supports full revision control, engineering change orders (ECOs) and BOM maintenance, along with what-if cost rollups and the ability to place parts on hold. Routing maintenance is also managed through the workbench. Epicor notes that attachments linked to end products and components flow to production planning and the production floor at each revision. This means a released engineering change carries its documentation with it through the system rather than requiring a separate distribution step.

Yes. Epicor describes CADLink by QBuild Software as a tool that lets engineers push BOM revisions to Kinetic directly from their CAD environment. Rather than exporting a BOM from CAD and re-entering it in the ERP, engineers work in their CAD tool and the revision moves into Kinetic. This is relevant for ETO and CTO manufacturers where the BOM originates in a CAD system and changes with each engineering revision. The integration reduces the manual step between the engineering record and the production record in Kinetic.

Epicor CPQ was formerly KBMax. Epicor acquired KBMax in May 2021 and announced it would market the software under the Epicor brand. Epicor CPQ is a separate product that extends Kinetic's built-in configurator with visual configuration in 2D, 3D and augmented reality, a no-code rule engine, CAD file generation and automated BOM and production document output. It is separate from the question-and-answer configurator built into Kinetic's ERP and is positioned by Epicor as a solution for engineer-to-order manufacturers.

Fluent describes its quote entry automation as reading incoming RFQs as PDFs, scans, photographs, spreadsheets, Word files and plain email text, and drafting the quote for a person to review. Fluent also notes that where a line carries a configuration, it works the Epicor product configurator and reads the configured price back onto the line. The result is a drafted quote that reflects both the customer's part and quantity information and the configured price, ready for a person to review and process into Kinetic. For a live demonstration, the webinar on November 19 shows the agents working in a Kinetic environment.

Yes. When CRM and Kinetic are both in scope, the customer master, pricing and quote flow need to be designed once so they work consistently across both systems. Designing them separately creates a re-keying problem: a quote built in CRM has to be re-entered in Kinetic when it becomes an order. Designing them together means quotes that become sales orders without re-keying. This is a discovery-phase decision, not a post-go-live integration task. The Epicor Kinetic implementation service describes how the CRM and AI plan is designed alongside the ERP setup.

Epicor describes Kinetic's Production Management as including Quality Management with inspection workbenches and nonconformance records. For manufacturers who need more, Epicor QMS adds nonconformance reporting and audits. These controls apply regardless of production mode: a configured product and an engineered product both move through production and can be subject to inspection and nonconformance tracking. Nonconformance records document the issue and its resolution. The Epicor Kinetic implementation service covers scoping quality setup alongside the method and configurator work.

Read more