You are quoting a cell, not a robot. The arm is one line item. The deliverable is the whole station.
The customer does not buy a six-axis arm. They buy the ability to weld, palletize, or assemble at a target cycle time. If the gripper, the vision system, or the safety zone is wrong, the cell does not run. The quote has to get every layer right.
Five layers of a cell quote
Every robotic cell quote has five layers. Miss one and the cell does not start.
Sales teams often price the robot and leave peripherals to engineering. By then the customer already has a budget number that does not include what the cell actually needs.
Robot arm
Payload capacity, reach envelope, axis count, and mounting orientation define whether the arm can physically do the job. A 6 kg robot quoted for a 5.8 kg part leaves no margin for the gripper weight. The cell stalls at full extension.
End-effector
Grippers, welding torches, dispensing heads, or deburring spindles attach to the arm flange. Each has a weight, a communication protocol, and a mounting interface. If the end-effector protocol does not match the controller generation, the integration fails at commissioning.
Vision and sensing
Camera systems, force-torque sensors, and laser scanners guide the robot or inspect the output. They add weight to the wrist, require controller I/O, and depend on lighting conditions. An unplanned vision system changes the cycle time calculation and the safety zone.
Safety enclosure
Light curtains, area scanners, fencing, and interlocked gates define the safety zone. Adding a second robot, a conveyor, or a manual load station changes the zone geometry. If the safety layout is not part of the quote, the integrator redesigns it on site at the OEM's cost.
Integration labor
Programming, commissioning, I/O wiring, PLC integration, and runoff hours are not optional. They scale with cell complexity. A two-robot cell with vision and conveyor infeed is not twice the labor of a single-arm pick-and-place. The labor estimate has to reflect the actual scope.
Where cell quotes break
Three configuration failures that surface after delivery
A slow quote loses a deal. A wrong cell configuration loses the margin on the rework and the customer's trust in the next project.
Payload calculated without the end-effector
The robot's rated payload is 10 kg. The part weighs 7 kg. The quoted configuration looks correct. But the gripper weighs 4.5 kg. At full reach the effective payload drops further. The robot faults on every cycle. Engineering knew the constraint. The quote tool listed the robot and the gripper on separate lines without checking the combined weight.
Safety zone drawn for one robot, cell ships with two
The original quote covered a single robot with a light curtain on the operator side. During the sales process the customer added a second arm for loading. Nobody recalculated the safety zone. The cell arrives, the risk assessment fails, and the integrator installs additional fencing and scanners before the cell can run. The cost was not in the quote.
Controller I/O exhausted by peripherals nobody counted
The controller has 32 digital I/O points. The robot arm uses 8. The gripper uses 4. Then the quote adds a conveyor interface (6), a vision trigger (4), a part-present sensor (2), and safety interlocks (10). That is 34. The controller needs an expansion module nobody priced. The cell cannot be wired as quoted.
Who owns each layer
Sales configures. Application engineering validates. The integrator delivers. CPQ keeps them on one version.
When each role works in their own spreadsheet, the customer gets a quote that does not match what ships.
| Cell layer | Sales rep | Application engineer | Integrator partner |
|---|---|---|---|
| Robot arm | Selects model and payload class from the catalog | Validates reach, cycle time, and mounting against the application | Confirms floor layout and foundation requirements |
| End-effector | Adds the standard gripper or tool option | Checks protocol compatibility, flange type, and weight budget | Sources or builds custom tooling if standard options do not fit |
| Vision / sensing | Includes or omits based on customer request | Specifies camera model, lighting, and resolution for the part geometry | Installs, calibrates, and integrates with the PLC program |
| Safety enclosure | Quotes standard fencing package | Runs risk assessment and defines zone geometry for the full cell | Installs physical barriers, scanners, and interlocked gates on site |
| Integration labor | Estimates hours from a rate card | Defines scope: I/O count, PLC complexity, runoff criteria | Executes programming, commissioning, and customer runoff |
Same enquiry, two outcomes
The same four-robot palletizing cell, quoted two ways
With Mercura CPQ
- Cell layers linked: adding a second robot recalculates payload budget, I/O count, and safety zone automatically
- End-effector compatibility enforced by controller generation and flange type
- Integration labor scales with actual cell complexity, not a flat percentage
- One configuration document shared by sales, engineering, and the integrator
- The customer sees what the cell includes before the order is placed
Spreadsheet or ERP line items
- Robot, gripper, vision, and safety quoted as independent lines with no dependency checks
- Payload budget checked manually after the quote is sent, if it is checked at all
- Integration hours copied from the last similar project, regardless of scope differences
- Sales, engineering, and the integrator each maintain their own version of the configuration
- Mismatches surface at order review or, worse, at commissioning on the customer's floor
Questions robotics sales teams ask
Frequently asked questions
Does CPQ replace our application engineers?
No. Application engineers define the rules: which payload class fits which application, which controller supports which end-effector protocol, how safety zones change with cell layout. CPQ stores those rules and applies them at quote time so sales and channel partners do not need to call engineering for every configuration. Engineering reviews edge cases, not routine quotes.
We sell through integrators and distributors. Can they use the same tool?
Yes. Channel partners access a guided configuration that enforces the same rules as your internal sales team. They can select a robot, add peripherals, and see the valid options for each combination. Pricing tiers and margin rules can differ by partner without exposing internal cost structures.
Our cells are engineer-to-order. Is CPQ relevant?
CPQ does not eliminate engineering. It handles the configurable portion of the cell: selecting the robot, matching the end-effector, sizing the safety enclosure, and estimating integration labor within defined parameters. The engineer-to-order scope (custom fixturing, unique PLC programs, non-standard materials) stays with engineering. CPQ keeps the standard layers consistent so engineering focuses on what is actually custom.
How does CPQ handle multi-robot cells?
Each robot in the cell is a configuration block with its own payload, reach, and end-effector. Adding a second robot triggers recalculation of the safety zone, the total I/O requirement, and the integration labor estimate. The system enforces that the combined cell does not exceed controller capacity or create overlapping work envelopes without a collision-avoidance note.
What about legacy robots and discontinued models?
Products can be marked as available for service quotes but hidden from new-cell configurations. Spare parts and retrofit options remain accessible without exposing discontinued models in the standard configurator. This prevents sales from quoting a model that cannot be manufactured while keeping the service pipeline intact.
When is CPQ not the right tool for a robotics OEM?
If every cell you sell is fully custom with no repeatable robot or peripheral selection, CPQ adds overhead without reducing configuration effort. CPQ works best when you have a defined catalog of robots, a set of compatible peripherals, and recurring cell architectures where the same selection logic applies across projects. If your quoting is pure engineering estimation with no catalog component, a project-estimation tool is a better fit.
Not ready for a call? Watch a short product walkthrough or ask a question below.
Request a CPQ demo