Accueil
Produits
Rangements pour la salle de bains Rangements de cuisine Paniers de douche Paniers en fil métallique Porte-serviettes Voir tous les produits
Fabrication sur mesure Usine Qualité Blog Contact

Connaissances en matière d'approvisionnement en matériel informatique

Purchase Order vs Sales Order: Follow the Buyer and Seller Records

Purchase order vs sales order describes two records from opposite sides of a transaction. The buyer issues a purchase order (PO) to request defined goods or services; the seller may create a sales order (SO) to…

Purchase order vs sales order shown as separate buyer and seller procurement records

Purchase order vs sales order describes two records from opposite sides of a transaction. The buyer issues a purchase order (PO) to request defined goods or services; the seller may create a sales order (SO) to record and manage its response to that request. The records can refer to the same planned order, but they serve different organizations and may not match automatically. For an importer buying custom bathroom or home-storage hardware, compare item, quantity, unit, price basis, destination, dates, packaging, and revisions. Resolve every discrepancy with the authorized parties instead of treating a document title as proof of acceptance, payment, production release, or delivery.

What is a purchase order and who issues it?

A purchase order is a buyer-side purchasing record that identifies what the buyer is requesting from a supplier. Its details may include the buyer’s and supplier’s identities, product or service description, quantities, pricing basis, requested delivery information, payment terms, and references to specifications or other agreed documents. The exact fields vary by company and transaction. A PO helps the buyer communicate and track the requested scope through its own purchasing process.

The accounting-software publisher Sage explains the basic direction as a purchase order from buyer to seller and a sales order created by the seller in response. Procurement-software publisher Precoro describes the PO as the buyer’s request and the SO as the seller-side record. These are useful explanations of common business practice; neither page establishes the legal status or approval workflow of a specific transaction. Those questions depend on the actual documents, authority, agreement, and governing circumstances and are outside this article’s scope.

For a hardware importer, the PO may point to a product drawing, sample approval, packaging instruction, BOM, or quotation. Those references are important because the line-item title alone may not describe a customized product fully. If the PO says “bathroom shelf” but the controlled drawing contains the material, finish, dimension and packaging requirements, verify that the PO references the correct drawing revision and quote. Do not assume the supplier can infer which version the buyer intended.

Record field Buyer-side PO question Why it matters when compared with a seller record
Item/part number Which product or component is being requested? Similar descriptions may refer to different revisions or configurations
Quantity and unit How many units, sets, cartons, or other units are ordered? Unit mismatches can change the apparent quantity or price basis
Price basis Which currency, unit price, and included scope are referenced? A seller record may summarize a quote differently
Specification reference Which drawing, sample, finish or packaging instruction applies? Custom scope often sits outside the short item name
Destination Where should the goods be delivered or made available? A different address or delivery point can change the order scope
Requested dates Which date is requested and what does it mean? Request, confirmation and shipment dates are not interchangeable
Revision/exception Which approved terms or changes are included? Unrecorded revisions can split the parties’ understanding

The PO is the buyer’s view of the requested purchase. It should be complete enough for the buyer’s own approvals and for the supplier to identify what is being requested, subject to the agreed commercial and technical process. A buyer should avoid treating an internal PO number as the supplier’s order number unless the parties explicitly map those references.

What is a sales order and who issues it?

A sales order is commonly a seller-side record that reflects how the seller has entered or is managing an order. It may refer back to the buyer’s PO and summarize items, quantities, prices, delivery information, or seller-side processing details. It is often used within the seller’s systems and communications. Its format and role vary by organization; not every supplier uses a document called a sales order or the same field layout.

Sage’s explanation notes that a seller-side SO can confirm or manage the seller’s response and that an invoice is a separate document used to request payment. This distinction is important for procurement: a sales order is not the goods themselves, not a payment receipt, and not necessarily the only record needed for a project. Likewise, a pro forma invoice, commercial invoice, quotation, order acknowledgment, or order confirmation has its own role. Buyers should identify each document by the purpose agreed in the transaction rather than assume one name replaces another.

A seller may generate an SO from a buyer PO, a quotation, or another approved communication, depending on its process. That does not prove that every field was copied correctly or that every exception was accepted. A buyer should read the details and check the seller’s reference back to the originating PO and current specifications. If the seller’s system uses different labels, ask which record is the operational acknowledgment and where changes are shown.

For a customized hardware order, an SO might show a commercial line item while an attachment or reference carries the technical configuration. The buyer should verify that the attached drawing, sample status, packaging instruction and order line all point to the same product. The document may help the seller manage its side, but the presence of an SO does not itself verify manufacturing capability, production status, quality acceptance, or shipment readiness.

How does the purchase order vs sales order relationship work?

The documents can be understood as a two-sided record map. The buyer’s PO communicates the requested purchase; the seller’s SO may record the seller’s corresponding order entry or response. The comparison is useful because it can reveal whether both sides are discussing the same products and conditions. It should be treated as a reconciliation step, not an assumption that the documents match or that a particular legal consequence follows.

Consider a hypothetical purchase of custom towel bars. The buyer’s PO refers to a quotation, a defined finish, a drawing revision, an order quantity, a destination, and a requested delivery window. The seller’s SO arrives with the same product name but a different finish code and a later date. The buyer should not silently accept the changed fields or assume they are typographical errors. The responsible buyer and seller should identify each exception, determine which one is intended, and record a clear resolution before the transaction proceeds under the parties’ process. This is an illustrative case, not a Koitor customer order or legal scenario.

Transaction stage Buyer-side record Seller-side record Buyer’s reconciliation action
Quote selection Selected quotation or offer Seller’s quote/offer reference Confirm which quote version the PO uses
Purchase request PO with requested items and references Seller receives or records the request Confirm PO number, item scope and supporting documents
Seller record Buyer may receive an SO or acknowledgment SO or equivalent internal order record Check copied fields and note exceptions
Clarification Revised PO or written buyer confirmation, if used Updated SO or written seller confirmation, if used Make the approved change traceable on both sides
Fulfillment Buyer tracks approved order basis Seller manages fulfillment under its process Keep production, inspection and shipment evidence tied to the approved configuration
Payment/documentation Buyer processes agreed payment documents Seller issues relevant invoice or records Reconcile invoices and receipt records separately

The precise sequence depends on the parties’ system and commercial arrangement. Some buyers issue a PO after quote approval; others require internal authorization first. Some suppliers issue a formal SO; others use an order acknowledgment or email. The names may differ while the business need remains the same: a shared, recorded understanding of the product scope and open exceptions.

The comparison should therefore capture more than document names. Identify who prepared each record, its reference number, the source document it uses, its issue date or version, and any differences that require action. If a seller document uses the buyer’s PO number but has an additional internal number, record both without replacing one with the other.

Which fields should buyers reconcile between the PO and SO?

Start with fields that define what will be supplied and where it is expected to go. A line-by-line comparison is especially useful when the goods are customized or the quotation contains assumptions. The buyer’s procurement team can use a review table and assign a responsible owner to any technical or commercial exception.

Check these fields as relevant to the order:

  • Item identity: part number, product description, style, model, size, material or finish code.
  • Quantity and unit: number of products, sets, components or cartons; unit-of-measure basis.
  • Pricing: currency, per-unit or total basis, included service or packaging scope, and any referenced quote.
  • Technical references: drawing number and revision, approved sample, BOM or specification attachment.
  • Customization: logo, label, color, finish, accessories, fasteners, or other approved configuration fields.
  • Delivery information: ship-to or delivery point, requested date, delivery window and whether dates are estimated or confirmed.
  • Conditionnement : export packaging, retail packaging, marks or instructions if included in the quotation.
  • Payment and commercial terms: match to the agreed quotation or contract documents without inferring terms from a PO/SO template alone.
  • Exceptions: any substitution, partial quantity, revised date, exclusion or assumption.
  • Traçabilité : buyer PO number, supplier SO or acknowledgment number, and the document versions each record references.

The fields shown may be split across documents. For example, the seller’s order record may contain a shortened product description while the controlled drawing defines the detailed geometry. The important check is whether the records clearly point to the same specification, not whether every field is duplicated word for word. If a reference cannot be traced, ask for the controlling attachment or a written clarification.

Pay special attention to unit basis. A buyer may order pieces while a seller quote prices sets, or a product may be listed per unit while packaging is described per carton. A numerical quantity that looks consistent can still mean different things if the unit differs. Ask the seller to state the unit and package basis explicitly. This article does not define a universal field list or required PO form; the buyer’s own purchasing controls and the parties’ agreement determine what is needed.

Generic purchase order and sales order compared during a hardware sourcing review
Compare the buyer request and seller record before resolving any changed order field.

What should a buyer do when the PO and SO do not match?

Treat the difference as an open item until an authorized party resolves it. First identify the exact field and source record that conflict. Then determine whether the difference reflects a proposed change, a transcription error, a different interpretation, or a document version that should no longer be used. Do not guess which side is correct based on which file is newer or more visually complete.

A practical resolution workflow is:

  1. Record both document references and revisions.
  2. Mark the specific field that differs, such as finish, unit, quantity, date, destination or drawing revision.
  3. Identify the person authorized to decide that field: buyer procurement, product engineering, seller order contact, or another named owner.
  4. Ask the other party to confirm the intended value and explain any proposed change.
  5. Update or supplement the relevant controlled record using the company’s normal procedure.
  6. Confirm that the revised record and attachments refer to the same configuration.
  7. Tell relevant teams which version controls and retain the clarification with the order record.

If a finish code changes, engineering or product ownership may need to confirm that the substitute matches the intended appearance and product specification. If quantity or unit changes, procurement should check commercial implications. If a date changes, the buyer should determine whether the revised expectation is acceptable. The responsible party depends on the organization; do not treat every discrepancy as purely administrative.

A verbal discussion may help resolve an issue quickly, but the agreed result should be written into the record that controls the order. Keep the correction traceable rather than overwriting the only copy or leaving the change buried in a chat. This supports handoff across purchasing, product, quality, production planning and receiving teams without implying a specific enterprise software workflow.

Do not issue a duplicate PO just because the seller’s SO has a different reference or an error. First establish whether the original order already exists and which record needs correction. A duplicate may create two order records instead of resolving one discrepancy. The parties’ authorized process should determine whether a revision, cancellation, replacement or supplemental confirmation is appropriate.

How buyers can reconcile purchase order vs sales order records

Are a sales order, quotation, invoice, and purchase order interchangeable?

No. They may contain overlapping information, but their roles differ. A quotation or offer describes proposed commercial terms before the buyer makes a purchase request. A PO communicates the buyer’s requested scope. An SO may be a seller-side record of the requested or confirmed order. An invoice is a separate payment document. A receipt or goods-received record addresses what the buyer or warehouse received. The exact document flow varies, so buyers should not infer one record’s role from the presence of familiar fields.

A commercial invoice used in export documentation is also distinct from a PO or SO. Koitor’s separate guide to pro forma versus commercial invoices covers that document comparison. The article on invoice matching for hardware importers addresses invoice, order and receipt matching. These owner pages cover adjacent transaction stages; this article stays focused on buyer and seller order records.

Likewise, a sales order in a seller’s system should not automatically be confused with “sales order” as a forecast or demand-planning input. Koitor’s existing article about sales orders and forecast consumption addresses that internal planning question. The shared phrase does not make the subject the same as comparing the buyer’s PO with the seller’s SO.

How should OEM buyers connect order records to specifications?

Custom products make document references especially important. A short PO line may not describe all agreed characteristics of a bathroom shelf, wire basket, towel bar or storage organizer. The order can rely on a quotation, drawing, sample, finish schedule, packaging instruction, label proof, BOM, or other approved document. The buyer should identify which document controls each part of the requirement and make the reference visible in the order record.

For a private-label hardware project, reconcile brand artwork and packaging separately from the product’s technical revision. A seller’s order record may reference a packaging file while the product drawing has a different revision. Those can both be correct if the documents are explicitly identified and approved, but they should not be assumed to be one combined version. Confirm the actual product, artwork and packaging scope with their responsible owners.

When the supplier proposes a change, ask whether it affects the physical product, included accessories, packaging, quantity, price basis, delivery assumption, or required evidence. The change should be reviewed by whoever owns that decision. A buyer may accept a revised date but reject a material substitution; the SO should not be treated as a blanket approval of all differences. Record each decision with the specific field it covers.

For Koitor Hardware projects, buyers can share the current drawing or sample and the related quotation/order references through the Page consacrée à la fabrication sur mesure d'accessoires de salle de bains or the OEM home-storage hardware page. Koitor is a family-owned custom metal hardware factory; the exact scope, specifications and confirmed capability must be checked for each project. This does not imply legal, accounting, ERP or contract-administration services.

What mistakes should importers avoid?

  • Assuming the SO automatically matches the PO. Compare each required field and reference.
  • Treating the seller’s record as proof of buyer approval. Resolve changes with the authorized buyer owner.
  • Using the document title to infer legal status. Do not make contract-law assumptions from “PO” or “SO.”
  • Confusing an SO with an invoice. Payment documents have a separate purpose and should be reconciled separately.
  • Ignoring units or packaging basis. Pieces, sets, cartons and price units can differ.
  • Leaving the drawing revision out. Custom product identity often depends on referenced technical files.
  • Accepting a changed finish or date by silence. Record an explicit resolution.
  • Replacing a reference without preserving traceability. Keep the buyer and seller document numbers linked.
  • Issuing a duplicate PO to fix an SO error. Check the existing order first and follow the authorized correction process.
  • Assuming every supplier uses the same workflow. Ask which record is the supplier’s confirmation and how exceptions are recorded.

These are avoidable reconciliation gaps, not claims that all supplier processes work the same way or that a particular organization has made these mistakes. The goal is a shared, traceable order scope.

Buyer checklist for confirming who issued each order record and its reference
Keep issuer, order reference and approved exceptions visible during handoff.

What checklist can buyers use before order release?

Use this checklist to compare documents and expose open questions. Mark each field as matched, not applicable, or awaiting confirmation.

  • [ ] Buyer PO number and seller SO/acknowledgment number are recorded.
  • [ ] Both records reference the same quotation and order revision.
  • [ ] Product identity and part numbers match.
  • [ ] Quantity and unit of measure match.
  • [ ] Price basis and included scope are clear.
  • [ ] Drawing, sample, BOM, finish and packaging references are current.
  • [ ] Ship-to location and requested/confirmed date fields are distinguished.
  • [ ] Seller-proposed deviations are listed explicitly.
  • [ ] Each deviation has an authorized decision owner and written resolution.
  • [ ] Invoice, receipt and export documents remain separate records with their own review.
  • [ ] The corrected documents are shared with teams that need the approved order basis.
  • [ ] No duplicate order is created before checking the existing order record.

Foire aux questions

Who issues a purchase order?

The buyer issues a purchase order to state the goods or services it is requesting from a supplier. Internal approval and document format vary by organization. The PO should point to the relevant quote, specifications and revisions for a customized order.

Who issues a sales order?

The seller commonly creates a sales order in response to or as a record of the buyer’s request. Some suppliers use another type of acknowledgment or confirmation. Ask which seller-side record represents the current order entry and how changes are documented.

Is a sales order the same as a purchase order?

No. They may refer to the same transaction but are prepared from different sides and serve different records or workflows. Compare their content and references rather than assuming the seller’s version is an exact copy of the buyer’s request.

Is a sales order an invoice?

No. A sales order is generally an order-management record; an invoice requests payment under the seller’s billing process. The buyer should reconcile invoices separately against the relevant order and receipt records according to its own controls.

Which document controls if the PO and SO differ?

Do not infer the answer from the document names alone. Identify the discrepancy and ask the authorized buyer and seller contacts to resolve it under their agreement and normal procedures. Record the result on the appropriate controlled documents.

Does an SO mean production has started?

Not necessarily. A seller-side order record does not by itself prove production status or release. Confirm the project’s actual authorization and status through the parties’ agreed communication and records.

Collaborez avec Koitor Hardware

For a custom bathroom or home-storage hardware order, share the current PO, supplier confirmation, quotation, drawing revision and any open discrepancy. Koitor Hardware can discuss the project scope against the available documents; the authorized buyer and seller contacts should record the agreed order basis before the next action.

Clarify a custom hardware order before it moves forward.

Discutez de votre projet
Review OEM Hardware Scope

Fabrication pour compte de tiers / Marque de distributeur

Transformez ce guide d'approvisionnement en cahier des charges

Indiquez-nous le produit souhaité, ses dimensions, sa finition, la quantité commandée et vos exigences en matière d'emballage. Votre équipe recevra une analyse pratique de la faisabilité de la fabrication avant l'établissement du devis.