Put every supplier offer beside the same buying decision.
Structure the requirement once. Record eligible bids against the same price, timing, and service fields. Review the disclosed comparison, then choose the supplier yourself. Delivery, receipt, and payment remain separate evidence.
The Buying Contract
One comparison is useful only when the buying question is the same.
01
Align the requirement
Name the item or service, quantity, unit, timing, requirements, budget range, and decision owner before comparing offers.
02
Verify the alignment
A shared record shape does not make mismatched scope, currency, taxes, shipping, units, or supplier statements equivalent.
03
Preserve the decision
The comparison assists an authorized person. Award, external delivery, receipt, and payment evidence remain separate events.
Request To Commitment
Comparable bids converge. Authority does not disappear.
The workflow prepares an inspectable decision, then preserves the person who made it and the records created next.
Illustrative managed flow. Supplier delivery, bid entry, permissions, and supporting evidence depend on the configured engagement.
01
Scope the request
Record the buying need and the fields every eligible bid must answer.
02
Publish the internal record
Move the RFQ into bidding. Supplier delivery uses the manual or configured external handoff defined for the engagement.
03
Record structured bids
Capture bid amount, timeline, the recorded SLA-confidence value, and supporting terms. A reviewer still verifies whether the commercial terms are complete.
04
Compare eligible offers
Rank active bid records with fixed weights: 50% price, 25% timeline, and 25% recorded SLA confidence. Review scope and terms outside the score.
05
Award one bid
An authorized person reviews the terms and chooses the supplier. The ranking does not make the decision.
06
Write the commitment
After award, the workflow creates or reuses a contract draft and, when project- or task-linked and the downstream write succeeds, records a contracted cost item.
Comparison Mandate
A score is assistance, not procurement judgment.
The current comparison ranks active records by bid amount, timeline, and the recorded SLA-confidence value. It does not validate that value, identify mismatched terms, or make unlike commercial terms equivalent; the reviewer must do that outside the score.
- Comparable
- Equivalent scope, currency, quantity, unit, taxes, shipping, and commercial terms.
- Disclosed
- 50% price, 25% timeline, and 25% recorded SLA confidence.
- Reviewable
- A reviewer inspects scope, currency, quantity, unit, taxes, shipping, and supporting terms outside the score before award.
Evidence After Award
Each state proves one thing—not the next thing.
A contract draft is not a signature. An approved PO is not supplier receipt. A recorded delivery is not a reconciled inventory movement or paid invoice.
01
Awarded
One bid was selected and the decision record identifies who made the award.
02
Contract drafted
The selected terms were carried into an internal draft—not represented as signed.
03
PO authorized
A purchase order passed its configured approval state. Delivery still needs its own path and evidence.
04
Quantity received
Partial or full receipt was recorded against PO lines. Inventory movement remains a separate ledger action.
Separate Inventory Branch · CTO+
Low stock can prepare a decision. It cannot place the order.
Recorded movement → deterministic recommendation → approval-required PO draft
When inventory and auto-suggest settings are enabled, daily rules can group urgent reorder recommendations into purchase-order drafts. They do not create RFQs, choose suppliers, or send orders. Approval remains required.
Access & Authority
Supplier access and award rights are named, not assumed.
The engagement records who controls supplier contacts and external accounts, who may send requests and award purchases, and which records are copied into Connected Spaces.
Your business data is exportable in documented, usable formats. Customer-specific templates, mappings, dashboards, integration code, and documentation transfer only as identified in the agreement. Supplier systems, payment rails, licensed inputs, third-party services, hosting, and Connected Spaces shared code remain separate.
Procurement questions, answered.
What the current workflow records, what remains external, and where approval stays explicit.
Connected Spaces supports structured RFQ records, bid comparison, authorized human award, contract and cost commitment records, a separate purchase-order lifecycle, and configured inventory reorder recommendations. Availability depends on the modules, permissions, records, and implementation scope in use.
Not by itself. Publishing changes the internal RFQ into its bidding state. Supplier delivery and response collection require the manual or configured external handoff defined for the engagement, plus separate evidence that the request was delivered.
No. Bids use a common record shape, but a reviewer must align scope, currency, quantity, units, taxes, shipping, and commercial terms before treating their scores as comparable. The score does not identify or validate those differences.
The current comparison deterministically ranks active bid records using fixed weights: 50% bid amount, 25% timeline, and 25% recorded SLA confidence. An authorized person reviews scope and underlying terms outside the score, then awards one bid; the ranking does not choose the supplier.
After an award commits, the downstream workflow creates or reuses a contract draft. When the RFQ is linked to a project or task and the downstream write succeeds, it also records a contracted cost item. The award does not by itself sign a contract, send a purchase order, execute a payment, or update inventory.
No. At CTO+, a configured inventory foundation can record stock movements, calculate deterministic reorder recommendations, and optionally prepare purchase-order drafts grouped by supplier. Approval remains required, and drafts are never auto-sent.
Not in the current shared workflow. PO receiving records partial or full quantities and updates the PO state. Inventory movements are recorded separately through the inventory ledger, so the two records should not be treated as reconciled without that step.
No universal payment or quote-to-invoice reconciliation rail is implied. Cost records can hold entered costs, invoice or receipt references, payment lifecycle notes, and budget fields. A recorded payment status is not proof that Connected Spaces executed or verified the payment.
The engagement records who controls supplier contacts and external accounts, who may send requests and award purchases, what records are copied into Connected Spaces, and the export and retention terms. Customer-specific templates, mappings, reports, integration code, and documentation transfer only as identified in the agreement. Supplier systems, payment rails, third-party services, hosting, and Connected Spaces shared platform code remain separate.
Continue The System