Blog
First confirm that the source is a buyer-issued purchase order—often orden de compra or pedido de compra—rather than a supplier quotation, sales order, order confirmation, invoice, delivery note or packing list. Inventory the original order, every attachment and each later revision separately. Preserve the purchase-order number and date; buyer, supplier, bill-to and ship-to roles; internal and quotation references; currency; each line number, item identifier, description, quantity and unit; prices, allowances, taxes and printed totals; requested delivery details; payment and delivery wording; approvals and visible marks. Do not merge versions, recalculate amounts, convert units or currencies, import a value from a companion record, interpret commercial terms or decide which document controls. For an exact quote, securely upload every current page and the version chain.
Scope
Use this post when an already-selected Spanish-language purchase order needs an English translation for procurement, supplier onboarding, operations, accounts payable, audit or another business review. It covers classification, header and line-item structure, linked references, revisions and bilingual QA. It does not create or approve an order, decide contractual effect, audit procurement, verify prices or tax, reconcile an invoice or delivery, advise on trade rules, authenticate approvals or guarantee that a recipient will accept the translation.
Procurement and supplier teams exchanging an already-issued order across languages.
Operations, finance and audit reviewers who need every line and reference to stay traceable.
Translators handling dense order tables, annexes and revision chains.
Table of contents
Step-by-step explanation
Orden de compra commonly supports “purchase order,” but pedido may name a buyer order, seller-side sales order or a general order depending on the document. Check who issued it, who receives it, the order identifier, party labels, line table and response or approval blocks. A supplier quotation states proposed prices or terms before an order, an order confirmation or sales order comes from the supplier side, an invoice requests payment, and an albarán records delivery. Keep each as its own source.
Fictional example: buyer Loma Norte issues “OC-418” against quotation Q-91; supplier Mar Azul later sends “Confirmación CV-77.” Translate them as two linked documents, not one order.
Record the exact title, order number, issue date, page count, annexes, incorporated terms, revision label and status printed on every file. Keep the original order, amendment, replacement and cancellation separate and in sequence. Ask for a complete current set when a page or referenced schedule is missing.
Fictional example: “OC-418 Rev. 2” includes a two-page pricing annex; Rev. 1 remains a separate source in the manifest.Translate each role label in context—including comprador, proveedor, facturar a, enviar a, entregar en, solicitante, buyer contact and invoicee—and keep every party name and address attached to the corresponding role. One organization may occupy several roles, and the bill-to office may differ from the delivery site. Do not replace a role with a familiar but unsupported label.
Fictional example: Sierra Labs is the buyer, its shared-services unit is bill-to, and Planta Este is ship-to.Copy the purchase-order, quotation, requisition, contract, project, cost-centre, sales-order and supplier references character for character with their labels. Preserve prefixes and leading zeros. Flag a mismatch without substituting the identifier printed on another record.
Fictional example: “OC 00418 / Requisición R-090” stays separate from the supplier’s “Pedido V-804.”Keep line numbers, buyer and supplier item IDs, descriptions, variants, quantities, units, requested dates, delivery locations and notes in their source rows. Distinguish a blank, dash and zero. Do not merge repeated descriptions, convert a unit or infer a back-ordered quantity.
Fictional example: line 20 orders 15 kg while line 30 orders 12 units; both numbers and units remain exactly associated.Retain currency, unit price, price basis, discount or charge, tax labels, line extension, subtotal, rounding and payable total exactly as displayed. Preserve decimal punctuation as a source value or apply only the approved presentation convention without changing value. If a manual check reveals an apparent discrepancy, keep the printed values and flag it; never replace them with recalculated figures, convert currency or certify arithmetic.
Fictional example: a printed “1.250,00 EUR” subtotal is not replaced by a sum derived from the translated rows.Translate delivery, payment, validity, warranty, inspection, cancellation and incorporated-term wording in its clause or field context. Preserve cross-references and visible approval or signature labels. Do not advise what a term means legally, whether it was accepted, or whether an approver had authority.
Fictional example: “Entrega parcial sujeta a autorización escrita” is translated as written, without deciding whether an email qualifies.Compare titles, parties, identifiers, every line, digits, units, currencies, dates, terms, totals, revisions and marks with their exact source locations. Flag differences instead of repairing them. Put only generic scope facts in ordinary quote text and use secure upload for complete files and annexes.
Fictional example: a four-page order with 36 lines, two annexes and one revision is quoted after the whole version chain is reviewed.Decision table
Issuer, recipient, order number and buyer-side function.
Whether it is a sales order, offer or order response.
Printed role labels; do not infer payer or owner.
Prefixes, leading zeros, variants and line number.
Do not recalculate or certify arithmetic.
Original, revision sequence and referenced order.
Complete pagination, references and current version.
Current written instruction and delivery format.
Checklist
The source is a buyer-issued purchase order, not a quotation, sales order, invoice or delivery note.
Every page, reverse, attachment, incorporated term and revision is inventoried.
Buyer, supplier, bill-to, ship-to, requester and contact roles remain distinct.
Order, quotation, requisition, contract, project and supplier references retain every character.
Line numbers, item IDs, descriptions, quantities, units, dates and locations match the source.
Currency, prices, allowances, charges, tax labels and printed totals stay in their relationships.
Delivery, payment, validity and other terms preserve hierarchy and cross-references.
Approvals, signatures, stamps and handwritten notes are represented without authentication.
Revisions remain separate and discrepancies are flagged, never silently consolidated.
Ordinary quote text excludes private source data; complete files use secure upload.
Official and reviewed sources
The current model treats the purchase order as a document distinct from the commercial invoice and packing list. Its linked example separates number and date, buyer, seller, invoicee, delivery location, payment data, allowance or charge, total and ordered-item identifiers, descriptions, quantities, unit prices and line totals. It is a model, not a rule that every order contains every field.
United Nations Economic Commission for Europe
Open the reviewed sourceThe guide distinguishes sender and receiver, original and copy status, add, full-refresh change and delete actions, last-update time, unique order identification, buyer, seller, bill-to and ship-to roles, order lines and quantities. It supports traceable versions and roles, not a decision about which supplied version governs.
GS1
Open the reviewed sourceThe current Spanish documentation uses pedido de compra and orden de compra, separates header data from order lines, and shows supplier, delivery place and date, requester, item or service, quantity, unit, price, discount, net amount and totals. It illustrates one system, not universal field or terminology requirements.
Microsoft Learn
Open the reviewed sourceThe current service page describes quote scoping by document type and volume together with terminology, formatting, confidentiality and deadline needs.
SpanishToEnglishTranslations.com
Open the reviewed sourceThe current quality page describes scope review before work starts, translator fit by document category and correction handling.
SpanishToEnglishTranslations.com
Open the reviewed sourceThe current security page describes private intake, non-public storage URLs, private object identifiers, role-based access, retention and incident practices.
SpanishToEnglishTranslations.com
Open the reviewed sourceAbout this guide
Authority instructions can change or vary by form and case. Use the linked primary sources and your current filing instructions.
Blog FAQ
“Purchase order” is usually the direct functional title when a buyer issues the record to a supplier, but classification still depends on the complete document. Pedido can be broader. Confirm issuer, direction, party labels, identifier and line table before choosing a title.
No. The buyer issues a purchase order; a supplier may issue a quotation before it, a sales order or confirmation in response, and an invoice for billing. They may repeat references and values, but each remains a distinct source and should be translated as printed.
Translate the field labels and copy each identifier exactly under the correct heading. Preserve prefixes, leading zeros and variants. Do not replace the buyer code with the supplier code or merge them because they describe the same item.
No. Preserve printed quantities, units, prices, currencies, discounts, tax labels and totals, then flag an apparent difference. Only an authorized party can provide a corrected or replacement order. Translation does not audit or certify the arithmetic.
Inventory every supplied version, preserve its identifier, date, sequence, status and source-order reference, and keep changed or deleted lines traceable. Do not silently build a consolidated order. Ask the customer which complete version set is in translation scope.
That depends on the recipient’s current written instruction. Treat the English translation, signed certification statement and delivery format as separate choices. Certification describes the translation; it does not authenticate approvals, validate the transaction or guarantee acceptance.
In ordinary fields, share only the generic type, country or Spanish variant, approximate pages and lines, annex and revision counts, scan quality, recipient category, deadline, delivery format and certification preference. Keep names, addresses, identifiers, products, prices, terms and images out of free text. Securely upload every page, reverse, annex and version for exact review.