How to Set Up a Hotel Purchasing System: The Process from Request Form to Order

At first glance, purchasing in a hotel looks quite simple.

Housekeeping asks for towels.

The kitchen asks for equipment.

Reception asks for stationery.

The technical department asks for spare parts.

Management asks for office furniture.

The need is identified.

A supplier is found.

A price is obtained.

The product is bought.

But as the hotel grows, this method can very quickly get out of control.

Because soon these questions arise:

• Did we really need this product?
• Did we already have it in the warehouse?
• Who approved buying it?
• Why was this supplier chosen?
• Were other quotes obtained?
• Was the product ordered really this one?
• We ordered 100 units, but how many arrived?
• Is the product that arrived of the quality we wanted?
• Is the price on the invoice the same as the quote?
• What did we pay for this product last month?
• Have we gone over budget?

If the answers to these questions cannot be found, there is purchasing, but:

there is no purchasing system.

A professional purchasing system builds this chain:

Need → Request → Technical Definition → Quote → Comparison → Approval → Order → Delivery → Goods Receipt → Invoice → Payment → Record

The aim of this chain is not to create bureaucracy.

The aim is:

to buy the right product, at the right quality, in the right quantity, at the right time, from the right supplier, at the right total cost.

Why Is a Purchasing System Necessary?

A hotel business can buy hundreds of different products.

Some of them are products that recur:

• daily,
• weekly,
• monthly.

Others are higher-budget investments such as:

• FF&E,
• equipment,
• technology,
• furniture,
• technical systems.

If no system is set up, purchasing becomes dependent on individuals over time.

For example:

Housekeeping looks for its own supplier.

The kitchen buys from another company.

The technical department places orders directly.

Invoices arrive at accounting.

Management sees the total spend only at month-end.

This structure is not purchasing.

It is reactive spend management.

The Five Core Goals of a Good Purchasing System

A professional system should control at least five things:

1. Need

Do we really need to buy it?

2. Quality

Are we buying the right product?

3. Price

Are we buying on the right commercial terms?

4. Authority

Was it approved by the right person?

5. Record

Can the whole transaction be traced later?

When any one of these five is missing, purchasing control weakens.

Where Should the Purchasing Process Start?

Not with the supplier.

With the department.

Because the need is determined not by the purchasing department but by operations.

Housekeeping:

knows it needs towels.

The kitchen:

knows which equipment is necessary.

The technical team:

knows which part needs to be replaced.

But a department saying:

“I have a need.”

should not automatically mean:

“Buy it.”

The need should first become a:

Purchase Requisition

1. The Purchase Requisition

The starting point of the purchasing system is the purchase requisition.

Instead of placing an order directly with a supplier, the department reports its need through the system.

For example:

Even this simple form makes a very important question visible:

Why are we buying?

2. What Should a Purchase Requisition Form Contain?

A simple Purchase Requisition form can contain this information:

Request Details

• requisition number,
• request date,
• department,
• requester,
• product/service,
• quantity,
• unit,
• date needed.

Need Details

• purpose of use,
• current stock,
• minimum stock,
• reason for request,
• urgency.

Technical Details

• technical specification,
• brand/model note if required,
• quality standard,
• sample requirement.

Budget

• budget code,
• estimated cost,
• is there budget for it?

Approval

• department manager,
• relevant manager,
• purchasing,
• senior management if required.

The clearer the requisition, the more correctly purchasing proceeds.

3. A Requisition and an Order Are Not the Same Thing

This distinction is the foundation of the purchasing system.

Purchase Requisition — PR

It means:

“We need this product.”

Purchase Order — PO

It means:

“We are buying this product on these terms.”

So a department creating a requisition does not mean it has the authority to place an order with a supplier.

A PR is a need document; a PO is a purchasing commitment.

These two documents must not be confused.

4. Check Stock First

Not every request should turn directly into a purchase.

The first check:

Is the product in the warehouse?

For example, housekeeping:

requested 30 pillows.

But if there are 20 usable pillows in the warehouse, the real purchasing need may be:

not 30,

10 units.

That is why purchasing and the stock system should not work disconnected from each other.

5. Minimum Stock Can Automate the Purchase Requisition

For recurring products, the system can be set up on:

Minimum Stock — Maximum Stock

logic.

For example:

Minimum stock:

20 cartons

Maximum stock:

50 cartons

Current:

18 cartons

Order requirement:

50 − 18 = 32 cartons

This method reduces the department's approach of:

“I think it's running low, let's order a bit.”

6. Always Write the Date Needed

In a purchase requisition, it is not enough to say only:

“We need 30 units.”

This information is also needed:

When do we need them?

Because the purchasing department plans the following timelines accordingly:

• quotation,
• approval,
• production,
• shipping,
• delivery.

A request with no date needed makes purchasing priority unclear.

7. Not Every Request Should Be Marked “Urgent”

This is one of the biggest problems of purchasing departments.

If every department defines its own need as:

URGENT

no priority remains in the system.

Urgent purchasing should be used for genuinely exceptional situations.

For example:

• a critical equipment failure,
• a stock-out that will stop operations,
• a safety problem,
• an unexpected technical failure.

If a recurring product running out because of a planning error keeps creating “urgent purchases,” the problem is not in the purchasing department but in the stock or planning system.

A business that constantly makes urgent purchases is, more often than not, experiencing a planning problem, not a purchasing problem.

8. After the Request Is Approved, a Technical Definition Must Be Made

A product's name is often not enough.

For example:

“Buy 50 towels.”

Which towel?

• its size?
• its weight?
• its color?
• its composition?
• its quality standard?
• its stitching?
• its wash performance?

Or:

“Buy 30 chairs.”

Which chair?

That is why the purchase requisition says what is needed.

The technical specification says exactly what will be accepted.

9. Why Is the Technical Specification Critical?

Without a technical specification, getting prices from three suppliers often means comparing three different products.

For example:

Supplier A:

4,000 TL

Supplier B:

5,500 TL

Supplier C:

6,000 TL

At first glance A is the cheapest.

But if:

A's product offers a different material,

B's product a different size,

C's product higher durability,

this is not a real price comparison.

To compare prices, you first have to make the products comparable.

The technical specification provides that.

10. The Five Qualities of a Good Technical Specification

A good specification is:

Clear

What is wanted must be understandable.

Measurable

It should contain objective criteria as far as possible.

Feasible

It should not create requirements that have no equivalent in the market.

Verifiable

The conformity of the delivered product must be testable.

Current

The latest approved revision must be used.

The specification will be used not only to get quotes but later for goods receipt too.

11. The Quality Gate of the Purchasing Flow Is the Technical Specification

The ideal flow:

Need Identification → Purchase Requisition → Technical Specification → Quote Collection → Technical Compliance Check → Commercial Quote Comparison → Supplier Selection → Order

This sequence is very important.

Because before price evaluation, the question:

“Does the product meet our need?”

is answered.

12. Research Suppliers

After the specification is prepared, suitable suppliers should be found.

When selecting a supplier, you do not look only at:

“Who is cheaper?”

The following can also be evaluated:

• product quality,
• references,
• capacity,
• delivery time,
• payment terms,
• service,
• warranty,
• spare parts,
• product continuity.

We will cover supplier selection in more detail in the next article.

13. How Many Quotes Should Be Obtained?

Each business should define this in its own purchasing procedure.

For example, the system can be set up as:

• an approved price list for low-value routine purchases,
• multiple quotes for medium-value purchases,
• more comprehensive quotes and management approval for high-value purchases.

What matters here is not some magic number of quotes.

What matters is:

that it is written down in advance how, under what conditions, quotes will be obtained.

That way the rules do not change depending on the person or on purchasing.

14. The Request for Quotation Should Go Out with the Same Information

If Supplier A is sent different information,

Supplier B different,

Supplier C different,

the quotes cannot be compared soundly.

That is why prices should be requested with, as far as possible, the same:

• technical specification,
• quantity,
• delivery location,
• delivery date,
• warranty expectation,
• payment terms request,
• quote format.

This approach creates a true:

apples-to-apples comparison

15. Create a Quote Comparison Table

Don't leave quotes in the email inbox.

Put them in a single comparison table.

For example:

This table also makes the differences other than price visible.

16. Technical Compliance First, Then Price

For example:

A may be the cheapest.

But if it does not meet the specification, it is not the real winner of the comparison.

That is why the process should proceed as:

Technical Screening → Commercial Comparison

17. Get Sample Approval for Products That Need Samples

In products such as:

• textiles,
• amenities,
• furniture,
• porcelain,
• glassware,
• decorative items,
• printed materials

the sample can be important.

The approved sample should be put on record.

Because at delivery this question will be asked:

“Is the product that arrived the same as the one we approved?”

Without a sample, the answer to this question becomes subjective.

18. Record the Supplier Selection

The selection should not remain just:

“We're buying from company A.”

The rationale can be recorded:

• best total cost,
• technical compliance,
• shorter lead time,
• better warranty,
• better payment terms,
• existing successful supplier performance.

This provides transparency, especially for high-budget purchases.

19. Create an Approval Matrix

Not everyone should be able to approve purchases of any amount.

Each business should create an:

Approval Matrix

according to its size.

For example, only to show the logic of the system:

Amounts should be set according to each hotel's size and organization.

But the principle does not change:

As the purchase amount grows, the approval level should rise.

20. The Requester, Approver, and Buyer Should Be Separated as Far as Possible

An important internal control principle:

the same person should not manage the whole process alone.

If the same person, for example:

requests the product,

selects the supplier,

places the order,

receives the goods,

approves the invoice,

and makes the payment,

the control mechanism is very weak.

In small boutique hotels full segregation of duties may not always be possible.

But at least for critical purchases, the control points of:

Request → Approval → Purchasing → Goods Receipt → Payment

should be separated.

21. What Is a Purchase Order — PO?

The supplier has been selected.

The price has been approved.

The terms have been set.

Now a:

Purchase Order

is created.

A PO is the formal purchasing instruction given to the supplier.

A simple PO can contain:

• PO number,
• supplier,
• product,
• technical description,
• quantity,
• unit price,
• total,
• tax information,
• delivery date,
• delivery address,
• payment terms,
• warranty,
• other commercial terms.

22. Why Is the PO So Important?

Saying on the phone:

“Send 500 of the same towels as last time.”

is easy.

But then these questions can arise:

Which model?

Which price?

Which size?

When is delivery?

Is freight included?

What are the payment terms?

The PO fixes all of these terms in a single document.

The PO is the commercial memory of a purchasing decision.

23. Use PO Numbers

Every order should carry a unique number.

For example:

PO-2026-042

The related purchase requisition could be:

PR-2026-015

That way, later on, the chain of:

PR → Quote → Approval → PO → Delivery → Invoice

can be tracked.

24. Minimize Verbal Orders

In small businesses in particular, purchasing is often done by:

phone,

WhatsApp,

email.

These communication tools can be used.

But it is healthier for the final order to be tied to a PO recorded in the system.

Because six months later, the answer to:

“At what price did we order this?”

should not be searched for in WhatsApp history.

25. The Process Does Not End When the Order Is Placed

The purchasing department's job should not end with sending the PO.

The order should be followed up:

• Was the PO sent?
• Did the supplier confirm?
• Has production started?
• Has the delivery date changed?
• Has it been shipped?
• Has it reached the hotel?

This follow-up becomes critical in pre-opening FF&E and OS&E purchasing in particular.

26. Create an Open PO List

For orders that are not yet complete, an:

Open Purchase Orders

list can be kept.

For example:

This list can be one of the purchasing department's daily control screens.

27. When the Delivery Arrives, Compare It with the PO

The truck has arrived.

The products have been unloaded.

The delivery note has been signed.

Is the process complete?

No.

The first question:

Did we actually order these products?

The delivery must be compared with the PO.

28. Do Not Automatically Accept the Quantity on the Delivery Note as Correct

The delivery note may say:

50 chairs

The physical count may show:

47 chairs

The goods receipt record should be made as:

47 received / 3 missing

The quantity in the document and physical reality do not have to be the same.

29. Set Up a Goods Receiving System

At delivery, at least these checks can be made:

Quantity

How many arrived?

Product

Is it the right product?

Technical Specification

Does it meet the specification?

Quality

Is it at the expected quality level?

Damage

Is there any transport damage?

Sample

Is it the same as the approved sample?

Documents

Is it consistent with the PO and delivery note?

After these checks:

Goods Receipt

is carried out.

30. Receiving Delivery and Accepting It Are Not the Same Thing

This distinction is very important.

The truck dropped the product at the hotel.

That means:

the product physically arrived

But it should not mean:

the product was accepted

For example:

100 towels arrived.

20 are outside the specification.

In this case, a record can be created of:

80 units accepted,

20 units rejected.

Not every product delivered is a product that was ordered and should be accepted.

31. Create a Non-Conformance Record

For problematic deliveries, a:

Non-Conformance

record can be kept.

For example:

• short quantity,
• wrong model,
• wrong color,
• damaged product,
• size error,
• quality problem,
• late delivery.

The resolution can then be recorded as:

• replacement,
• completion,
• return,
• discount,
• re-production.

These records can later be used to measure supplier performance.

32. Three-Way Match

One of the most powerful and simplest tools of purchasing control is the:

Three-Way Match

The three documents compared:

1. Purchase Order

What did we order?

2. Goods Receipt

What did we receive?

3. Invoice

What were we billed for?

For example:

If everything matches, the payment process can proceed.

33. What Mistakes Does the Three-Way Check Catch?

For example:

PO:

100 units

Delivery:

90 units

Invoice:

100 units

If accounting looks only at the invoice:

100 units may be paid.

The Three-Way Match catches the difference.

Another example:

PO price:

1,000 TL

Invoice price:

1,100 TL

Even if the quantity is right, a price mismatch emerges.

34. You Can Strengthen Control Even Further for High Amounts

For important purchases in particular, the chain:

Purchase Requisition → Purchase Order → Goods Receipt → Invoice

can be controlled at four points.

This system answers these questions:

• Was there a need?
• Did an authorized person place the order?
• Did the product really arrive?
• Was the right amount invoiced?

35. How Should Invoice Control Be Done?

The invoice should be checked before it enters the payment queue.

For example:

• is the supplier correct?
• is the invoice date correct?
• is there a PO link?
• is the product correct?
• is the quantity correct?
• is the unit price correct?
• is the discount correct?
• is the tax correct?
• is the total correct?
• is it consistent with the quantity received?
• are the payment terms correct?

Making sure no payment is made before the check is complete creates a healthy system.

36. Keep the Purchasing File as a Single Chain

For important purchases, the file can be organized like this:

1. Purchase Requisition
2. Quotes
3. Quote Comparison
4. Supplier Selection
5. Technical Specification
6. Sample / Approval
7. Purchase Order
8. Delivery Note
9. Goods Receipt
10. Invoice
11. Payment Document
12. Purchasing Closure Record

That way the whole transaction can be traced backward even years later.

37. Give Every Document a Unique Number

For example:

Purchase requisition:

PR-2026-015

Purchase Order:

PO-2026-042

Delivery note:

DN-2026-118

Invoice:

INV-2026-356

If these documents are linked to one another, it becomes easy to reach the entire history of a single purchase.

38. Is ERP Necessary in a Small Hotel?

No.

In a small boutique hotel, basic purchasing control can be set up with a well-designed:

• Excel,
• Google Sheets,
• digital form,
• accounting system.

In larger businesses, the following can be used:

• ERP,
• a stock management system,
• accounting integration,
• an e-procurement system.

But the basic principle is this:

Bad process + good software = a digitized bad process.

The system must be built first.

The right order:

Procedure → Authority → Standard → Data → Software

39. The Purchasing Procedure Must Be Written

The procedure should answer at least these questions:

• Who can create a request?
• Who can approve?
• What approval is needed at what amount?
• How many quotes are obtained?
• How are quotes compared?
• How is the supplier selected?
• Who creates the PO?
• Who performs goods receipt?
• Who does quality control?
• Who checks the invoice?
• Who approves payment?
• How is urgent purchasing done?

The answers to these questions should be in the system, not in employees' heads.

40. Minimum Purchasing Document Set

For a hotel's basic purchasing system, the following documents can be created:

• purchasing procedure,
• approval matrix,
• purchase requisition form,
• request for quotation form,
• quote comparison form,
• supplier information form,
• Purchase Order,
• goods receipt form,
• quality control form,
• invoice control form,
• supplier performance form,
• urgent purchase form.

All of these do not have to be physical.

They can also be managed digitally.

41. Build a Purchasing Database

Every purchase transaction produces data that can be used in the future.

Topics that can be tracked:

• most-purchased products,
• most-used suppliers,
• price changes,
• department-level spend,
• monthly purchase amounts,
• budget variances,
• urgent purchases,
• delivery performance.

After a few years, this data becomes very valuable to the business.

For example:

“What did we pay for this product last year?”

can be answered in a few seconds.

42. Keep a Purchase Price History

Especially for frequently bought products, a price history can be kept.

For example:

That way price increases and supplier differences are easier to see.

43. Create Purchasing KPIs

It is inadequate to measure the purchasing department only by:

“How much discount did we get?”

For example, these KPIs can be tracked:

Purchase Spend

Total purchase amount.

Budget Variance

Deviation from budget.

Emergency Purchase %

The rate of urgent purchases.

On-Time Delivery %

The rate of on-time delivery.

Rejection Rate

The rate of products rejected at goods receipt.

Supplier Lead Time

Supply time.

Price Variance

Price change.

Purchase Order Compliance

The share of purchases made through the PO system.

These indicators show the health of the system.

44. Use the “Savings” KPI Carefully

If you give the purchasing manager only the goal of:

“Find the lowest price.”

quality can fall.

For example:

An 80 TL product is bought instead of a 100 TL one.

A 20% saving shows up.

But if the product breaks in half the time, the business may actually have spent more.

That is why purchasing performance should be evaluated as:

Price + Quality + Delivery + Total Cost

together.

45. Report Urgent Purchases Separately

The number of urgent purchases is an important management indicator.

For example, in a month:

100 POs were created.

25 of them were urgent.

Emergency Purchase Rate = 25%

If this rate is constantly high:

• stock levels may be wrong,
• department planning may be weak,
• supply time may have been miscalculated,
• the request system may not be working.

So urgent purchasing is not only the purchasing department's problem.

46. Purchasing and Budget Should Be Linked

When a department creates a request, the system should ask this question:

Is there money in the budget?

For example:

Housekeeping annual textile budget:

1,000,000 TL

Actual + Committed:

920,000 TL

New request:

150,000 TL

If the request is approved, the total will be:

1,070,000 TL

That is, the budget overrun can be seen before the order is placed.

A good purchasing system catches budget overruns at the request stage, not on the invoice.

47. A Simple System for a Small Boutique Hotel

In a boutique hotel of 10–20 rooms, for example, the purchasing system should not be unnecessarily heavy.

A simple model:

1. The department creates a digital PR.
2. The manager approves the need.
3. Stock is checked.
4. If needed, quotes are obtained.
5. Quotes are compared.
6. Approval is obtained according to the authority limit.
7. A PO is created.
8. The product is received.
9. PO + Goods Receipt + Invoice are matched.
10. Payment is made.

This system can be controlled enough for a small hotel yet simple enough not to bog down operations.

48. How Does the System Change in a Large Hotel?

As the hotel grows, systems such as the following can come into play:

• a purchasing department,
• a central warehouse,
• department budgets,
• ERP,
• electronic approval,
• a supplier portal,
• contract management,
• automatic reorder,
• central price lists.

But the basic logic does not change:

Who asked? → Why did they ask? → Who approved? → Who did we buy from? → Why did we choose them? → What did we order? → What arrived? → What was invoiced? → What did we pay?

49. 12 Common Mistakes in a Purchasing System

1. Departments ordering directly from suppliers

It breaks the control chain.

2. Not using a request form

The source of the need is invisible.

3. Buying without checking stock

It creates unnecessary stock.

4. Not creating a technical specification

Prices of different products get compared.

5. Choosing only the lowest price

Total cost and quality are overlooked.

6. Not defining authority limits

The approval system becomes dependent on individuals.

7. Placing verbal orders

The proof of commercial terms is weakened.

8. Not creating a PO

The link between the order and the invoice is broken.

9. Accepting the quantity on the delivery note without a physical count

Short deliveries may go unnoticed.

10. Paying without goods receipt

Quality control is lost.

11. Not matching the invoice with the PO

Price and quantity errors can slip through.

12. Not retaining purchasing data

Every purchase starts from scratch.

50. 10 Decision Gates for a Hotel Purchasing System

Every purchase can go through these ten gates.

Decision Gate 1 — Need

Is it really necessary?

Decision Gate 2 — Stock

Is it available in the warehouse?

Decision Gate 3 — Budget

Is there budget for it?

Decision Gate 4 — Standard

Is exactly what we will buy defined?

Decision Gate 5 — Quote

Have market conditions been compared?

Decision Gate 6 — Supplier

Has the right supplier been chosen?

Decision Gate 7 — Authority

Did the right person approve?

Decision Gate 8 — PO

Is the order written and recorded?

Decision Gate 9 — Goods Receipt

Was the right product actually delivered?

Decision Gate 10 — Invoice

Are the order, delivery, and invoice consistent with one another?

When these ten gates are complete, the purchase has been brought under control.

51. Hotel Purchasing System Checklist

Organization

• ☐ Purchasing owner identified.
• ☐ Department responsibilities identified.
• ☐ Approval matrix created.
• ☐ Approval limits determined.
• ☐ Segregation of duties achieved as far as possible.

Request

• ☐ Purchase Requisition form exists.
• ☐ Every request is numbered.
• ☐ Reason for request is written.
• ☐ Date needed is written.
• ☐ Current stock is checked.
• ☐ Budget is checked.

Technical Standard

• ☐ Product specification exists.
• ☐ Technical specification exists for necessary products.
• ☐ Sample system exists.
• ☐ Latest revision is tracked.

Quote

• ☐ Quote-gathering rule is written.
• ☐ The same specification is sent to all suppliers.
• ☐ Quotes are compared in a single table.
• ☐ Technical compliance is checked.
• ☐ Commercial terms are compared.

Supplier

• ☐ Supplier registration system exists.
• ☐ Supplier selection is justified.
• ☐ Delivery performance is measured.
• ☐ Quality performance is measured.

Order

• ☐ Purchase Order is used.
• ☐ Every PO has a unique number.
• ☐ Price is stated on the PO.
• ☐ Quantity is stated.
• ☐ Delivery date is stated.
• ☐ Payment term is stated.
• ☐ An Open PO list is kept.

Delivery

• ☐ Delivery note is checked.
• ☐ Physical count is done.
• ☐ Technical compliance is checked.
• ☐ Damage inspection is done.
• ☐ Goods receipt record is created.
• ☐ Rejected/short products are recorded.

Invoice

• ☐ Matched with the PO.
• ☐ Matched with goods receipt.
• ☐ Quantity is checked.
• ☐ Unit price is checked.
• ☐ Tax and total are checked.
• ☐ Payment term is checked.

Reporting

• ☐ A monthly purchasing report is prepared.
• ☐ Department spend is tracked.
• ☐ Budget variance is tracked.
• ☐ Urgent purchase rate is tracked.
• ☐ Price history is kept.
• ☐ Supplier performance is tracked.

The Full Flow of the Purchasing System

If we show a professional purchasing process as a single chain:

Need Identification → Stock Check → Purchase Requisition → Budget Check → Approval → Technical Specification → Supplier Research → Request for Quotation → Technical Compliance → Commercial Comparison → Supplier Selection → Authority Approval → Purchase Order → Order Follow-Up → Delivery → Physical Count → Quality / Technical Check → Goods Receipt → Warehouse Entry → Three-Way Match → Invoice Control → Payment → Purchasing Record → Supplier Performance

Once this chain is in place, purchasing stops depending on individuals.

It becomes dependent on the system.

The Core Principle of the Purchasing System

A hotel's purchasing system is not set up merely to find a lower price.

The real aim is to control, in the same chain:

the correctness of the need,

the quality of the product,

the competitiveness of the price,

the correctness of authority,

the conformity of delivery

and

the correctness of payment.

That is why:

The purchase requisition shows what we need, the technical specification shows what we will accept, the PO shows what we ordered, the goods receipt shows what we received, and the invoice shows what we will pay.

When these documents are linked to each other, the purchasing system emerges.

Conclusion

The purpose of setting up a hotel purchasing system is not to make departments' work harder.

On the contrary:

to plan needs,

to reduce unnecessary purchases,

to prevent surplus stock,

to buy the right product,

to compare prices,

to reduce unauthorized spending,

to see delivery problems,

to catch invoice errors,

to control the budget,

and to turn purchasing history into institutional memory.

In a small boutique hotel this system can be simple.

In a large hotel it can run on ERP.

But regardless of the size of the system, the basic logic is the same:

No need, no request.
No request, no purchase.
No standard, no right quote.
No approval, no order.
No PO, no order control.
No goods receipt, no invoice verification.
No control, no payment.

And perhaps the most important result of the purchasing system is this:

It turns the question “Who can we buy from more cheaply?” into the question “Which product, at which quality level and at what total cost, best meets our business's need?”

This is exactly what good purchasing management is.

Hotel Investment Guide — Volume IV: Procurement & Equipment

From the purchase requisition to the technical specification, from quote comparison to supplier selection, and through the Purchase Order, goods receipt, Three-Way Match, invoice control, and purchasing reporting, I cover the whole system in more detail in Hotel Investment Guide — Volume IV: Procurement & Equipment.