Purchase approval and PO status tracking answer different questions. Approval records whether an authorized person has allowed a request to proceed. Status tracking records evidence about the supplier order, its changes and its physical receipts. Connecting them helps the next person act without treating a supplier message as spending permission.
For a small team evaluating LineNow, test a request through Procurement, supplier ordering, receiving, and finance. Requisitions go directly to the owner or Procurement. Any formal spending approval belongs in the business’s separate approval process.
Separate the request from the supplier order
A requisition records an internal need: requester, items, quantities, estimates, need-by date and notes. A supplier PO communicates the purchase request. Sending it does not establish that the supplier accepted every line or will deliver as requested.
Keep the internal approval connected to the downstream purchasing record. A later price increase or substitute can require a separate commercial decision even when the original request was approved.
For example, suppose an illustrative requisition estimates ten cases at $30 each. Approval of that $300 request does not itself establish permission to accept ten cases at $35. The buyer needs to follow the business's change policy for the additional $50.
Review the request in Procurement
LineNow keeps requisitions distinct from supplier POs. A submitted request is available immediately to the owner or Procurement at its business unit. Review the requested items, estimates, missing prices, and need-by date, then add items to a cart or start supplier sourcing.
Test the queue and its permissions
Submit a request with priced and unpriced items. Confirm that the owner and Procurement can find and handle it without an approval or resubmission step. Inventory requesters can submit requests; purchasing actions require owner or Procurement access to the business unit.
Demonstrate any formal approval requirements in the system responsible for them before choosing a workflow.
Record supplier evidence without treating it as approval
Procurement can act on a submitted need through stock fulfillment, sourcing or a supplier order as appropriate to the configured workflow. Supplier sending then needs its own evidence and follow-up owner.
A sent email, technical acknowledgement or read receipt is not commercial acceptance. A manually placed portal or phone order needs its external reference so another operator does not submit it again. Test the actual supported channel using the supplier sending checklist.
On configured supported channels, LineNow can turn supplier messages into reviewable updates. Interpret them according to what they actually establish:
| Message | Evidence to record | What remains unresolved |
|---|---|---|
| “Got it” | The supplier acknowledged the message | Accepted items, prices and delivery may still need confirmation |
| “Order #A7-3315 confirmed” | Supplier order reference and confirmation source | Whether its detailed terms match the buyer's request |
| “Can sub iceberg for romaine” | Proposed substitution | Suitability, pack, price and buyer acceptance |
| “18 of 24 this week” | Proposed partial quantity | Exact arrival date and treatment of the other six |
| “Shipping Thursday” | Planned ship date | Actual dispatch and arrival |
| “Now $42.50 per case” | Proposed new unit price | Commercial approval and which quantities it applies to |
These are evidence interpretations, not a promise that the product uses these exact status labels. Preserve the original request, proposed change and buyer's decision in the living purchase order.
Keep receiving and finance decisions separate
The receiver records what physically arrived and was accepted, with shortages, damaged goods and remaining quantities visible. Supplier confirmation or an invoice cannot establish that physical event. Verify which system updates stock and how it handles a failed or repeated receipt transfer.
Finance needs the relevant commitment, approval, receipt, invoice and credit evidence. It may need those records before all goods arrive or after the original delivery is complete. Avoid designing the handoff around one supposedly final order state.
Agree which records move, in which direction, when they are created and how corrections are applied. Test deposits, partial deliveries, credits and unresolved differences with the accounting owner.
Upstream reconciliation helps the buyer, receiver and supplier resolve purchasing differences earlier. AP still owns its policy, coding, tax, duplicate-invoice and payment checks.
Evaluate a complete approval exception
Bring an estimated request, a supplier price increase, a partial receipt and the resulting invoice to a demonstration. Ask the requester, approver, buyer, receiver and finance reviewer to explain what they can do and what still needs another person's decision.
Measure time awaiting review, active handling time, unapproved changes and unresolved receipt or invoice differences over comparable orders. Include the time needed to correct software output. A faster approval queue is useful when it preserves authority and gives downstream staff a reliable record.
Use PO status tracking to evaluate the connected workflow and current pricing to scope the setup. The team rollout guide covers adding buyers and locations after the first cycle works.