It is 4:47 PM on Tuesday. Your order requested ten cases at $42 each, delivered Thursday. Then the supplier replies:
Only have 6 cases. Price is up. Delivery Friday.
The reply changes the buying decision, but it does not contain enough information to finalize the order. Is six the total available or the first shipment? What is the new price? Which Friday delivery window applies? Are the remaining four cases backordered or unavailable?
This fictional example shows how to turn a short supplier reply into a reviewable order update without inventing missing details. The practical workflow is PO status tracking, where the buyer, receiving team and finance reviewer can see the same evidence.
Keep the original request and the proposal visible
Do not replace ten ordered cases with six and silently erase the balance. Keep the original quantity, price and date alongside the supplier’s message.
| Field | Original request | What the reply establishes |
|---|---|---|
| Quantity | 10 cases | Supplier says 6 are available; balance needs clarification |
| Unit price | $42 per case | An increase is proposed; amount is missing |
| Delivery | Thursday | Friday is proposed; date and receiving window need confirmation |
| Acceptance | Requested terms | Buyer decision still required |
Expected incoming stock and actual on-hand stock are different. A supplier confirmation can change the delivery plan; it does not establish that goods have physically arrived.
Resolve the facts that change the decision
Ask the supplier to confirm the available quantity, remaining balance, exact price and delivery window. Check the stock and demand that must be covered before then. If Thursday’s requirement cannot wait, evaluate a transfer, an approved substitute or another source using actual availability.
Suppose the supplier clarifies: six cases at $48 each will arrive Friday morning, and the remaining four are unavailable. The six-case purchase would be $288 before other charges. At the original $42 price, those same six cases would have cost $252, so the comparable price increase is $36.
The total order value falls from the original $420 because fewer cases are supplied. That lower total does not mean the item became cheaper or that the business saved $132. The four-case shortage still needs an operating decision, and the replacement could add cost.
Record what the buyer accepts
The buyer may accept six cases, negotiate, cancel where permitted or choose another response. Record the decision and its source. If the balance is cancelled, preserve that cancellation rather than making it look as though only six cases were ever requested.
For a proposed substitute, the responsible person must confirm identity, pack conversion, usable yield and suitability. Extracting the supplier’s suggestion is not approval to use it in a recipe, assembly or regulated process.
After acceptance, notify the receiving team of the expected quantity and window. Review any replenishment recommendation against the updated incoming supply. Do not assume an unknown price can be used to calculate a precise margin impact.
Carry the decision through receiving and invoice review
If five cases arrive against the accepted six, record five and investigate the remaining case. The original ten-case request, accepted six-case commitment and five-case receipt answer different questions.
If an invoice bills six cases at $48, its $288 total exceeds the five received cases’ $240 goods value by $48. Resolve the difference against delivery and billing terms. It is not automatically a loss or a credit, and the receiver should not record the missing case merely to make the documents match.
Invoice mismatch review then starts from the original order, accepted change and physical receipt. Finance still checks authorization, coding, taxes, duplicates, terms and unresolved exceptions.
What to test in LineNow
LineNow connects supplier messages, purchase orders and receipts through a living purchase order. Supported message processing can turn supplier replies into order context and reviewable changes. Verify the actual channel, matching behavior and review path with your own messages.
Use this sparse reply as an acceptance test:
- Does the message attach to the correct order?
- Does the original ten-case request remain available?
- Is the missing new price left unresolved rather than invented?
- Can the buyer record the six-case acceptance and four-case cancellation separately?
- Does receiving preserve the actual five-case result?
- Can a second employee explain the invoice difference from the shared record?
Demonstrate any required downstream forecast, alert or accounting update explicitly. A parsed reply alone does not establish that every connected system updates every field.
Agree which system owns stock and finance records and who resolves failed or ambiguous updates.
Measure whether the handoff improves
Compare similar orders before and during a pilot. Track active review time, missing facts, corrections and unresolved receipt or invoice differences. Keep the work of approving a change separate from copying it between systems.
The useful outcome is that the next person can see what was requested, proposed, accepted and received without reconstructing the conversation. Evaluate that workflow with a changed supplier order.