Input boundaries
The RFQ builder rejects empty specifications, non-integer quantities, unsupported commercial terms, and FOB/CIF quotes without a named port. It validates again before generating an output.
Independent product · Verified release · 03 Nov 2026
Beyond a working demo: make the failure paths visible.
A concrete example from ProcureLink: turning a free supplier RFQ checklist into an actual browser-based document generator, with tests for invalid inputs, quotation assumptions, spreadsheet safety, and release behavior.
Build verification
309 routes
Static site build succeeded.
Test verification
22 / 22
Local unit and headless Chrome tests passed.
Production verification
Chrome E2E
Live form generation and invalid-input rejection verified.
01 · Business problem
Comparable requests before comparable prices.
Two suppliers may quote different materials, quantities, Incoterms, freight inclusions or sample conditions. Comparing their unit prices before the terms match creates a misleading decision.
The original ProcureLink site already offered a free RFQ checklist and quote calculator. This release closes a specific gap: buyers can now generate a usable supplier enquiry and an editable comparison sheet from the same structured inputs.
Scope: an independently developed public tool. This is not a commissioned client implementation, certified sourcing service, real supplier quote, or evidence of paid purchase orders.
02 · Actual output
Something the user can take away.
- 01
A structured English supplier enquiry that buyers can copy or download
- 02
An editable CSV worksheet for tracking quotation answers and outstanding questions
- 03
Explicit boundaries: an enquiry is not an order, a company registration is not a factory audit, and low quoted price alone is not delivered cost
03 · Engineering validation
What we tested besides the happy path.
Supplier quote comparability
An existing quote calculator compares unit prices, discounts, order quantity and freight share. Different supplier names are escaped before rendering as HTML.
Failure paths
Negative tests cover fractional/invalid quantity, malformed quote inputs and unsafe spreadsheet cell prefixes. An invalid form hides its previous result instead of presenting stale success.
Client data boundaries
The RFQ draft and CSV file are produced in the user's browser. No supplier content is uploaded by the free drafting form; the visitor decides if and when to send the enquiry elsewhere.
Independent browser checks
A separate headless Chrome test loads the built site, fills real form controls, generates a supplier RFQ, then changes quantity to an invalid value to verify rejection. The same check passed against the published production domain.
Validation evidence: isolated logic tests, existing tool-browser regression tests, built-page checks, a production deployment and a direct headless Chrome check of the public RFQ flow on 03 Nov 2026. The source repository is private, so this page does not pretend to provide a public code audit.
04 · Limits and what a real review requires
A passed test is evidence, not a sales result.
The tool is live. There is no verified customer payment, sourcing agreement or qualified lead attributable to this RFQ builder yet. The tests describe this implementation; they do not prove every future release or external supplier response will be correct.
An independent workflow or AI-agent review for someone else's system would need a separately agreed scope, permission to inspect representative evidence, an integration inventory, positive/negative/recovery tests, risk ranking and an actionable handover. Specific n8n, telephony or platform expertise would be verified before claiming coverage.
This case demonstrates transferable engineering practices — input discipline, explicit business assumptions, safe output, failure cases and evidence-based release — not proof of having delivered a commercial n8n contract.