"E-procurement" gets sold as a software category. Anyone who actually buys for a living knows better: there isn't one job to digitize, there are five, chained together. A need appears, prices get requested, quotes come back and get compared, an order goes out, a delivery gets chased. Break any link in email, and the rest of the chain collapses into spreadsheets.
This guide walks the whole chain — what happens at each step, where it usually snaps, and what it looks like when the steps share one backbone.
1. The request: procurement's invisible first step
Purchasing doesn't start in the purchasing department. It starts on the production floor, in a project plan, or in a stock count that came up short. And that's exactly where things first go wrong: the need arrives as a hallway conversation, a voice note, or an email with the subject line "URGENT". Half the specification is missing; the quantity is a guess.
In a digital flow, the request is a structured record from minute one — line items, quantities, units, target dates. Every later step builds on that record instead of retyping it.
2. The RFQ: one request, many suppliers
The classic way to ask for prices: paste the same request into six emails, track six separate threads, and keep "who has answered?" in your head. If the request has ten lines and three suppliers reply in PDF, one in Excel, and two in prose, the comparison becomes its own project.
Done properly, the RFQ is one document sent to many suppliers at once. Each recipient gets their own copy; sent, viewed, and responded states are tracked per supplier. If the request changes, the document is versioned — "which revision did you quote?" stops being a question.
Suppliers also get a real place to answer: a portal that carries your brand. They type the quote in; you stop excavating data from attachments.
3. Quote comparison: where the decision actually happens
This is the heart of procurement — and the step spreadsheets damage most. Hand-built comparison tables mix unit prices with totals, squeeze three currencies into one column, and bury quantity breaks in footnotes.
Structured quotes dissolve the problem: price, lead time, and terms arrive as fields, so putting them side by side takes seconds. Price breaks live on the quote itself; each document keeps its own currency while reporting converts to one. And when the decision is made, the reasoning is on the record — when someone asks "why this supplier?" six months later, nobody has to do email archaeology.
4. The order: the discipline behind one click
If the winning quote is known, why does writing the PO take half an hour? Because in the classic flow, the PO is a separate Word template with no link to the quote. Lines get carried over by hand — and damaged in transit.
In an end-to-end flow, the winning quote converts to a purchase order in one click. Lines, prices, and terms are inherited; the moment the document is sent, its content freezes into an immutable snapshot. The number, the PDF, and the history all live on the record.
5. Delivery: the forgotten last step
The silence after the PO goes out is procurement's most expensive habit. "When will it arrive?" gets asked by phone; the answer gets written somewhere nobody else can see.
End to end, delivery is a status on the order: confirmed, processing, shipped, delivered. The supplier updates progress in the portal; stock moves with the confirmed order. And if your counterparty runs Gloyd too, documents are created on both sides automatically via O2O — neither of you plays data-entry department for the other.
What changes when the chain is one piece
Each step looks survivable on its own. The difference shows when the chain is unbroken:
- Speed: RFQ rounds drop from days to hours, because waiting, copying, and reminding disappear.
- Traceability: Every document from request to delivery stays linked; the whole story fits on one screen.
- Institutional memory: Price history, supplier behavior, and decision rationale live in the company's records — not in someone's inbox.
E-procurement projects get postponed because they sound like "a big software migration." The actual job is smaller: connect five steps to one backbone. That's a start-this-afternoon size of project, not a quarter-long one.
If you want to see the first step concretely, the e-procurement solution page walks the entire flow — supplier portal included.
