Procurement · Deciding

Why this vendor,
on what comparison.

Three layers, computed separately and shown separately, so you always know which one you are looking at — and the reason you overrode any of them is stored beside the order rather than remembered.

A recommendation you cannot take apart is an instruction. All three layers stay legible.

The comparison

Three layers, kept separate.

DeterministicLowest per item and lowest total, straight from the quotes. No weighting and no interpretation — the number that is simply true.
WeightedPrice, quality and delivery against weights your tenant sets, forced to total a hundred so nobody can quietly tune it to a chosen answer.
QualitativeThe trade-off explained in words with a confidence attached — and never on its own.
The award

Cheapest overall is often nobody.

Split per lineOne vendor rarely wins everything. Splitting is normal buying, so it is a feature rather than a workaround.
Coverage previewWhat a split actually covers before you commit to it.
The override reason is storedWhich is the part that answers the question months later, usually from an auditor.
The record

Comparisons kept, not regenerated.

Comparison historyEvery comparison run on an inquiry, so the one you decided from is retrievable rather than reproduced approximately.
Vendor coverageWhich vendors can actually cover which lines, before you try to split an award across them.
Split preview then commitPreview what a split covers, then select it — two steps, because the preview is where mistakes are caught.
Nearby

Related capabilities.

RFQs and sourcing · Vendor management · Purchase orders

A decision with its reasoning attached.

The weights, the arithmetic and the override, all on the record.

Get started → See pricing