ASHUR International

Before You Send an Oilfield RFQ in Iraq

Define the evidence, delivery and acceptance requirements.

Two quotations can carry the same item description and still price different obligations. One supplier may include inspection records and delivery to a named handover point. Another may quote the equipment alone. The difference needs to be visible before price decides the conversation.

ASHUR International · Procurement & Trading

ASHUR International · Published 22 November 2026 · Research reviewed 22 November 2026

A technician measuring an unbranded industrial gate valve in a workshop.
AI illustration. This is not an ASHUR project photograph, a stock statement or evidence of a completed supply.

Start with the same requirement

Use one controlled RFQ version for every supplier. Give each requirement an identifier and record the specification, revision, quantity and unit. Add the application, operating conditions and required interfaces where they affect selection. A description such as ‘industrial valve’ is rarely enough to compare material, size, pressure rating, connection or performance.

Ask suppliers to identify the exact offered item and to declare departures against the same requirement identifiers. Distribute subsequent amendments consistently. A comparison becomes unreliable when one offer follows an earlier specification and the difference disappears into a general ‘compliant’ statement.

Decide what evidence would answer the question

State the documents needed for the particular purchase, and when they are needed: with the quotation, before manufacture, before dispatch or at acceptance. Product data, manufacturer identity, test reports, inspection records and traceability details serve different purposes. Request the evidence relevant to the equipment and the buyer's requirements, rather than an indiscriminate certificate bundle.

Match product or lot evidence to the item under review. Match a quality-management certificate to the named organisation or site, stated scope and validity. A general company certificate does not itself establish the conformity of a particular valve, pump, cable or chemical.

If manufacturer appointment is claimed or required, review the authorisation's issuer, product line, territory and period. A logo in a catalogue is not sufficient. A product image can help identify an item but does not demonstrate stock, condition, origin or delivery availability.

Keep API requirements product-specific

API describes its Monogram programme as a voluntary licensing programme for manufacturers of products conforming to applicable API specifications. Its programme documents distinguish product specifications, licensing scope and management-system registration. Where the RFQ calls for an API specification or Monogram requirement, verify the specified product, edition and licence scope using the relevant programme documents and current directory record.

A distributor's offer is not the manufacturer's licence. A quality-system registration is not a substitute for required product evidence. The reference to an API standard does not create a universal certification requirement for every Iraq purchase. Record the requirement that actually applies to this product and contract.

Draw the delivery boundary before comparing prices

Name the delivery point and allocate the work on both sides of it. Clarify packing, transport, insurance where relevant, import arrangements, unloading and movement to the receiving location. If an Incoterm is used, identify the term, named place and edition; also check the rest of the contract for obligations that the term does not settle.

Ask who will provide origin and technical documents, who will act as importer, which appropriately authorised party will handle customs declarations, and who will accept the goods at site. Agree what evidence marks each handover. Avoid placing a responsibility into an unowned gap between supplier, freight provider and receiving team.

Use ASHUR's existing import-readiness and logistics guidance for the documentary and provider interfaces. This RFQ review supports requirement definition and comparison; it does not represent customs-broker or carrier authorisation.

Specify inspection and acceptance as separate decisions

If the buyer requires an inspection or test plan, identify the stages, records and approval responsibilities in the RFQ. Explain whether any witness or hold point applies. State the acceptance criteria and the party authorised to accept a deviation.

An inspection record, dispatch approval and delivery receipt answer different questions. Make the contract's required close-out documents visible, including manuals, test records or support commitments where applicable. Do not assume that arrival at the destination demonstrates technical acceptance or successful commissioning.

Use the comparison worksheet

Enter one supplier and one requirement per row. Repeat the same requirement identifier for each supplier so the offers can be filtered and compared. The workbook separates the supplier's answer from the evidence reference, declared deviation, delivery responsibility, reviewer, unresolved question and next action.

Use ‘Evidence reviewed’, ‘Clarification needed’, ‘Deviation for decision’ or ‘Not reviewed’ as the review status. ‘Evidence reviewed’ only records that a person examined the identified material. It does not automatically mean compliance, award or approval. Keep the decision in the next-action record and follow the buyer's actual approval process.

The fictional example shows why this matters. Supplier A offers delivery to a named warehouse but leaves unloading unallocated. Supplier B proposes a different destination. A unit-price comparison cannot resolve either gap. Both need a written answer before the delivery basis is comparable.

Make clarification questions answerable

A useful clarification points to the precise mismatch: ‘For requirement R-03, confirm who unloads at the named warehouse and whether the quoted price includes it.’ It should also identify the response needed and the person who will review it. ‘Please confirm full compliance’ leaves too much room for different interpretations.

Record a departure plainly. Do not silently turn an exception into compliance or assume an attractive price compensates for it. Where the buyer's procurement procedure prescribes equal-treatment, pass/fail or weighted criteria, use those rules. This worksheet deliberately does not invent a qualification score.

Carry the decision into the order

Before selection, reconcile the price basis, currency, validity, lead time, payment terms, warranty and exclusions against the same agreed scope. Retain the RFQ revision, supplier response, clarification record, technical disposition and approved commercial decision.

The selected quotation should not lose its open questions when it becomes an order. Transfer the agreed responsibilities and documents into the contract and delivery follow-up. An indicative offer remains an offer until the relevant commitments are made.

Prepare an Iraq procurement discussion

A useful initial brief contains the specification or bill of quantities, application, quantity and unit, destination, timing, required evidence and acceptance criteria. ASHUR can help define the enquiry, compare supplier responses and coordinate documentary and delivery responsibilities within an agreed scope.

Availability, manufacturer relationships and delivery commitments require written confirmation for the actual proposal. Send a non-confidential requirement summary through the existing Contact page or to [email protected].

Related guidance

Buyer-side procurement guidance. The RFQ, contract, relevant technical standards and applicable procurement rules determine the requirements. The worksheet does not certify a supplier or product, establish inventory or constitute an award.

Sources and review

Published 22 November 2026 · research reviewed 22 November 2026. No named legal reviewer or professional sign-off is asserted.