The Verified Loop · Construction supply chain
Delivered. Verified.Paid.
every step on one tamper-evident record.
ChainBuild360 gives contractors and suppliers one shared record of every order. The supplier declares the delivery, your own site receiver confirms what arrived, and a clear payment instruction follows — less to chase, less to argue about.
Built for the contractors, suppliers, and site teams who order, deliver, and receive construction materials — and need one record they can all rely on.
The loop
Deliver → Verify → Pay
One shared loop replaces the paper trail. The supplier delivers; your site receiver confirms what arrived; a payment instruction says what to pay and when.
Deliver. The supplier dispatches the order and declares it delivered to your site.
Verify. Your own site receiver records what actually arrived, line by line.
Pay. Accepted in full, a payment instruction is issued; the buyer pays directly.
Deliver
Site receiving, straight from the field
The supplier marks the order delivered — but that is only a declaration. Your own site receiver then records what actually arrived, line by line: received, damaged, or rejected, on a phone-friendly screen.
The delivery slip and photos go on the record too — not a scrawled signature on a clipboard that disappears by month-end.
- ordered
- 120 · rebar 15M
- received
- 120 · in full
- damaged
- 0 · rejected 0
- evidence
- slip · 2 photos
- status
- RECEIPT_RECORDED
Verify
A record you can check, not just trust
Every step — order, acknowledgement, dispatch, receipt, payment — is written to an append-only record. Each entry is linked to the one before, so a past entry cannot be changed without it showing.
Each new entry lands with an orange sweep. The panel shows sample entries, not customer data.
- entry #482130xda50…bf3bORDER_PLACED$142,500
- entry #482140x68c6…03dcORDER_ACKNOWLEDGED$88,600
- entry #482150xe261…d999SHIPMENT_DISPATCHED$315,000
- entry #482160x78fb…a9b0DELIVERY_DECLARED$47,250
- entry #482170x0c72…2363EVIDENCE_ATTACHED$206,400
Pay
A clear payment instruction
When a delivery is accepted in full, ChainBuild360 issues a payment instruction: the amount, the statutory lien holdback for the province, and the due date. The buyer pays the supplier directly and marks it settled.
ChainBuild360 never holds or moves money. A short or damaged delivery keeps payment on hold until it is put right.
Payment instruction
$142,500
Sample · PO-1042 · less lien holdback · buyer pays directly
The idea
Deliveries still run on phone calls, paper slips and trust
When a delivery is questioned, each side rebuilds the story from its own emails. A shared record of what was ordered, what arrived and what is owed is the missing layer.
0
Shared record per order, seen by buyer and supplier
One history
0
Ways a dispute can end: pay in full, pay an agreed part, or cancel
Managed disputes
0
Provinces supported, with a holdback you set on each order
Payment instructions
Built in Vancouver, BC · Pilot in preparation
Platform
Seven capabilities, one verified loop
Everything here serves the same idea: make delivery provable, and let the record show what is owed.
Tamper-evident record
Every order, receipt, and payment step is written once to an append-only record. Each entry is linked to the one before, so a changed entry shows.
Supplier qualification
Suppliers upload insurance and licence documents. The buyer checks them and approves the supplier, with a review date, before anyone can order.
Project purchase orders
Each order is tied to a project, site address, receiving contact, and expected delivery date. Changes are versioned and re-acknowledged by the supplier.
Site receiving
The buyer's own site receiver records what arrived on each line — received, damaged, or rejected — on a phone-friendly screen, with slip and photos.
Payment instructions
A delivery accepted in full issues an instruction: amount, provincial lien holdback, and due date. The buyer pays the supplier directly and marks it settled.
Documents with fingerprints
Attach certificates, delivery slips, photos, and invoices at any stage. Every file gets a fingerprint and can be re-checked against the record at any time.
Managed disputes
A dispute is a case with a category, a response date, and a conversation. The other party must accept the resolution; overdue cases escalate to ChainBuild360.
The record
Not crypto. A shared record that shows if anyone changes it.
When the general contractor, the supplier, and the PM all read from the same tamper-evident record, the argument stops being “whose paperwork is right” and starts being “what the evidence says.”
How the record worksdeliver — verify — pay
Close the loop
Deliver it. Verify it. Get paid for it.
We’re preparing a limited pilot with a small number of Canadian design-partner contractors. Bring us a delivery-and-payment headache worth solving.