Requisitions vs Internal Purchase Orders for SMB Procurement
When SMBs need formal requisitions, when internal POs to a central warehouse are cleaner, and how branch demand, supplier buying, receiving, and accounting should connect.Growing SMBs often ask for requisitions when what they really need is controlled internal ordering.
The distinction matters. A requisition is a request to buy. A purchase order is a committed order. In enterprise procurement, those are separate objects with approval chains, budgets, policies, and AP controls.
At SMB scale, the workflow can often be simpler: locations create internal purchase orders to a warehouse or central buyer, and the central buyer decides what gets fulfilled from stock versus purchased from outside suppliers.
That gives control without forcing the team into an enterprise procurement process.
The classic requisition workflow
A formal requisition workflow looks like this:
- Employee requests goods or services.
- Manager approves request.
- Procurement converts requisition into supplier PO.
- Supplier confirms PO.
- Receiver records goods receipt.
- AP matches invoice to PO and receipt.
This is a good fit when:
- many employees request spend
- budgets need strict approval
- purchases are not mostly inventory replenishment
- finance owns spend control
- the company has dedicated procurement or AP roles
It is often too heavy when a small operator is just trying to stop branch managers from calling suppliers directly.
The internal PO workflow
An internal purchase order workflow looks like this:
- Store manager creates an order to the central warehouse or main buying location.
- Warehouse or central buyer approves, edits, or fulfills it.
- Warehouse consolidates demand from multiple stores.
- Buyer places external supplier POs only when needed.
- Supplier replies update the external PO.
- Warehouse receives goods.
- Store receives allocation.
- Accounting sees the final supplier bill and location-level allocation.
This is a strong fit when:
- locations regularly need product
- a central warehouse or main store supplies branches
- the same buyer controls supplier relationships
- the business buys inventory, ingredients, or hard goods
- store managers need a simple workflow
- accounting needs cleaner location-level spend
The internal PO is not pretending the warehouse is an outside vendor. It is using the PO as the shared operational record between branch, warehouse, buyer, receiver, and accounting.
Why SMBs ask for requisitions
SMBs usually ask for requisitions because they want one of four controls:
Visibility. "I want to know what stores are asking for before they call suppliers."
Approval. "I want a buyer or manager to review requests before spend is committed."
Consolidation. "I want the warehouse to combine location demand into fewer supplier POs."
Accounting traceability. "I want to know which location consumed the spend."
Those are valid needs. But they do not always require formal requisition software.
When internal POs are better
Internal POs are usually better when the request is actually a replenishment order.
Example:
- Branch needs 10 cases from the warehouse.
- Warehouse has 6 cases.
- Warehouse fulfills 6 and adds 4 cases to supplier demand.
- Central buyer places supplier PO.
- Supplier short-ships 1 case.
- Warehouse receives 3 cases.
- Branch gets updated allocation.
A requisition object is less useful here than a living order record. The work is not only approval. It is fulfillment, supplier changes, receiving, and allocation.
When requisitions are still better
Use formal requisitions when the request is not part of the normal inventory loop.
Examples:
- new equipment
- software spend
- repairs and maintenance
- services
- marketing expenses
- office supplies outside normal inventory
- purchases requiring budget approval before vendor selection
Those purchases often need policy and budget controls more than warehouse fulfillment.
The central warehouse pattern
For multi-location operators, the central warehouse pattern is often the cleanest middle ground.
Each store treats the warehouse as its approved source. The warehouse can:
- confirm available inventory
- adjust quantities
- reject or backorder items
- consolidate supplier demand
- allocate costs
- communicate expected arrival dates
The outside supplier relationship stays centralized. Store managers get a simple workflow. Accounting gets a cleaner record.
See Central Warehouse Procurement for Multi-Location Retail for the full model.
How this changes supplier buying
Without internal POs:
- Store A calls Supplier 1.
- Store B texts Supplier 1.
- Store C emails Supplier 2.
- Warehouse discovers demand later.
- Accounting receives supplier invoices with unclear location context.
With internal POs:
- Store A, B, and C order from the warehouse.
- Warehouse sees total demand.
- Buyer places one supplier PO or fulfills from stock.
- Supplier reply updates the order.
- Receiving confirms what arrived.
- Accounting sees the final record.
The supplier does not need to change. The buyer's workflow changes.
What to track
For internal POs, track:
- requesting location
- fulfilling location or warehouse
- requested quantity
- approved quantity
- fulfilled quantity
- backordered quantity
- external supplier PO link where applicable
- expected arrival
- receiving status
- internal markup or allocation, if used
- final accounting treatment
For external supplier POs, track:
- supplier
- line items
- pack size
- MOQ
- supplier cost
- supplier reply changes
- receiving discrepancies
- invoice documents
- QuickBooks or Xero handoff status
The internal PO and external PO should be connected but not collapsed. One represents branch demand. The other represents supplier commitment.
The accounting implication
Internal POs help accounting because they preserve intent and allocation.
The accountant can see:
- which branch requested product
- which supplier created the cost
- what the warehouse fulfilled
- whether an internal markup applied
- what should hit each location/class/category
- why the vendor bill differs from the original supplier PO
This is especially useful when warehouse employees, freight, or corporate overhead are allocated back to locations.
Where LineNow fits
LineNow supports SMB procurement workflows where formal enterprise requisitions would be too heavy but informal supplier calls are no longer controlled.
The practical setup:
- store locations create internal POs to a central warehouse or main buyer
- central buyer consolidates demand
- external supplier POs carry supplier communication and receiving
- supplier replies update order state
- accounting receives clean purchase data after the workflow is current
For many SMBs, this is the right level of control: more structured than calls and spreadsheets, lighter than enterprise requisitions.