Skip to main content
Apollo NZ Global

Built Intelligence · Architecture & Specification · Architecture & specification

Buying Building Products Wholesale: What Developers Should Include in an RFQ

A good request for quotation can save far more time than it takes to prepare. When developers send suppliers only a product photograph, an approximate quantity and the words 'best price', they invite replies that are difficult to compare. One may include packaging, another may exclude freight, and a third may assume an entirely different material specification.

Apollo NZ Global EditorialPublished 2026-11-19Project intelligence
Final product selection, technical documentation and local approval requirements are assessed for each project.
Apollo developer page architectural facade construction project image

Existing Apollo developers page architectural reference; illustrates specification and sourcing context.

01

Project context

For wholesale building products, the RFQ should be a controlled description of what the project needs and what the supplier is expected to deliver. It also needs to make clear where product supply ends and local professional work begins. That distinction is central to Apollo NZ Global's supply-only business model.

02

State the project and buyer use case

Open with the project type, general location, intended end use, programme and purchasing entity. A 20-unit townhouse project, a school sports upgrade and an international resort need different product, documentation and logistics arrangements. Provide enough context for suppliers to identify unsuitable products before pricing.

Indicate whether the enquiry is for one prototype, a recurring unit type, a single bulk order or staged releases. Avoid presenting forecast quantities as firm commitments unless the buying programme supports that. A staged project may need unit-by-unit schedules and revision control.

03

Supply drawings that establish dimensions

An RFQ should include dimensioned plans, elevations or marked-up photographs suitable to the product category. Provide tolerances or indicate which dimensions remain subject to site verification. For large roofs and structures, include intended support positions, clearances and interface information instead of relying on nominal catalogue dimensions.

Where details are missing, name the person or discipline responsible for confirming them. A supplier may offer a preliminary budget against assumptions, but no one should mistake that budget for a final fabrication release.

04

Identify the exact product function

Ask for outcomes, not just labels. 'Outdoor pergola' could mean a manually adjustable louvre kit, powered roof, retractable shade canopy or fixed insulated roof. 'Sports flooring' may refer to modular tile, roll material or specialist indoor surfaces. The functions, environments and included components differ.

List operational requirements, expected users, environment, finish and maintenance needs. If alternatives are permitted, ask each bidder to make substitutions explicit and provide evidence showing how the proposed product meets the required function.

Apollo architects and specifiers hero showing architectural procurement context
Existing Apollo architects and specifiers website hero. Not a photographed RFQ meeting or supplier commitment.
05

Separate mandatory evidence from preference

For safety-critical or regulated products, request applicable manufacturer data, test reports, approvals, drawings and project-specific professional design responsibilities. Ask where a claimed standard or certification actually applies: to the full system, one component, a previous model or a different installation context.

Do not treat a generic brochure claim as a local approval. Make a list of required evidence at quotation, order confirmation and prior-to-installation stages. Some documents can legitimately be produced only after final configuration, but that timing needs agreement.

06

Specify environmental conditions

Products destined for coastal, high-wind, tropical or high-use public environments should be assessed against those conditions. Record site location, known wind or seismic design requirements, likely salt or moisture exposure, operating temperatures and unusual maintenance constraints where relevant.

Be clear where the local designer will establish the formal design inputs. Suppliers should not invent a wind zone, corrosion category or ground bearing capacity from a broad regional description. Require the bidder to state assumptions and identify where its offering may not be suitable.

07

Ask for a schedule of inclusions and exclusions

Require a line-by-line schedule of supplied components and options. For a roof system, identify frames, posts, blades, gutters, downpipes, controls and fixings as applicable. For a sports system, identify surface units, edges, adhesive if relevant, nets and accessories. Each product family will have its own complete list.

Separately list omitted work such as foundations, building consent, local engineering, installation, cranes, electrical connections, site drainage and disposal. The buyer should be able to calculate the full project cost without guessing what is inside the manufacturer's carton.

08

Make quantity and variation control practical

Create an item schedule with unique line numbers, product type, size, finish, quantity, location, project phase and drawing revision. For developers, map each item to its unit or construction zone. This reduces confusion when changes arise after the first quotation.

Confirm who authorises substitutions, colour changes or production releases. A small variation in opening size or coating can affect lead time and batch compatibility. Changes should be tracked formally rather than buried in an email thread without an updated schedule.

09

Give freight and receiving a separate section

State destination country, delivery city or depot, preferred Incoterms where relevant, port or customs assumptions, receiving arrangements, access restrictions and packaging requirements. Heavy steel systems and bulky modular products have different handling needs from small boxed accessories.

Ask for package dimensions, weights where available, delivery lead time, transport exclusions and required unloading equipment. If goods are staged, ask which items arrive in each shipment. A low unit price may not produce the lowest landed cost.

10

Compare whole-project cost, not only product price

Prepare a comparison sheet with identical fields for product cost, freight, GST or relevant taxes, supplier options, exclusions, evidence, warranty, lead time and local works. Separate known prices from provisional allowances. Unverified assumptions should remain visible and not be converted silently into facts.

Quality and risk matter as well as price. A technically documented system may be the better choice if it reduces later design changes or downtime. But that conclusion should follow the actual requirements, not a preference for a more expensive brand.

11

Use an RFQ release checklist

Before sending, verify that the product function, quantity schedule, drawing revisions, environmental assumptions, delivery destination, required evidence, local interfaces and response date are all included. Invite bidders to identify critical missing details rather than to guess.

When requesting Apollo supply, make the wholesale, supply-only basis explicit in the tender return. A good response should clarify the exact package and create a straightforward path to the remaining local engineering, approvals and installation tasks.

12

Frequently asked questions

What is the biggest cause of incomparable quotes? Different assumptions about included products, freight, documentation, delivery and local works.

Should an RFQ ask for the lowest price? It should request a comparable, technically suitable proposal with clear optional alternatives and exclusions.

Can I request supply before final design? A preliminary budget may be possible, but final product release requires verified configuration and interface details.

What is the minimum information for Apollo? Product category, location, quantities, intended use, dimensions where possible, environmental conditions, timing and desired delivery method.

13

Include a product ownership and substitutions register

A large project can have dozens of materials packages, and a vague supplier response can blur who is responsible for particular design details. Use an ownership register to show the nominated product category, approved design reference, supplier responsibility, professional designer, local installer and acceptance authority. If a substitution is offered, require the supplier to identify exactly what changes and supply corresponding evidence. The architect or engineer may need to review dimensions, loads, finish or performance before accepting the alternative. Do not treat a 'similar' product photograph as equivalence. A formal substitution process protects design consistency across repeated units and prevents cost savings from being achieved by silently reducing scope.

14

Request samples and technical evidence at the right stage

Material samples can help designers confirm visual finishes and interface details, but their colour or appearance is not proof of mechanical performance. Ask for the product's actual datasheets and relevant manufacturer documentation, including which model or manufacturing batch the evidence covers. For critical components, identify whether further test or compliance documentation is needed before release. Set milestones for receiving the documents rather than making every tenderer compile unnecessary paperwork at the initial budget stage. A structured evidence schedule can speed procurement because suppliers know what matters and when it must be produced. Be wary of unverified screenshots presented as official certificates or local approvals.

15

Use alternates without losing comparison quality

Allow bidders to propose an alternative that could reduce cost, delivery time or maintenance burden, but insist that it be priced separately from the requested base specification. The alternative should list changes in dimensions, operation, substrate, finish, documentation, warranty and installation requirements. This protects the buyer from comparing a fully documented roof assembly with a bare frame while assuming they are equivalent. For repeated product families, a substitution may affect dozens of interfaces and must therefore be reviewed as a coordinated change. Maintain one clear baseline for tender evaluation. Any accepted alternate should produce an updated drawing and schedule before the purchase order is placed.

16

Clarify international sourcing and Incoterms

International product sourcing requires precise language about who pays and arranges export clearance, freight, insurance, destination taxes, import clearance and inland delivery. Where Incoterms are used, reference the agreed term, named place and applicable edition; do not rely on a casual phrase such as 'delivered to NZ' without defining what that includes. Request packaging and weight information appropriate to the product, particularly for large steel frames or fragile glazing. Confirm likely customs and compliance checks with the relevant specialists before ordering. A supply quote that omits destination costs may still be useful, but it should be labelled as such. Commercial buyers need comparable landed-cost assumptions to make a defensible decision.

17

Keep the installation method outside the supplier's assumptions

A wholesale supplier can provide product instructions, packaging and relevant manufacturer data without assuming responsibility for a local site's foundations, cranes, access, electrical work or approvals. The project team should specify who designs those interfaces and confirms that the supplied item is fit for the intended location. An RFQ should ask for exact installer information requirements as well as product data. Where an installation contractor proposes modifications, the relevant product designer must confirm whether those changes are permitted. This separation reduces the risk of a supplier's indicative product price being used as a complete construction estimate. It also supports better decisions when several trades share the same roof or enclosure.

18

Record acceptance and defects procedures before dispatch

A good RFQ can state the documentation expected before shipment, how the buyer checks quantities and visible condition on receipt, and how defects or missing components are reported. Ask the supplier to identify packaging labels, component list, spare parts and the process for investigating discrepancies. For staged deliveries, each shipment should relate to an approved release schedule, reducing the risk of parts being mixed between different buildings. International delivery can make rework expensive, so early clarity is valuable. Acceptance procedures should remain commercially fair and consistent with the contract; they should not promise outcomes beyond the supplier's actual warranty or delivery responsibilities.

19

A practical tender evaluation scorecard

Use a weighted scorecard if the buying organisation needs formal procurement discipline. Categories can include technical fit, complete scope, evidence quality, lead time, freight certainty, maintenance support, warranty terms and total evaluated cost. Set weights from the project's real priorities rather than using a generic template. For a remote island facility, logistics and local repairability may matter more than decorative finishes. For a heritage-sensitive urban development, visual compatibility and approved interfaces may be critical. Mark any missing information for clarification before scoring. Avoid inferring product quality from a low number of documents when the documents have not been requested consistently from all bidders.

20

Close the loop after award

The procurement process should not end when an order is placed. Set milestones for approved shop drawings where required, final finish confirmation, production sign-off, packing list, freight booking and local receiving. Maintain one contact and revision trail for each package. At handover, collect the actual product identifiers, maintenance guidance, service contacts and warranties that apply to the goods supplied. These records help the developer resolve variations, assist facility managers and inform the next project. A well-organised first RFQ can become a reusable procurement framework for future Apollo wholesale orders without locking the buyer into unsuitable standard products.

Move from intelligence to project

Apply the thinking to the actual brief.

Open Developer Procurement Send a project brief
Project