Manual purchase-order management becomes difficult when the team loses track of which version was requested, accepted, received or billed. A spreadsheet can work with clear ownership and disciplined updates. The warning sign is recurring re-entry or unresolved differences, not a particular number of suppliers or POs.
Use the failure patterns below to find where a shared living purchase order would help, and where a clearer manual process may be sufficient.
Approval is detached from the request
If approval lives in an email while the draft changes elsewhere, the buyer may send something the approver never reviewed. Give the request a reference, show the proposed items and amount, record the decision, and define which later changes require another review.
LineNow supports a distinct requisition with operational approval triggers for every request, estimated total, item count or an unpriced item. Eligible default or requester-specific approvers can send it to Procurement or return it with a reason. Sequential approval chains, departmental budgets, delegation and timed escalation are outside that scope.
Supplier status is inferred from sending
An email transmission proves neither acknowledgment nor commercial acceptance. A message saying “shipping Thursday” is a planned ship date, not evidence of dispatch.
Keep the source message, order reference, promised quantity and date together. Assign an owner and follow-up deadline when confirmation is missing. If a portal or phone order is manual, record its reference so another buyer does not place it again.
LineNow can parse messages on configured supported channels into reviewable updates. It cannot know about an inaccessible personal chat or an unrecorded phone conversation.