How to request a quote: MOQ, lead time and certification scope

How to request a quote for hazardous-area devices: what to send, what to ask about MOQ, lead time and certification scope, and what a good answer looks like.

What to send in the first message

A quote request that gets a useful answer contains five things: the device type or model, the quantity, the operating environment, the target market, and the job the device must do. "Intrinsically safe tablet, 40 units, chemical plant, target market Germany, inspection checklists" can be answered; "intrinsically safe devices, price please" cannot, because price, availability and scope all depend on the configuration and the market. The contact form on this site asks for device type, company, and site requirements and quantity precisely so the first message carries those five things.

MOQ and lead time: ask, do not assume

No MOQ figure and no lead-time figure is published on this site, because none is published for these models. Confirm MOQ and lead time in your quote request, and ask what moves them: order size, configuration options, accessory bundles and market-specific preparation can all change both. A lead time quoted for a standard configuration may not hold for a no-camera variant or a particular battery tier, so name the configuration when you ask. If timing is critical — a shutdown window, a project start — say so in the first message, not after the quote arrives.

Certification scope: the question that decides deployment

Confirm certification scope and marking for your target market before ordering. That single question contains four sub-questions: which marking applies to the configuration you are ordering, which markets that marking covers, which site classification it supports, and what documents the supplier provides with the shipment. Certificates available upon request — ask for them for the named configuration and the named market, and check that the documents match the devices delivered. A certificate for a different configuration or a different market does not answer the question.

What a good answer looks like

A good supplier answer names the configuration, the quantity, the price basis, the lead time, the marking and scope for your market, the warranty scope and the availability for your site — each tied to the model you named. An answer that repeats category language without those specifics has not answered the request, whatever its tone. Keep the exchange in writing, and treat the written answers as part of the order record. If any answer contradicts a figure on a model page, ask which one governs before ordering.

What to put in the quote request

Confirm MOQ and lead time in your quote request. Confirm certification scope and marking for your target market before ordering. Confirm the model availability for your site before ordering. Certificates available upon request. Related reading: before-you-order checklist, how to order, contact page, frequently asked questions.

A template first message

Below is a template first message that carries the five things a useful answer needs. Adapt the bracketed parts and send it through the contact form: "We need [device type or model] for [job] at [site type] in [target market]. Quantity: [number]. Operating environment: [brief description, including site classification if known]. Questions: (1) price for this configuration including accessories and spares; (2) MOQ and lead time; (3) certification scope and marking for our target market, with documents for this configuration; (4) availability for our site; (5) warranty scope including duration, coverage and exclusions; (6) [any model-specific question, for example operating system, battery tier or no-camera availability]." A message in that form can be answered in one round. A message without those parts will take three rounds to reach the same place, and the answers may still not be comparable across suppliers.

Following up without losing the thread

Follow-up discipline matters as much as the first message. Keep one thread per supplier and per configuration, so answers stay attached to the questions that prompted them. When an answer changes — a lead time slips, a configuration is substituted, a price basis moves — ask for the change in writing, with the same specificity as the original answer, and confirm that the changed answer still matches the site's requirements before accepting it. When comparing suppliers, compare answers to identical questions, not brochure language: a supplier that answers all six template questions specifically has given you an orderable quote, while a supplier that answers two of them has given you a conversation. The order should go to the quotable answer, not the friendliest tone.

After the quote arrives

Before ordering, run three checks on the quote itself. First, configuration check: does every line item match the model and options you asked about, with no silent substitution? Second, document check: do the certification documents supplied match the named configuration and the named market? Third, completeness check: are price, MOQ, lead time, marking and scope, availability and warranty all present, each tied to the configuration? Any missing item goes back as a question before the order, not as a dispute after delivery. That discipline is the whole point of the checklist method: the order record should contain every commitment the deployment depends on, before the devices ship.

Comparing two quotes line by line

Two quotes for the "same" devices can differ in every line that matters. One may price the standard configuration while the other prices the no-camera variant; one may quote a lead time for a small order while the other covers the full quantity; one may include warranty and spares while the other excludes them; one may name a marking and scope for your market while the other repeats category language. A line-by-line comparison catches those differences: configuration, quantity, price basis, lead time, marking and scope, availability, warranty, accessories and spares, training and support — each line compared across quotes, each gap sent back as a question. The comparison takes an hour and routinely changes the decision, because the cheapest headline quote is often the one with the most missing lines. Order against the quote whose lines are all present and all specific, not the quote whose headline is lowest.

Keep the thread after delivery

The quote thread should stay open after delivery, because the questions it contains recur: spares orders, configuration changes, warranty claims, software updates and the next site's rollout all refer back to the original answers. Keep the thread, the quote, the order and the delivery documents together in one file per supplier, and add each later exchange to the same file. When a new question arises — a battery tier for a reorder, a document for a new site's acceptance — the file gives the answer's history without a fresh round of archaeology. Suppliers notice when a buyer keeps that kind of file, and their answers get more specific, because they know the record will be checked.