Purchase-order approvals portal

A purchase-order approval portal is where staff raise purchase orders for what they need, finance approves or rejects each one, and requesters see it move from approved to ordered to received.

Pattern: Requests

Describe it to Pory

“Our staff need to raise purchase orders, finance approves or rejects each one with a note, and whoever asked can see when it's been ordered and when it arrives.”

Viewing as

Purchase orders

Purchase orders to decide

Add
Pending2
Approved1
Ordered1
Received1
Rejected1
Powered by Pory

In plain English

What is a purchase-order approvals portal?

A purchase-order approval portal is where staff raise purchase orders for what they need, finance approves or rejects each one, and requesters see it move from approved to ordered to received. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (requester and finance) that shows only what that role should see, and flat pricing with unlimited employees.

What it does

01

Finance approves or rejects each purchase order with the reason attached

Purchase requests went to whichever finance person replied fastest, with the quote buried somewhere in the email chain. In Pory finance opens the order, sees the supplier, amount, department and justification, and approves or rejects it; a rejection carries a note saying why. Nobody places a $4,800 desk order on a verbal yes.

Approve / reject with a reasonDone by: Finance
02

Requesters see their order go from approved to ordered to received

Once a PO was approved, the requester lost sight of it until a box appeared, or didn't. Each person sees their own purchase orders move from Pending to Approved, Ordered and Received. Finance stops getting "did my desks get ordered?" messages, and the requester knows the order is placed before chasing anyone.

Status tracker for the submitterDone by: Requester

The parts every portal is built from

Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.

Collect

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, in its detail view, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Detail view with related items

Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the records a viewer is allowed to see.

Control

Who sees which records

Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

Frequently asked questions

Your purchase-order approvals portal, live today.

Describe it in a sentence and send the invite. Unlimited employees, flat price.