Small-business outsourcing research

What share of purchase order changes lack a written reason after supplier acknowledgement?

A protocol for measuring how many purchase order changes are made after the supplier confirms the order without a recorded reason or approver.

What share of purchase order changes lack a written reason after supplier acknowledgement?

Research question and scope

This protocol asks what share of purchase order changes made after supplier acknowledgement lack a written reason. The unit is one change event, not one purchase order and not one supplier. The study measures the share with a recorded reason, the share with a named approver, and the share with neither. It does not judge whether the change was commercially wise.

Set the scope to one shop, one purchasing process, and one change rule. Record the approval thresholds, the supplier confirmation method, and the date the rule took effect. If the shop changes its order system during the window, keep the original rule for orders already acknowledged and analyze later orders separately. A new system can change the recording speed without changing the reason for changes.

Definitions that make the measure reproducible

Define supplier acknowledgement as the supplier's written confirmation of the order terms. Define a change event as any edit to quantity, price, item, delivery date, ship-to address, or payment term after that acknowledgement. Define a written reason as a note that states why the change was needed and who requested it. A version number with no explanation does not meet the definition.

Define the denominator as every acknowledged order that had at least one later change during the window. Exclude typo corrections that leave the commercial terms the same and record that count separately. Treat two changes on the same order as two events when they were approved at different times. Test the definitions on ten closed orders before collection begins.

Evidence standard and data dictionary

For each change event, capture the purchase order number, supplier, original terms, new terms, request date, acknowledgement date, requester, reason, approver, supplier confirmation, and invoice outcome. Attach the change message and the supplier reply. Record whether the change arrived before or after production started. Note the version that both sides accepted so the invoice can be matched to one set of terms.

Record the reason in the requester's own words when possible. Note whether the reason points to a demand change, a specification error, a supplier issue, or an internal approval delay. Mark unknown reasons as unknown and report the count. A guessed reason hides whether the shop needs better forecasting or better order review.

Sampling and collection

Collect every acknowledged order with a later change in the window rather than a sample, because the rule applies to each event. If the shop runs several departments or suppliers, collect each separately and record the group. Report the number of events and the value behind every percentage. A combined rate can hide one department that changes orders after production starts.

Draw the data from the order system and the supplier messages, not from a spreadsheet rebuilt after the fact. If either record is incomplete, say so and reduce the claim. Record the export date and the events that could not be matched to an approval. A missing approval is itself a finding about the routine.

Analysis and reporting

Report the share of change events with a written reason, the share with a named approver, and the share with both. Show the median days from acknowledgement to change. Present the results by department, supplier, and change type. Use the same denominator for every rate.

Separate a change requested before production from one requested after. Report both because the cost and the fix differ. A shop may accept a late change for a good customer reason but should not accept one with no recorded reason at all. Report the invoice differences that followed the change so the financial effect is visible.

Limits of the evidence

The order records can show what changed and who approved it, but they cannot show whether the reason was honest or complete. A recorded reason is not proof of a good decision. The protocol also cannot capture a change made verbally with the supplier and never entered in the system. State that limitation before presenting the rate.

A small shop may have too few acknowledged orders to support a stable trend. Describe the event count and the supplier mix instead of ranking staff. Do not compare a shop that orders custom goods with one that orders catalog stock. Report the change rule and the approval threshold beside the rate.

What to change

Give the result to the owner and the purchasing lead and ask them to choose one observable change. The change might be a required reason field, a second approval after production starts, a weekly change review, or a supplier confirmation step. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.

If the written-reason rate rises but change volume also rises, the shop may be documenting changes it could have prevented with a better first order. If both fall but supplier disputes grow, the team may be suppressing changes that should be recorded. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research