Página inicial
Produtos
Armazenamento na casa de banho Armazenamento na cozinha Organizadores de duche Cestos de arame Toalheiros Ver todos os produtos
Fabrico por encomenda Fábrica Qualidade Blogue Contacto

Conhecimentos sobre o aprovisionamento de hardware

Purchase Requisition vs Purchase Order: Separate Internal Approval from Supplier Ordering

Learn how a purchase requisition differs from a purchase order, who receives each document, and what a supplier needs before an order is released.

Purchase requisition vs purchase order shown as blank supplier documents with a metal hardware sample

The purchase requisition vs purchase order distinction is that a requisition generally requests internal approval, while a purchase order is the buyer’s supplier-facing order document. They may contain overlapping details such as item, quantity, cost center, and requested date, but they serve different audiences and document states. Approval of an internal requisition should not be assumed to instruct an outside factory to begin work. Buyers and suppliers should identify the released order, the approved scope, and the communication that authorizes the next action under their actual process.

The distinction matters when a procurement team approves a custom hardware reorder or new product run. An employee may submit a requisition, managers may review it, and purchasing may later issue an order with the supplier-facing details. The supplier needs a clear, controlled order and agreed project documents. A requisition number can help the buyer’s internal tracking, but it is not automatically the supplier’s production instruction.

The central difference: internal request versus external order

A purchase requisition (often shortened to PR) is typically an internal document used to request approval or budget for a purchase. Its issuer is an employee, department, project team, or other buyer-side requester, depending on the organization’s process. Its audience is usually internal approvers and procurement staff. It can help explain what is wanted and why, but it may still be incomplete, unapproved, or subject to review.

A purchase order (PO) is generally the buyer’s external purchasing document sent to a supplier. It communicates an order’s commercial and delivery scope, such as item identity, quantity, price basis, dates, destination, terms, and referenced specifications. The exact fields and effect vary across buyer processes and agreements. The supplier should not infer a universal legal result from the phrase “purchase order”; the parties’ terms, communications, and applicable rules matter.

A requisition and a purchase order may relate to the same planned purchase, but one does not substitute for the other. The internal request helps a buyer decide whether to purchase. The supplier-facing PO communicates the buyer’s released order. Some organizations use software and additional approval steps; others use different forms. The terminology and sequence may vary, so the parties should confirm the specific document state that applies.

Document question Purchase requisition Purchase order
Primary audience Internal requester, approvers, procurement Supplier and buyer’s order administration
Main purpose Request and support internal purchase approval Communicate an order to an external supplier
Typical status Draft, submitted, pending, approved, rejected or returned; labels depend on system Draft, approved, issued, acknowledged, revised or closed; labels depend on process
Typical content Need, requested item, reason, budget/cost code, suggested timing Item/specification, quantity, price basis, delivery, ship-to, terms and references
Supplier action Usually not enough by itself to release work The supplier reviews the issued order against quote and agreed scope
Buyer control Internal authorization and budget tracking External order content, revision and release communication
What the name alone proves Not that an outside supplier has been instructed Not every legal or contractual consequence in all circumstances

This is a general buyer-education map, not a procurement standard. Pipefy’s workflow explanation also distinguishes internal purchasing permission from a vendor-directed order, while organizational systems may implement their own roles, statuses, and controls. Buyers should document their actual procedure and not assume software labels are universal.

Follow the document state, not only the document title

A purchase requisition vs purchase order review should therefore verify the request status and the supplier-facing release separately.

A document’s name is only one clue. The buyer should confirm whether it is a request, an approved authorization, a draft PO, an issued PO, a supplier-acknowledged order, or a later revision. A requisition can be submitted but not approved. A PO can exist as a draft but not be released. An order may have been issued and later revised or canceled. The status and intended recipient determine what action is appropriate.

A careful process might look like this, though not every organization uses the same steps:

  1. Need identified: a team decides it needs an item or service.
  2. Internal request prepared: the requester records the need, quantity, timing, specifications, and estimated cost if required.
  3. Internal review: authorized people review budget, scope, supplier, or other controls according to the buyer’s process.
  4. Purchase decision: the organization approves, rejects, returns, or changes the request.
  5. Supplier-facing order prepared: purchasing translates the approved need into a PO with current supplier-facing details.
  6. Order issued: the PO is sent through the agreed channel to the supplier.
  7. Supplier review: the supplier checks whether the order matches its quotation, capacity, specifications, and agreed terms, then responds under the parties’ process.
  8. Change controlled: any change to item, quantity, revision, delivery or commercial terms is documented and communicated.

This sequence is illustrative, not a claim that every company uses an eight-step workflow or the same status names. The important point is to avoid skipping from an internal need directly to supplier production without confirming the approved external instruction. If a buyer’s process has a defined release trigger, make that trigger explicit to the supplier.

A supplier may receive emails, drawings, sample notes, and an ERP-generated PO in separate messages. The project team should clarify which communication controls if those documents conflict. A quote might refer to one drawing revision while the PO attaches another. A purchase requisition may include a requested date that was not confirmed with the factory. A complete order exchange resolves these discrepancies before work proceeds.

What belongs in a supplier-facing PO?

The PO should communicate enough information for the supplier to identify the transaction and understand the agreed order scope. The exact content depends on the purchase and the buyer’s process. For custom metal hardware, useful fields may include:

  • Buyer and supplier legal or trading names as used in the order.
  • PO number, issue date, and revision or amendment reference.
  • The supplier quote or proposal being accepted, including its date and revision.
  • Item identifier, clear product description, quantity, unit, and price basis.
  • Drawing number and revision, approved sample reference, or specification attachment.
  • Finish, color, packaging, labeling, and private-label requirements where applicable.
  • Delivery location, requested date, shipping instructions, and relevant delivery terms as agreed.
  • Payment terms and other commercial fields as defined by the buyer and supplier.
  • Contact for order questions and the accepted channel for revisions.
  • Any exclusions, open items, or assumptions that remain unresolved.

The order should reference controlled specifications rather than rely on a vague product name. “Bathroom basket” or “custom rack” may not distinguish models, dimensions, finish, mounting method, or packaging. If the PO references a drawing, attach or identify the exact revision and confirm the supplier has it. If the order depends on a sample, state which sample is approved and for what purpose.

A requisition may have some of the same fields because internal approval requires a cost and a description. However, an internal request may use provisional estimates or internal accounting information that should not be sent to the supplier. The purchasing team should verify which information is approved for external disclosure and ensure that the PO is not just a copy of an unreviewed requisition.

For international purchases, a PO can be one of several documents in the order record. It may be reconciled with a quotation, pro forma invoice, commercial invoice, packing list, shipment records, and receiving information. The PO does not replace those records or guarantee that the goods have been delivered or accepted.

Three blank procurement sheets arranged beside a plain folder and metal hardware sample

A practical custom hardware example

Imagine an importer plans a repeat order for a wall-mounted metal storage product. The category team estimates the quantity and requests approval. The requisition might state the requested product family, target quantity, intended delivery window, project reason, and estimated spend. An internal manager or finance process may approve, reject, or return it for clarification. That internal action does not itself confirm the final finish, drawing revision, packaging, delivery destination, or current supplier lead time.

After internal approval, the buyer’s procurement team prepares the PO. It references the supplier’s current quote, exact SKU or project number, approved drawing revision, finish, packaging, quantity, delivery destination, and agreed commercial terms. The buyer sends it to the supplier. The supplier compares it with the quotation and flags conflicts or missing information before acknowledging the order under the agreed process.

If the internal requisition says “black finish” but the quote and drawing say “brushed nickel,” the PO must resolve the discrepancy rather than silently choose one. If the buyer’s target date came from an internal planning assumption, it should not appear as a supplier-committed delivery date without confirmation. If the new order changes a box label, screw kit, or approved drawing, include that change in the controlled supplier communication.

This example is hypothetical; it does not describe Koitor’s internal purchasing system or promise a production schedule. Its purpose is to show why a buyer separates internal authorization from supplier instructions. A clear PO helps both sides identify what is being ordered and what reference controls. The supplier still needs to review the order against its quote and agreed production scope.

When a requisition is approved but the supplier has no PO

An approved requisition means that an internal step has been completed according to the buyer’s process; it does not necessarily mean that a supplier has received an order. A sourcing or finance dashboard may display “approved” prominently, but that status may be invisible to the supplier. The buyer should confirm whether procurement has generated and issued the PO and whether the supplier has received the current version. For the supplier follow-up stage, see what to check before assuming production has started.

If a supplier asks whether to start, the buyer should not answer from an internal requisition number alone unless the parties have explicitly agreed that this is an authorized instruction. Confirm the released PO or the agreed order authorization channel, the specifications, and any required payment or sample milestone. If the buyer uses a different document as the release instruction, describe that process clearly and identify its controlling revision.

A simple communication checklist can prevent confusion:

  • Has the buyer approved the purchase internally?
  • Has a supplier-facing order been created?
  • Is the order released or still a draft?
  • Was it sent to the correct supplier contact and channel?
  • Does the supplier acknowledge the same quantity and revision?
  • Are quote, drawing, finish, packaging, and delivery details consistent?
  • Are any commercial or technical conditions still open?
  • Which message or document controls if records disagree?

Do not expose internal budget limits, requester names, or private approval notes unless the buyer intentionally shares them. A supplier generally needs the released scope, not every internal step. Keep the internal control record separate from the external order while preserving cross-references such as the requisition number or project code when useful.

Common mistakes in PR and PO handling

Treating the terms as synonyms

A requisition generally supports an internal request, while the PO communicates the supplier-facing order. Using the terms interchangeably can lead to work starting before the buyer has released the agreed scope.

Assuming requisition approval means production release

Internal approval and external communication are separate events in many processes. Confirm that the buyer has issued the approved order and that the supplier understands what it covers.

Sending a draft or incomplete PO

A draft may contain provisional quantity, dates, prices, or specifications. Mark the status clearly and do not expect the supplier to treat it as final unless the parties’ process says otherwise.

Copying internal estimates into a PO as commitments

A requested delivery date or estimated cost on a requisition may be an internal planning input. Confirm the quote and supplier agreement before representing a date or price as approved externally.

Omitting quote and drawing revisions

An order that refers to an old quote or drawing can create competing versions. Identify the accepted quote, drawing revision, approved sample, and any amendments.

Treating a PO as proof that the supplier accepted every term

The buyer’s document is important, but the parties’ agreement and applicable rules determine legal effects. Do not make blanket legal claims. Use the organization’s contract or legal owner for that question.

Failing to communicate changes

Changing quantity, finish, packaging, ship-to details, or revision through an internal system does not guarantee the supplier has the update. Send controlled amendments through the agreed channel and obtain confirmation where required.

Confusing order authorization with receipt or payment

A PO records an order; it does not by itself prove goods were received, inspected, invoiced, paid, or accepted. Those events have their own records. Use the appropriate documents for each stage.

Sharing confidential internal approval information

A requisition can include internal budgets, cost centers, or approver comments. Check what should be shared externally and send only the information needed to execute the supplier-facing order.

Coordinate purchasing with technical and supplier teams

A purchase order can only communicate the scope that the buyer has defined. Purchasing may coordinate the order, but product, engineering, quality, logistics, and finance teams may own different inputs. For a custom hardware project, a technical owner should confirm the controlled drawing and product revision; the buyer should confirm quantity and commercial terms; quality should identify applicable inspection or records; logistics should align destination and packaging; and the supplier should identify its assumptions or deviations.

Not every organization has the same department structure, approval sequence, or ERP. The buyer should use its own authorized process and make the supplier-facing instruction clear. This article does not provide procurement software implementation, accounting advice, or a legal determination.

A purchasing record may link the requisition and PO numbers for auditability. That cross-reference helps trace why the order was created. It should not imply that the requisition itself is the supplier’s controlling order. Similarly, an internal change request may be needed before a PO revision, but the supplier must still receive the actual approved change if it affects the work.

For a metal hardware order, internal request detail may begin with a product family and budget. The released PO should be specific enough to identify the offered item and current requirements. If material, finish, mounting, packaging, or private-label details are unresolved, the buyer should address them before release or clearly document them as pending and agree how they will be closed. Do not use an external order to disguise an unapproved technical choice.

What a supplier should confirm after receiving a PO

A supplier’s review can help catch document mismatches before work starts. The buyer should agree how the supplier will acknowledge receipt or raise a question. Depending on the transaction, a useful acknowledgment may confirm order number, items, quantities, quote basis, current drawing or sample reference, delivery destination, requested timing, and open deviations. The acknowledgment is a communication step; the exact commercial effect depends on the parties’ arrangement.

If the supplier sees a conflict between the PO and prior quote, the supplier should identify it rather than choose silently. For example, a difference in finish, packaging or drawing revision should be clarified in writing. The buyer should then update or confirm the controlling record through its authorized process. A phone conversation may help resolve the issue, but record material changes in the agreed written system.

The buyer should also identify whether there are conditions before work can begin, such as sample approval, deposit, artwork, or another milestone. Those conditions vary by project and agreement. State them explicitly and verify both sides understand the sequence. Do not infer that an internal approval status has satisfied an external milestone.

For a related supplier follow-up question, see what to check before assuming production has started.

Buyer checklist before sending a purchase order

  • Has the requisition or other internal approval completed the buyer’s required process?
  • Is the PO in a released/issued state rather than a draft?
  • Does the supplier name match the intended contracting or purchasing entity?
  • Does the PO reference the accepted quotation and current revision?
  • Are item, quantity, unit, price basis and delivery details clear?
  • Are drawings, specifications, finish and approved sample references current?
  • Are packaging, labels, private-label and shipment instructions included where needed?
  • Are payment and other commercial terms aligned with the accepted scope?
  • Are assumptions, exclusions and pending items clearly stated?
  • Has the PO been sent through the agreed communication channel?
  • Is supplier acknowledgment or discrepancy confirmation required?
  • Who can authorize amendments, and how will changes be recorded?
  • Are internal requisition data and external supplier details separated appropriately?
  • Does each document point to the same product, revision, quantity and destination?
Two blank procurement sheets beside a plain folder, pencil, and metal hardware sample

The purchase requisition vs purchase order distinction is practical: internal approval supports the buyer decision, while the released supplier order communicates the purchase scope. Confirm status before asking a factory to proceed.

Perguntas frequentes

What is the main difference between a purchase requisition and a purchase order?

A requisition is generally an internal request for purchase approval. A purchase order is generally the buyer’s supplier-facing order. Their audiences, purpose, and document state differ even when some details overlap.

Does an approved requisition tell a factory to start production?

Not necessarily. Internal approval may not be visible to the supplier or constitute the agreed external order instruction. Confirm the released PO or the specific authorization channel that the buyer and supplier have established.

Can a purchase requisition be sent to a supplier?

Some organizations may share request information, but the document’s normal internal purpose does not automatically make it a supplier-facing order. If a buyer uses a different process, clearly identify the controlling authorization and approved scope.

Is every purchase order legally binding?

The legal effect depends on the parties’ agreement, communications, and applicable rules. This article does not offer a legal determination. Consult the organization’s qualified legal or contract owner for a specific question.

Can a PO include details that were not in the requisition?

It can include supplier-facing specifications, quote references, delivery and commercial details that become clear during procurement. The buyer should ensure those details are properly approved under its process and consistent with the supplier’s quotation.

What should I do if a PO conflicts with the quote?

Pause the affected instruction and identify the conflicting fields—such as quantity, revision, finish, price, or delivery. Resolve the discrepancy through the buyer’s authorized process and communicate the controlling order version to the supplier.

Is a PO proof that goods were received or paid?

No. A PO records an order. Receiving, inspection, invoicing, payment and acceptance are separate events with their own records and controls.

Should the supplier acknowledge a PO?

The buyer and supplier should follow their agreed process. An acknowledgment can help confirm receipt and identify mismatches, but its exact meaning depends on the transaction and does not replace clear order terms.

Trabalhe com a Koitor Hardware

For a custom bathroom or home-storage hardware order, send the released purchase order together with the current quote reference, drawing revision, finish, packaging, quantity, and delivery details. Koitor can review the supplier-facing scope within its confirmed manufacturing capabilities and flag mismatches or missing information before the order proceeds.

Discuss released order and drawing scope with Koitor Hardware.

Send your drawing, sample, target quantity, finish, packaging, and project questions for a scope discussion.

Discuta o seu projeto
Review OEM Hardware Scope

OEM / MARCA PRÓPRIA

Transforme este guia de fornecimento num resumo do produto

Indique o produto pretendido, as dimensões, o acabamento, a quantidade a encomendar e os requisitos de embalagem. A sua equipa receberá uma análise prática da viabilidade de fabrico antes da apresentação do orçamento.