Knowledge · Business Operations

    Purchase Orders and Vendor Workflow

    A purchase order is a written commitment to buy. Learn the PO lifecycle, why vendor prices belong on the item, and how receiving closes the loop on spend.

    What is a purchase order in a service business?

    A purchase order is a written commitment to buy specific quantities from a specific vendor at agreed prices. It exists so that spend is authorised before it happens, deliveries can be checked against what was ordered, and invoices can be verified rather than trusted.

    Key takeaways

    • A PO authorises spend before it happens; a receipt confirms what arrived.
    • Without a PO, an invoice is unverifiable — you are trusting a number.
    • Vendor prices belong to the item-vendor pairing, not to a memory.
    • Partial receipts keep the order open, which is the point.
    • A PO tied to a job is how material spend reaches job cost honestly.

    What a purchase order is actually for

    Three things: authorising spend, checking the delivery, and verifying the invoice. All three fail together in businesses that order by text message. The material arrives, someone signs for it, and four weeks later a statement shows up with a number nobody can dispute because nobody wrote down what was agreed.

    The formality is not bureaucracy. It is the only mechanism that makes a supplier invoice checkable.

    The lifecycle

    • Draft — lines assembled, quantities and prices set, not yet sent.
    • Sent or open — the vendor has it and delivery is expected.
    • Partially received — some lines or quantities arrived, the rest is outstanding.
    • Received — everything arrived and stock and cost layers were created.
    • Closed or cancelled — the order is settled or abandoned, with the reason visible.

    Vendors are records, not names in a phone

    A vendor record holds the contact, the account number, the terms and — most usefully — the prices you actually pay for specific items. Same item, three suppliers, three prices, and the difference between them across a year is real money.

    Storing an item-vendor price also makes the preferred vendor meaningful. When a material line becomes a purchase order, the system already knows who you buy that item from and roughly what it costs, so the order takes seconds and the estimate baseline stays current.

    The loop from job to order to stock

    The clean path is: material lines on a job are selected, a purchase order is created from them, the order is sent, goods arrive, the receipt creates stock at real cost, and the job lines flip to received. Every step is a deliberate human action and every step leaves a record.

    The value of the loop is that it closes. A job's material line can be traced to an order, to a delivery, to a cost — which means when a job's margin comes out wrong, the investigation takes ten minutes and not an afternoon.

    What automation does not do here

    Buying is a judgement call. Lead time, credit position, minimum order quantities, who is willing to deliver on a Friday, and whether the customer has actually paid the deposit are all inputs no reorder rule can see.

    A good system surfaces the need loudly and prepares the order. The decision to spend money stays with a person, and that is a feature rather than a gap.

    Where URBLD fits

    URBLD includes vendors, item-vendor prices, purchase orders with line-level receiving, and PO creation from a job's material lines. Receiving a line creates the cost layer and updates stock. Orders are created and sent by people; URBLD does not purchase automatically and does not read live supplier availability.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page