Appearance
The things that move
Three objects carry the state of every deal. Learn these three and you can read any screen in any app.
| Object | One sentence | Owned by |
|---|---|---|
| Request | What the buyer needs, before anyone has committed to supply it. | Buyer |
| Purchase order (PO) | A contract with one supplier for some of the request's lines. | Buyer and supplier together |
| Correction | A proposed change to a PO that the other side must accept. | Whoever proposes it |
Request
A request is a list: lines of materials with quantities, a site to deliver to, and a date they are needed by. It is where sourcing happens.
Draft→Sourcing→Awaiting approval→Approved→Ordered · n POs→Closed
- It stays a Draft while the buyer builds it.
- Sourcing means suppliers are being chosen, by LCPP's proposal, by hand, or through a request for quotes.
- If the buyer's company requires it, it waits in Awaiting approval.
- Issuing it creates purchase orders, and it becomes Ordered. When all its orders are finished it is Closed.
One request can produce several purchase orders, one per supplier.
Purchase order
The purchase order is the heart of the platform. It is the agreement between one buyer and one supplier, and it moves through the whole flow.
Issued→Awaiting confirmation→Confirmed/Partially confirmed → correction/Rejected
→Awaiting payment→PaidorPay on delivery→Preparing→Dispatched/Ready for pickup
→Delivered / Picked up→Receipt pending sign-off→Signed off/Discrepancy → correction or return→Invoiced→Closed
Read it in three rows:
- Commitment. The supplier confirms in full, partly, or rejects. A partial confirmation comes with a correction for what changed.
- Payment and fulfilment. Paid up front or paid on delivery; then prepared, dispatched or made ready for pickup.
- Receipt and close. The buyer checks the goods and signs off. Problems found here become a correction or a return. The supplier invoices and the order closes.
A PO carries a version number. Every accepted correction makes a new version, so anyone can see what was originally ordered and what changed.
Correction
A correction is the only way a purchase order changes after it is issued. Either side can propose one: the supplier when confirming ("I can send 8, not 10"), or the buyer at sign-off ("two arrived broken").
Proposed→Accepted/Rejected/Countered→Applied · PO v2· or →Escalated · dispute with Ops
- The other side accepts it, rejects it, or counters it, for example by offering a refund instead of a replacement.
- An accepted correction is applied: the PO moves to its next version with new quantities, prices or lines.
- If the two sides cannot agree, either can escalate it to a dispute, and platform staff mediate.
Supporting objects
These appear around the three main objects. Each has its own page.
| Object | What it is | Read more |
|---|---|---|
| RFQ (request for quotes) | Lines sent to chosen suppliers to quote, when no one lists them | RFQs and BOQs |
| BOQ (bill of quantities) | A big list, usually a spreadsheet or PDF, turned into request lines | RFQs and BOQs |
| Project | A company's job site with a budget; requests and orders belong to it | Projects and teams |
| Approval | A request or award waiting for someone allowed to approve it | Approval |
| Return | Damaged or wrong goods the supplier collects | Corrections and returns |
| Commission invoice | What a supplier owes the platform for a month | Commission |