Use case · Procurement
A purchase order app, linked to its requisitions
Raise a purchase requisition, then create a purchase order that points back to it — two related forms from one workbook, with vendor and product lists, line totals and approval rules. Start from the free template.
Something went wrong — please check your email address and try again.
You’re on the early-access list 🎉
Thanks! Your workbook is ready — download it below. We’ll be in touch about early access.
Get this template
The Purchasing starter workbook — two linked forms (Purchase Requisition and Purchase Order, joined by a relation), vendor / product / currency lists, and validation rules. Download it, adjust the sheets, and upload. Enter your email to download the workbook and join the early-access list.
In a spreadsheet, requisitions and purchase orders live on separate tabs with nothing tying them together — you copy a requisition’s vendor and lines into a PO by hand and hope they stay in sync. Sheetward turns that workbook into two forms in one app, with a real relation: each purchase order references the requisition it came from, and picks up its details rather than re-keying them.
Vendors, products and currencies come from List_ tabs; each line’s Total is a Formula_ field (quantity × unit price); and Rules_ / Logic_ sheets carry the validation and approval logic. The workbook stays the design you revise and re-upload.
How it works
Open the template
Download the Purchasing workbook: a Purchase_Requisition form and a Purchase_Order form, List_ tabs for vendors, products and currencies, a per-line total formula, and Rules_/Logic_ sheets for validation and approval.
Upload & review
Sheetward shows both forms, the relation linking a purchase order to its requisition, every dropdown and each rule it detected. Confirm, and the two-form app is live with its own isolated dataset.
Requisition → order
Raise a requisition, then open a purchase order and link it back to that requisition; vendors and products come from the lists, line totals compute, and the rules gate what can be approved.
What the template becomes
Two linked forms
A Purchase Requisition form and a Purchase Order form in one app, joined by a relation — each PO carries a reference to the requisition it came from, so the two stay connected instead of copy-pasted.
Requisition lookup on the PO
The purchase order’s requisition field is a relation, not free text — pick an existing requisition and see its date and vendor, so orders trace back to an approved request.
Vendor & product lists
List_ tabs become the vendor, product, currency and unit dropdowns on both forms, so procurement data stays consistent and filters cleanly.
Line totals computed
Each line’s Total is a Formula_ field (quantity × unit price), recalculated as you enter items and read-only so it can’t be edited away.
Validation & approval rules
Rules_ and Logic_ sheets become field validation and conditional logic — required fields, allowed values and the checks that gate an order — enforced deterministically for every user.
Roles, history & export
Per-app roles, a full change history of every requisition and order, and export to Excel, CSV or JSON.
Why teams pick Sheetward
- A real relation between two forms — the link between a PO and its requisition is data, not a copied cell.
- Approval and validation are your Rules_/Logic_, applied the same way every time — not a prompt that guesses.
- Flat pricing for the whole procurement team — no per-seat costs as approvers are added.
- Own it: export everything, or run the app yourself as a standalone bundle.
Frequently asked questions
How are the requisition and the purchase order linked?
The purchase order form has a relation field that points at the Purchase Requisition form. On a PO you pick the requisition it fulfils and see its details (date, vendor); the link is stored as a real reference, so orders trace back to their requisitions instead of duplicating them.
Can one workbook really become two connected apps?
It becomes one app with two forms. Sheetward reads both the Purchase_Requisition and Purchase_Order sheets and the relation between them, and generates a single app where the two forms are joined — no code, no separate integrations.
Where do the approval checks come from?
From the Rules_ and Logic_ sheets in the workbook. They define required fields, allowed values and conditional logic; Sheetward enforces them server-side for every user, so the same checks apply no matter who enters the order.
Can I import our existing vendors and products?
Yes — the vendor and product lists are List_ tabs you can fill from Excel or CSV, and both forms accept bulk import so you can bring in existing requisitions and orders.
Is the template required?
No — it’s a head start. Any conformant workbook with two forms and a relation works; the template just saves you laying out the forms, lists, line-total formula and approval rules.