Carry estimate intent into procurement
Record supplier requests, quotations, commercial comparisons, and package tracking without dropping the quantities, scope, and assumptions that shaped the estimate.
A typical disconnected buying path
The commercial problem is not that spreadsheets exist. It is that each hop below can drop quantity, exclusion, and revision context.
- 1Estimate
- 2Export workbook
- 3Email RFQs
- 4Supplier files
- 5Manual comparison
- 6Purchase decision
RFQ lifecycle in Infrenta
The procurement workspace records vendors, RFQs, quotations, comparison, and package tracking on the project.
- 1Scope / quantity
- 2RFQ
- 3Supplier quotations
- 4Commercial comparison
- 5Selection
- 6Package tracking
Why landed cost belongs in the comparison
Quote comparison can include freight and duty inputs when they are present. Duty figures come from stored reference data and entered assumptions—not a live customs determination.
Commercial / landed cost structure
- Supplier quoted price
- Freight
- Duty / tariff (when entered)
- Other applicable costs
Commercial / landed cost used for comparison
Who uses it
Procurement managers and buyers who need RFQ and quotation history attached to project quantities. Estimators and project-controls leads benefit when awarded values remain comparable to the baseline they already issued.
The practical task
Turn an issued estimate revision into RFQs, quotation comparison, and a recorded commitment on the same lines.
What you do and produce
You create an RFQ against the approved quantity, compare supplier responses, and record the award. Award remains a buyer decision. The output is a compared package and a commitment — not an auto-award.
How that output helps another team
Project Controls can roll the committed value against the issued baseline. Execution later records deliveries against the same material identity.
Example
On the public Red Mesa demonstration, RFQ RMS-FND-004 requests 12,400 EA of driven posts — the same quantity the estimate issued. A person selects the supplier. See the product tour.
Next step
See module pricing, or read Procurement documentation.
Why disconnected buying loses the estimate
A common path is: issue an estimate, export a workbook, email RFQs, collect supplier PDFs, compare bottom lines, then purchase. Each hop can change the question. Suppliers price different inclusions. Exclusions hide in footnotes. Quantities move after the RFQ is already in the market. Freight and duty sit outside the unit price. Quote revisions become hard to line up. The purchase decision no longer points at the issued estimate revision.
Infrenta procurement is the workspace that turns approved commercial scope into sourcing activity on the same project: vendors, RFQs, quotations, comparison, and package tracking.
Procurement organizes RFQs and quotations against approved project scope. Customs treatment remains a professional determination outside the workspace.
Who this is for
Procurement managers and buyers who need RFQ and quotation history attached to project quantities—not a personal inbox. Estimators and project controls leads benefit when awarded values remain comparable to the baseline they already issued.
Suppliers and RFQs
Vendors are company-scoped records: identity, qualification, and performance inputs that affect whether a vendor can be invited to an RFQ. Qualification exists so a package is not sent to an unqualified fabricator by habit.
The RFQ engine supports generating an RFQ number, creating an RFQ, issuing it, inviting vendors, and closing it. Response rate and late responses are measurable. An RFQ should point at a package whose quantities match the approved estimate revision.
Why supplier quotes need scope-level comparison
Comparing only the bottom-line quote value hides the commercial question. Two suppliers can return the same total while pricing different quantities, coatings, freight terms, or lead times.
Infrenta quote comparison can include:
- currency normalization
- quoted price and a normalized price
- landed-cost calculation when freight, insurance, and duty inputs are present
- lead-time (delivery days) comparison
- flags for incomplete submissions
- unusual-bid detection
Evaluation weights and award-recommendation helpers exist for structured scoring. Award and purchase issuance remain a buyer decision.
Educational note, separate from implemented fields: buyers still need to read scope inclusions and exclusions in the supplier text. The comparison matrix does not invent missing scope language.
Landed cost is not just the mill or factory price
Procurement decisions are often driven by more than supplier base price. When inputs are entered, landed cost can combine quoted price with freight, insurance, and a duty percentage.
Trade & Tariff can inform origin and duty assumptions from a stored reference catalog. Figures are not a live customs feed, and the workspace does not automatically classify goods or determine anti-dumping treatment.
This is not legal, customs, or tax advice. Classification, origin rules, and duty rates can change and can depend on facts that only a licensed customs professional and your counsel can confirm.
Connected workflow
Estimating supplies the issued quantities and assumptions. Procurement should buy that revision. Awarded values should become commitments that Project Controls can roll up. Deliveries later appear in Execution as logistics events—not as a second, unrelated material list.
Steel Intelligence and Trade & Tariff affect what a landed steel or module package should even ask for. If those assumptions diverge from the RFQ, comparison is theater.
The estimate should not become a detached workbook the moment purchasing starts. That continuity is structured workflow and shared records—not claimed as perfect automatic synchronization.