Growing SMBs need to separate three records that are often collapsed into one spreadsheet row: a request to buy, an internal stock transfer or fulfillment request, and a purchase order sent to a supplier.
The distinction matters. A purchase requisition records what a team needs before Procurement commits spend. An internal purchase order coordinates goods between a branch and a warehouse or central buying location. A supplier purchase order is the commercial order sent outside the business.
LineNow supports all three operational paths without pretending to be an enterprise spend-governance suite.
Quick answer
Use a purchase requisition when an employee or location needs Procurement to review a request before fulfillment or supplier commitment. Use an internal purchase order when one business unit is actually ordering stock from another. Use a supplier purchase order when the buyer is ready to commit an order to an outside vendor.
LineNow keeps requisitions separate from supplier purchase orders. Requests go directly to the owner or Procurement for item review, sourcing, and ordering. Business-unit access determines who can handle the request.
The requisition workflow
A practical LineNow requisition workflow looks like this:
- A requester records the needed item, quantity, need-by date, estimated price, and notes.
- The request enters the business unit's procurement queue.
- The owner or Procurement reviews quantities and estimates.
- Procurement decides whether to source each item or add it to a supplier order.
- Available goods can be issued from stock; missing goods can move into sourcing, an RFQ, or a supplier PO.
- Receiving records what arrived; the configured posting process updates the relevant inventory record.
- Accounting receives the purchasing context while remaining in the finance system.
This is a good fit when:
- many employees request spend
- a buyer needs to review demand before contacting suppliers
- the buyer needs quantities, estimates, and missing pricing visible before ordering
- the stockroom may fulfill some items before Procurement buys the rest
- the business wants an audit trail outside email and Excel
If the company also needs live departmental budgets, cost-center enforcement, delegated approval queues, or sequential multi-level chains, it needs a broader spend-governance product alongside or instead of this operational workflow.
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 produce reviewable changes to the external PO.
- Warehouse receives goods.
- Store receives allocation.
- Finance reviews the supplier bill and location context under the agreed accounting handoff.
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 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. They do require a distinct request record when Procurement must review the need before deciding how to fulfill it. They do not automatically require an enterprise procure-to-pay rollout.
When internal POs are the right record
An internal PO can serve as the fulfillment record when a warehouse accepts a replenishment request. Some systems use a transfer order or another internal record instead. Agree the record and stock-posting behavior for your setup.
Fictional 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 can capture the branch's original need, but the internal PO is the right fulfillment record once the warehouse agrees to supply it. The two should stay linked rather than being collapsed. The work after approval includes fulfillment, supplier changes, receiving, allocation, and upstream reconciliation before accounting sees the final supplier bill.
When requisitions are the right record
Use a requisition whenever the business needs to review a need before committing stock or supplier spend, including requests inside the normal inventory loop.
Examples:
- new equipment or replacement parts
- PPE, tools, and facilities supplies
- stockroom consumables and packaging
- a new or unpriced physical item
- replenishment that needs approval before sourcing
- goods that Procurement may fulfill from stock or buy from a supplier
Services, software, marketing spend, and other indirect purchases often need policy, budget, and contract controls more than stockroom fulfillment. LineNow gives owners and Procurement a shared physical-goods request to work on. Policy, budget, and contract controls require separate systems.
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 creates a reviewable order update.
- 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
If you are still drafting supplier POs by hand, the Purchase Order Generator covers the external-PO fields above.
The internal PO and external PO should be connected but not collapsed. One represents branch demand. The other represents supplier commitment. The living PO record is what keeps those states from drifting apart.
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
Finance determines the permitted allocation and legal-entity treatment. An internal markup within one company is not new group revenue; inventory valuation and intercompany accounting belong in the books. Location context in an internal PO does not prove that every allocation posts automatically.
Where LineNow fits
LineNow is a lightweight procurement management system for physical-goods teams moving requisitions, item review, RFQs, quote comparison, supplier communication, purchase orders, receiving, GRNs, and basic inventory out of email and Excel.
The practical setup:
- requesters submit a distinct requisition with items, quantities, need-by dates, estimates, and notes
- requests go directly to the business unit’s procurement queue
- owners and Procurement review items, adjust quantities, and start sourcing or ordering
- Procurement can issue available inventory, source missing items, compare supplier quotes, and create supplier POs
- supplier replies create reviewable order-state updates
- receiving records discrepancies, with stock updates governed by the configured item, location and posting process
- accounting stays in the finance system
The Whitmans customer account describes a shared supplier-purchasing workflow and includes the customer’s testimonial on support and flexibility. Use your own comparable orders to measure review time, corrections and unresolved exceptions.
Evaluate whether this request-to-order workflow matches your operation. A real requisition tied to buying can solve the operational handoff, while sequential approvals, departmental budget controls or contract enforcement may require additional systems.
See the full procurement management system workflow for requisitions, RFQs, receiving, GRNs, and inventory.
Related
- Central Warehouse Procurement for Multi-Location Retail
- Shopify Plus and QuickBooks Still Leave a Procurement Gap
- 90-Day Procurement Trial Setup for Shopify Plus and QuickBooks
- Three-Way Matching
- What Is a Living Purchase Order?
- Three-Way Matching vs. Living POs
- You Do Not Need a Procurement Department
Ready to stop branch managers from calling suppliers directly? Book a demo to start your 90-day free trial.