Use case · Procurement

A purchase order app, linked to its requisitions

Two linked forms — a purchase requisition and the purchase order that fulfils it — with vendor and product lists 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.

Download the workbook

Get this template

The Purchasing starter workbook: two linked forms — Purchase Requisition and Purchase Order, joined by a relation — with vendor, product and currency lists and approval rules. Enter your email to download it and join the early-access list. Enter your email to download the workbook and join the early-access list.

Joining the waitlist means we store your details and send you the messages needed to run it — your place in the queue, your invitation and launch access details. Those are service messages you ask for by joining; marketing email only with the box ticked.

In a spreadsheet, requisitions and purchase orders live on separate tabs with nothing tying them together — you copy a requisition's details into a PO by hand and hope they stay in sync. Sheetward turns that workbook into one app with two linked forms: each purchase order references the requisition it came from.

What’s inside this workbook

Read straight from the Purchasing App workbook — the same file you download.

  • 2 forms
  • 4 sections
  • 27 fields
  • 2 master-data tables
  • 20 validation rules
  • 2 formulas
  • 2 field derivations
  • 1 relation

Forms

  • Purchase Requisition

    • Purchase Requisition — 6 fields
    • LINE ITEMS — 7 fields
  • Purchase Order

    • Purchase Order — 7 fields
    • LINE ITEMS — 7 fields

Master data

Products, Vendors

What it demonstrates

  • Master-data lookups
  • Validations within and across sections
  • Field derivations from master data
  • Formulas
  • Multiple linked forms
  • Relations between forms

Not every app needs every feature — add what yours actually uses. See the Template Gallery

How it works

1

Open the template

Adjust the fields, lists and rules to match how you work.

2

Upload & review

Sheetward shows both forms, the relation linking them, and every rule it detected — confirm, and the two-form app is live.

3

Requisition → order

Raise a requisition, then create a purchase order that links back to it; line totals compute and the rules gate approval.

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 has a relation field pointing at the requisition it fulfils — a stored reference, not a copied cell.

Can one workbook really become two connected apps?

It becomes one app with two forms, which is the useful shape: shared lists, shared roles, one dataset. The relation is what connects them.

Can I import our existing vendors and products?

Yes — the lists are List_ tabs you can fill from Excel or CSV, and both forms accept bulk import.

Is the template required?

No — any conformant workbook works; the template saves you building the two forms, lists, rules and the relation from scratch.