Buying checklist: questions to ask before ordering hazardous-area devices

Why a checklist beats a brochure

Hazardous-area devices are bought on specifics, not on brochures. A brochure tells you a device class; an order needs a configuration, a quantity, a delivery date, a marking and scope for a named market, and a warranty arrangement. When any of those specifics is missing from a supplier's published pages, the buyer must supply it as a question. This post turns every missing figure on this site into a question you can copy into your inquiry.

The questions

Price: confirm the price for the configuration you need, including accessories and spares, because no price is published on this site. Quantity and timing: confirm MOQ and lead time in your quote request. Suitability: confirm certification scope and marking for your target market before ordering, and confirm the applicable hazardous-area classification for your site before ordering. Availability: confirm the model availability for your site before ordering, including whether a no-camera configuration is available where your site restricts cameras. Configuration: confirm the operating system configuration before ordering where the model page leaves it unstated, and confirm which battery tier applies where a listing gives a range of tiers. Support: confirm warranty scope in your quote request, including duration, coverage and exclusions, and confirm deployment support such as training and update provision.

Why the questions are written as buyer actions

Every item on the checklist is written as something the buyer confirms, not something the supplier promises in advance. That wording is deliberate. The published sources for these models do not support range-wide promises on price, lead time, warranty or certification, so this site does not make them. A supplier answer to each question, given for a named configuration and a named market, becomes part of the order record — which is exactly where such commitments belong. A promise made in general terms, for an unnamed configuration, is worth less than a specific answer to a specific question.

Common traps the checklist prevents

The first trap is carrying a parameter from one model to another: a battery figure, a screen size or a camera set that belongs to one model is read as a property of the range. The second trap is reading a category name as a suitability claim: a device sold for hazardous areas in general may still be wrong for a particular zone or market. The third trap is assuming an unspecified option exists: a no-camera variant, a particular system or a particular battery tier may or may not be offered for the model you want. The checklist blocks all three by forcing each point into a named question with a named answer.

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.

Turning answers into an order record

Questions are only half the method; the other half is what happens to the answers. Each supplier answer should be recorded against the question that prompted it, for the named configuration and the named market, and attached to the order. That record is what protects both sides later: the buyer can show what was confirmed, the supplier can show what was promised, and a dispute about scope becomes a document comparison instead of a memory contest. Keep the record in writing from the first inquiry, not reconstructed after delivery. Where an answer changes — a lead time slips, a configuration is substituted — record the change the same way, with the same specificity, and confirm that the changed answer still matches the site's requirements before accepting it.

Red flags in supplier answers

Several answer patterns should slow a buyer down. A price quoted without naming the configuration it covers will not survive a configuration change. A lead time quoted without naming the order size and market preparation behind it will not survive either. A certification answer that names no marking, market or classification has not answered the question. A warranty answer that names no duration, coverage or exclusions is not a warranty. And a specification answer that borrows a parameter from a neighbouring model — a battery figure, a screen size, a camera set — should be sent back with the model name attached. None of these patterns proves a supplier is unreliable; all of them prove the inquiry needs another round before an order is placed with confidence.

Negotiating from the checklist

A checklist is also a negotiating tool. When two suppliers answer the same questions, their answers can be compared line by line: price for the same configuration, lead time for the same quantity, marking and scope for the same market, warranty for the same duration. Differences that looked invisible in brochure language become visible in the comparison — one supplier's lead time assumes a standard configuration while the other's covers the no-camera variant, or one supplier's warranty covers repair while the other's covers replacement. Those differences are worth money and schedule, and they only surface when the questions are identical. Keep the question set fixed across suppliers, record answers against the same template, and negotiate on the lines where answers differ rather than on headline price alone. A supplier that answers every question specifically has already done part of the negotiation for you, because its quote can be ordered against without further rounds.

Keep the checklist alive after ordering

The checklist's job does not end at the order. Delivery brings a second round of checks: does the delivered configuration match the quoted configuration, do the documents match the named market, does the warranty start on the agreed date, and do spares and accessories arrive with the devices or separately? Each delivery check maps to a checklist question asked earlier, which is why the checklist should be kept with the order file and reused at goods-in. A mismatch found at delivery is cheap to correct; the same mismatch found on the first live round is a deployment delay. Treat the checklist as a living document through delivery, acceptance and the first month of operation, and close each item only when its evidence — a document, a test, a confirmed date — is on file.

One last use for the checklist: onboarding new buyers. A new procurement hire who inherits the checklist inherits the organisation's buying knowledge — which questions matter, which answers are acceptable, which gaps have bitten before. Without it, each new buyer relearns the same lessons by making the same mistakes, and suppliers learn to expect less rigorous inquiries from the new face. File the checklist where new buyers find it on day one, and review it whenever a deployment teaches a new lesson, so the document improves with every order instead of freezing at the first version.