Procurement and stock

Inventory, purchase requests, and purchase orders in one flow

Move from employee requests to admin approvals, inventory views, and purchase order tracking.

In short

What is the difference between an asset request and a purchase request?

An asset request asks IT for an item that may already be in stock; if it is, IT fulfils it from inventory. A purchase request is specifically to buy something new. An asset request that can’t be met from stock can be converted into a purchase request in one step.

Product proof

Already live in the product

Backed by app modules
Protected app route: /it-inventory

Running in production today: IT inventory, employee purchase requests, admin approvals, and purchase orders.

How it works

Built around real workflows

Highlights below describe capabilities already present in the protected app behind this page.

  • Inventory visibility
  • Employee purchase requests
  • Admin approval workflow
  • Purchase order tracking
Workflow

What teams can do here

  1. Step 1Request equipment
  2. Step 2Approve purchase requests
  3. Step 3Create purchase orders
  4. Step 4Connect spend to vendor records

How it works

  1. 01

    Employee raises a request

    Staff submit an asset request (auto-numbered AR-YYYYMMDD-…) or a purchase request (PR-YYYYMMDD-…) with the item, quantity, justification and priority — no email threads to chase.

  2. 02

    IT reviews and approves

    Admins approve or reject with notes. An asset request can be fulfilled straight from existing stock, or converted into a purchase request when nothing is on the shelf.

  3. 03

    Turn approvals into purchase orders

    Approved requests feed a purchase order against the supplying vendor, carrying its own status (draft, pending, approved, ordered, received, cancelled) plus totals, tax and shipping.

  4. 04

    Receive and register

    When a PO is received you can create the asset directly from it, so the new device lands in the register already linked to its PO and vendor.

“

A worked example

A typical 300-person BPO onboards 25 new agents in a month. Hiring managers raise asset requests — auto-numbered AR-YYYYMMDD-… — for headsets and monitors. IT fulfils 18 from stock; the other 7 convert to purchase requests in one step and roll into a purchase order to the AV vendor, tax and shipping on the total, tracked draft → approved → ordered → received. On delivery the monitors are created as assets straight from the PO, already linked to the vendor and order, then assigned to the new agents — so when the auditor asks in March, the request, the PO and the asset all reference each other.
An asset request asks IT for an item that may already be in stock; if it is, IT fulfils it from inventory. A purchase request is specifically to buy something new. An asset request that can’t be met from stock can be converted into a purchase request in one step.

From "I need a monitor" to a booked asset in one chain

Requests, approvals, purchase orders and asset creation reference each other end to end, so procurement leaves an audit trail instead of an email thread.