The Purchase Order Begins Before the Purchase Order

Part 3 of 16 · Behind the Buy Button

Maya receives a forecast, then an order

eComm Inc tells Maya that demand for Making Things Work may reach 1,000 copies. She starts thinking about paper and production time. A week later, she receives a purchase order for 100 copies. Has eComm Inc committed to buying 1,000, 100, or neither?

We cannot answer from the word “forecast” alone. In this example, the forecast is planning information and the accepted order is the particular commitment. A real agreement might make a forecast binding in specified circumstances. We must read it before choosing which meaning applies.

The before-the-order cheat sheet

Item	Plain-language purpose	Common misunderstanding
Forecast	Estimate likely need	Guaranteed demand
Requisition	Ask internally for a purchase	Order already sent to a supplier
RFQ: request for quotation	Ask for price and terms for a defined requirement	Accepted offer
RFP: request for proposal	Ask suppliers how they would meet a broader need	Permission to start work
Approval	Grant specified authority	Approval for every later change
Agreement or purchase order	State the applicable external terms	Proof of delivery
Acknowledgement	Record Maya's response	An unqualified acceptance of every line

These are explanatory categories, not a claim that every purchase must pass through every document. Ordering ordinary supplies from an approved catalog can be simpler than procuring a printing system. A long-term lease can establish obligations without behaving like a merchandise order.

Identify Maya before buying from Maya

The team needs more than a familiar contact name. Which legal entity is supplying the books? Which address receives notices? Who can agree a price change? Which entity receives payment? Is the machine contract with the same entity as the book contract?

In our fictional model, Maya’s Stories Inc. supplies books and Mayan’s Sapiens Inc. supplies printing machines. They are distinct suppliers, so the supplier identities, book agreements and machine agreements must remain separate. eComm Inc's retail business and eComm Inc's operations team identify the buying roles; their precise legal entity identifiers belong on the records.

Supplier qualification asks whether the business can meet the requirement. Supplier onboarding records the approved relationship. A later change to bank instructions is a separate authority event, not an ordinary edit to a mailing address. We will return to that distinction in the safety essay.

Approval has a scope and a version

Suppose eComm Inc authorizes 100 books at $20 each, for a $2,000 order. Maya can deliver 80 on the requested date and 20 later. A useful acknowledgement preserves those two commitments. “Accepted” at the order header hides the different dates.

If the price later becomes $21, the team needs to know who agreed, which quantities the revision covers, and when the revised terms became effective. The latest total cannot explain an earlier invoice if the earlier agreement has disappeared.

Amazon's public order-acknowledgement tutorial supplies a narrow, concrete example: omitted lines are treated as rejected, and acknowledged and invoiced cost prices must align under the documented rules. It also has book-specific price fields. That is evidence about that interface, not a universal contract rule for our fictional publisher.

A capital approval answers another question

Ordering a $100,000 machine may require a business case as well as a supplier order. In our model, the business case explains why the capacity is needed and who authorized the capital. The machine supplier order describes what Mayan’s Sapiens Inc. must supply.

An internal approval does not prove Mayan accepted the machine order. Conversely, a signed supplier commitment does not prove that every internal approval was properly obtained. That can leave a real obligation alongside an internal control failure; pretending the obligation vanished would not repair the failure.

I am not assigning eComm Inc a legal conclusion here. I am preserving the questions so the responsible people can assess the actual facts.

What this changes for the participants

Maya can ask for a clear commitment before making irreversible production decisions. eComm Inc's buyer can distinguish a desirable purchase from an authorized one. The business owner can compare the expected benefit with the full cost and the alternatives, including using existing capacity.

As the customer waiting for the book, I benefit when those promises are realistic. An attractive delivery date is only useful if the parties behind it understand what they have agreed to do.

The record I would want is a small, readable chain: the need, the approved scope, the supplier's commitment, and each authorized change. That chain gives the later shipment and invoice something definite to be compared against.

Continue the series

Previous: Maya Sells to eComm Inc. Maya Also Sells Through eComm Inc.. Next: Sent, Received, Accepted: Three Different Claims. Return to the introduction and cheat sheet.

Evidence and method: public references were checked on October 18, 2026. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.