01 · How it works

Three layers running in real time

Origen turns fragmented purchasing into a connected, intelligent system. Procurement data, behavioural analytics and operational insights flow through three layers — capture, detect, govern — so every supplier interaction becomes visible, measurable, and auditable.

Capture

Every procurement event lands in a single graph

RFQs, quotes, POs, deliveries, invoices and rebates all live in one Postgres schema with proper foreign keys
Each role writes events from their own portal — vendors submit invoices, PMs raise POs, finance approves payments
Every row carries org_id + created_by so multi-tenant isolation and personal attribution are non-negotiable

Postgres · 18 tables · realtime publication

Detect

Synchronous triggers fire the moment the event lands

Five Postgres triggers run inside the same transaction as the source insert — no batch jobs, no delay
Each alert carries the kind, severity, rich narrative message, structured evidence JSON, and a subject pointer
Thresholds live in sq_policy — admins can tune the engine from the Settings page without a deploy

Median fire latency: under 50ms

Govern

Reviewers decide with attribution; confirmed alerts auto-hold the cash

Admins and auditors can confirm, dismiss or reopen any alert with a resolution note
Confirmed alerts auto-open a Finance hold on the underlying invoice or PO — payment is frozen until released or escalated
Every status change writes to the audit log with the reviewer's identity and the exact JSON diff

SOX-ready · full who/what/when on every change

Data flow

What actually happens when a PM picks a quote

Event

PM marks quote selected

Trigger

sq_detect_on_quote_select

Alert

"PM picked Vendor B at +18% — lost savings GHS 4,140"

Confirm

Admin reviews evidence + adds note

Hold

Finance hold auto-opened on invoice

Resolved

Finance releases or escalates

Try it for yourself