Skip to content
ToolOracle CPQSales & pricing

1Click Configuration

Configure Oracle CPQ products from an Excel file

Type
Tool
Platform
Oracle CPQ
Category
Sales & pricing
Governance
Preview and approve before anything is written

The Problem It Solves

Who works with it

  • Product and pricing managers
  • CPQ administrators

Product and pricing teams keep their catalogues, options and rules in spreadsheets, then re-key them into Oracle CPQ one attribute at a time. It is slow, it drifts from the spreadsheet, and every catalogue change repeats the work.

1Click Configuration loads the spreadsheet directly. It validates the structure, shows what will be created or changed, and applies the configuration to CPQ in one run, so the spreadsheet stays the source of truth and CPQ stays in step with it.

What 1Click Configuration does

  • Loads products, attributes, options, rules and price lists from a structured Excel file

  • Validates the file against CPQ's model and reports every problem before anything is changed

  • Previews additions, updates and removals so the owner can approve the change set

  • Applies the configuration in one run and produces a log of every change

  • Re-runs safely: unchanged rows are skipped, changed rows are updated

How 1Click Configuration works

Four steps, from input to outcome.

  1. Upload

    The product owner uploads the Excel file in the agreed template.

  2. Validate

    The tool checks structure, references and rules against the CPQ model.

  3. Preview

    It shows exactly what will be created, updated or removed.

  4. Apply

    On approval it writes the configuration to Oracle CPQ and logs the result.

Works with

  • Oracle CPQ

What Data It Touches

  • Reads: the uploaded Excel file and the current CPQ product and pricing model
  • Writes: product, attribute, rule and price configuration in Oracle CPQ, with a change log
  • Never touches: quotes, orders or customer data

Security: Where the Data Stays and Who Can Access It

A governance layer routes every action through human approval workflows, and the action layer only executes JD Edwards transactions that have been approved. The connector layer is AIS, Orchestrator, REST APIs and the database.

See 1Click Configuration on your own data

A short demo against your environment, with your team in the room.