What a Purchase Order Is and Why Bill-To and Ship-To Differ
A purchase order (PO) is a document a buyer sends to a vendor to formally commit to buying specific goods or services at agreed prices. It is the first step in a standard procurement flow and, once accepted, becomes a binding order that the vendor fulfils and then bills against. This generator produces a clean, professional PO PDF in your browser, with the fields that make a PO legally and practically useful, including the one that defines it. Purchasing managers, small-business owners, and anyone ordering stock or services from a supplier use a tool like this to keep orders organised and auditable without procurement software.
The feature that distinguishes a purchase order from an invoice or a quote is the separation of bill-to and ship-to addresses. The bill-to is where the invoice goes and who pays; the ship-to is the physical location where the goods are delivered, and these are frequently different — a head office pays while a warehouse or a site receives. The tool keeps the two blocks visually distinct, with a same-as-bill-to shortcut for when they match. Beyond that, each line item can carry its own required delivery date, because a single order often has staggered deliveries, and the tool builds a delivery-schedule summary from those dates and flags any that are already in the past. PO numbers auto-increment and persist in your browser so your sequence stays consistent, and the totals use the same precise engine as the invoice tool.
Here is a worked example. Suppose you order ten units of a component at 250 each with 18% tax: the subtotal is 2,500, tax is 450, and the grand total is 2,950. You set the bill-to as your head office and the ship-to as your factory address, so the vendor knows where to deliver even though the invoice comes to head office. You give the line a required delivery date two weeks out, which appears in the delivery-schedule summary. The PO number is generated as PO-0001, and the next PO you create will be PO-0002 automatically, keeping a clean sequence. If you accidentally set a delivery date in the past, the schedule flags it in red so you catch it before sending.
A procurement officer ordering raw materials issues a PO with the factory as ship-to and the finance office as bill-to, so goods and paperwork route correctly. A retailer restocking from a distributor sets staggered delivery dates per line so the supplier phases the shipment, and the schedule summary confirms the plan at a glance. A startup buying equipment uses the auto-incrementing PO number and the authorised-signatory block to create an approval trail that satisfies its auditors. A services buyer raises a PO against an accepted quotation, referencing the same figures, so the eventual invoice can be matched back to the order.
The mistake to avoid is collapsing bill-to and ship-to into one address when they genuinely differ, which leads to goods arriving at the wrong place or invoices going astray; keeping them separate is the whole point of a PO, so the tool always shows both. Another is treating a PO number as a shared company sequence when, here, the counter lives in your browser's local storage — fine for one person, but a team should agree a numbering scheme so numbers do not collide. Remember the flow: the PO commits the buyer, the vendor delivers and raises an invoice referencing the PO, and payment follows the agreed terms; the tool includes a short explainer of exactly this. Every PO and its PDF are generated locally, and nothing you enter is uploaded to any server.
