Buyer guide Workflow

Sourcing Optimization Software for Complex Awards

When bids have interacting lots and constraints, test the feasible award choices before approving the supplier allocation.

  • Normalize bid data before optimization.
  • Keep mandatory constraints separate from preferences.
  • Record who approved the final allocation.
On this page

When does sourcing need optimization?

A straightforward RFQ may need a comparable bid table and buyer approval. Optimization becomes useful when a team must allocate several lots across suppliers under capacity, geography, service or risk limits. The model should reveal feasible alternatives and the cost of changing a rule.

Autonomous sourcing is a different decision: how much event work can progress without routine buyer intervention. A platform may support both, but an automated RFQ is not automatically an optimization problem.

Test event complexity before buying

Ask the vendor to solve the same fictional three-lot event with two eligible suppliers and one capacity cap.

Event type
Useful capability
Human control
Routine repeat RFQ
Template, supplier response, simple scoring and approval.
Event and award boundaries.
Multi-lot allocation
Feasible combinations under price, capacity and service limits.
Mandatory constraints and trade-off.
Changing assumptions
Recalculate when a supplier cap or requirement changes.
Approve the revised scenario and supplier communication.

Decision support versus execution

Market segment

RFx execution

Invite suppliers, capture revisions and normalize comparable responses.

RFx Automation
Example companies

Fairmarkit, Keelvar

Market segment

Award optimization

Model allocation constraints and compare feasible scenarios.

Scenario ModelingBid Evaluation
Example companies

Keelvar, Archlet

Market segment

Autonomous routine work

Apply approved event rules to repetitive sourcing while escalating exceptions.

Workflow Automation
Example companies

Fairmarkit, Keelvar

Pilot a three-lot award

Use fictional bids and no live supplier contact.

  1. Load source bids

    Include different units, a missing service item and one supplier capacity cap. Trace every normalized value.

  2. Change a binding rule

    Raise the resilience requirement. Show which scenarios become infeasible and the cost of the next valid choice.

  3. Authorize the award

    Record the chosen scenario, rejected alternative, override and approval before any supplier message or PO.

Published sourcing approaches

Published scope differs; test the proposed modules on the same event rather than assuming every RFx engine optimizes multi-lot awards.

Optimization demo questions

Inputs

Can a reviewer trace normalized bids to original supplier responses?

Rules

Which constraints are hard, and who may change them?

Scenarios

Can the team explain why one allocation was rejected?

Handoff

Where are award approval and supplier notice recorded?

FAQ

Is sourcing optimization the same as autonomous sourcing?

No. Optimization helps compare complex feasible awards; autonomy describes how much of the event workflow can run under approved rules.

Does a lower modeled cost prove savings?

No. The model depends on accepted bids, volumes, constraints and realized purchases.

Can a buyer use optimization for a simple RFQ?

Yes, but extra modeling only helps if the decision has meaningful interacting constraints.

Sources and further checks

This guide draws on published company profiles and their linked official websites. Check current product coverage, availability and implementation requirements with each company.

The content date reflects substantive guide edits, rather than a fresh verification of every company profile. Read our research methodology.

Workflow references

These sources explain process scope or a vendor’s own product approach. The comparisons and evaluation questions are ProcurementAI’s editorial guidance.

Official websites for the companies in this guide