QAD Configurator

Overview

QAD Configurator is a rule-based configuration and guided-selling module for manufacturers that build or assemble products to order. It is most suitable for companies already operating QAD Enterprise Applications (QAD EA) and needing customer choices to become valid manufacturing and sales records. The module’s tight ERP connection is its central advantage, while the same dependency makes it a poor fit for buyers seeking an independent configurator.

QAD Inc., founded in 1979 and headquartered in Santa Barbara, positions the product within a broader manufacturing platform powered by agentic AI. QAD’s portfolio also covers adaptive ERP, connected workforce and supply chain functions, with support for industries including automotive, industrial manufacturing, consumer products, life sciences, food and beverage, distribution and high tech.

Key features

Sales teams work through questionnaires and configuration rules that gather requirements and validate answers during quote or order entry. The rules can create variant items, product structures and routings. Option pricing parts, quantities and units of measure can feed a calculated configuration price, so guided selling continues into costing and production preparation rather than ending with a choice list.

Configured requests can produce quotations, sales orders, bills of material and routings. Integrations cover QAD EA sales quote and order maintenance, item master, product structure, routing and item-site maintenance. For a QAD EA manufacturer, that linkage can remove duplicate entry and keep commercial and production definitions aligned. It is substantially less compelling when the company’s item, routing and order data live elsewhere.

The module supports multiple QAD EA domains, although some functions work across domain data. Native Windows screens run inside the QAD.NET UI, while the questionnaire uses HTML, JavaScript and AJAX. The AppServer tier processes web-service API requests, and an optional web-service tier can expose Configurator APIs as services. The documented default deployment places the databases on the QAD EA database server and application files on the QAD.NET AppServer. Progress or Oracle databases are supported according to the existing QAD EA implementation.

Pricing

QAD Configurator has one published plan, QAD Configurator, offered as an add-on module to QAD Enterprise Applications. It has custom pricing. No seat allowance, usage quota, trial term or renewal condition is stated, so buyers should obtain those commercial terms with a quotation. The add-on model suits an existing QAD EA customer budgeting for deeper configuration capability; it offers no clearly defined low-commitment tier for evaluating the product independently.

Platforms

The product is listed for web, Windows and API use, with hybrid deployment as its primary model. In practice, the Windows interface and QAD.NET AppServer installation matter for operational users, while web services provide an integration route for other applications. Database placement and supported Progress or Oracle environments tie the deployment to the customer’s QAD EA architecture rather than a generic cloud-only setup.

Who it's for

Choose QAD Configurator when your business routinely sells highly configurable or customer-customized products and QAD EA already contains the governing items, structures, routings and order processes. It is especially relevant to manufacturers that want sales questionnaires to generate production-ready outputs across multiple QAD domains. Look elsewhere if you need a standalone product, a self-service free tier or a platform-neutral implementation.

Pros and cons

Pros

Manufacturing-ready outputs: Configurations can become quotes, orders, bills of material and routings, reducing the gap between selling and execution.

Deep QAD EA integration: Item, structure, routing and site-maintenance connections favor organizations already standardized on QAD EA.

Flexible integration surface: API processing and optional web-service exposure support connected applications alongside the native Windows interface.

Complex-domain support: Multiple QAD EA domains accommodate organizations with distributed operational data.

Cons

ERP dependence: The add-on architecture limits its appeal for manufacturers without QAD EA.

Hybrid deployment burden: Database and AppServer placement can require coordination with an existing enterprise environment.

Opaque commercial entry point: Custom pricing and no stated trial, seats or quotas make initial comparison and budgeting harder.

Alternatives

Product Configurator Software is the broader category to review when you want to compare several approaches before committing to an ERP add-on.

ConvertSite Product Configurator is a better starting point for a low-cost web or API evaluation: its free plan costs nothing, includes 250 AI credits per month with a 100-per-day maximum, and starts publishing with a 7-day free trial.

Choose Expivi if you need Android, iOS, web and API coverage and want a freemium entry, with business terms tailored separately.

Apto.ONE suits buyers prioritizing open-source licensing, self-hosting and workflow adaptation across Linux, macOS, Windows and web.

Acumatica Product Configurator is the alternative to assess when Acumatica is your core business platform and deployment preferences drive a tailored quote.

3D Cloud Product Configurator is another paid, multi-platform option for teams wanting Android, iOS, web and API access.

Hulk Product Options is more suitable for a freemium web and mobile-oriented rollout, with a free development-store plan and a Basic plan at $10 a month.

ConfigCraft Suite fits teams wanting self-hosted or web deployment with a free tier covering guided configuration, simple option pricing, file uploads and shared configurations.

ShapeDiver is the alternative to consider when a freemium product needs API, macOS, web and Windows support, including a Startup plan from €199 a month on annual billing.

Verdict

QAD Configurator is the right choice for QAD EA manufacturers whose configurable products need validated selling choices to flow directly into orders, bills of material and routings. Its main reason to choose it is the depth of that ERP-native workflow. Its main reason to look elsewhere is the same platform dependence, compounded by custom pricing and a hybrid deployment that offer little flexibility for standalone or early-stage evaluations.