100+ LoRa Mesh Device RFQ: Requirements Procurement Should Include

Prepared by the ChatField Editorial Team. Evidence reviewed August 18, 2026.

A request for quotation for 100 or more LoRa mesh devices should produce comparable commercial and technical answers. A one-line request for the best unit price does not tell the supplier which field workflow, regional configuration, phones, accessories, evidence, packaging or delivery responsibility the buyer expects.

A strong RFQ reduces quotation changes and prevents a low headline price from hiding an incomplete operating kit.

Short answer

Describe the users, route, supported message types, destination market, quantity, spares, phones, software, documentation, acceptance test, customization, shipping destination and commercial terms. Require the supplier to identify every assumption, exclusion and quote validity period.

ChatField's current B2B discussion begins at a minimum order quantity of 100 units. Final price, lead time, payment, Incoterm, accessories and delivery remain quotation-specific.

Start with the field problem

State who needs to communicate, where cellular coverage is unreliable, which routes matter and which outcome the organization wants to improve. Identify routine PTT, text, image or location workflows separately from alarms and emergency communication.

Give the supplier a site map or representative route without exposing sensitive locations unnecessarily. Mark buildings, terrain, vehicles, vegetation, gates, weak-coverage zones and safe test checkpoints.

The ChatField off-grid communication overview helps define the bounded local-team use case.

Specify the complete system path

For current J25 use, the smartphone is the interface. Bluetooth connects the phone to the carried J25 terminal, and the configured terminal carries supported traffic through the local LoRa mesh to another equipped terminal and paired phone.

The RFQ should list acceptable phone operating systems and models, application build, permissions, account or group setup, firmware and regional hardware. The phone alone does not transmit LoRa, and the terminal is not held like a conventional walkie-talkie.

Use the ChatField How It Works page to draw the bill-of-system path.

Define quantity by role

List active users, supervisors, participating relay roles, training units, replacement stock, repair turnaround coverage and growth allowance. Do not request 100 devices simply because 100 people appear on a roster.

Separate required production units from samples, pilot units and spares. Identify whether every shift shares hardware or receives assigned units, and whether phones are buyer-supplied.

Ask the supplier to show the proposed quantity calculation rather than only extending unit price.

State the destination and radio configuration

List every destination country and intended operating region. Ask for the exact hardware variant, frequency configuration, model identifier, compliance evidence and restrictions applicable to each destination.

Current public J25 evidence includes FCC ID `2BVP9-J25`. An FCC grant is model- and configuration-specific; it is not a universal approval for every destination, private-label change or future product.

Review the J25 specifications and evidence page and request the actual controlled documents.

Write route acceptance criteria

Define direct-path checkpoints first. Current J25 evidence includes 5 km in urban-obstructed testing and up to 10 km in ideal open terrain, but neither number guarantees a buyer's route.

For current planning, evaluate no more than two participating relay nodes where the tested layout and configuration permit. Record stable, marginal and failed results in both directions rather than multiplying distance figures.

Require the quote to identify what field support, fixtures or personnel are included in acceptance.

Define message and capacity tests

List the supported workflows the buyer will test: PTT setup and intelligibility, text delivery, image transfer, location update, acknowledgement and group membership. Define peak users, message mix, acceptable delay, retries and exception behavior.

A nearby two-user demonstration does not prove a 100-device deployment. Ask for a staged test that covers representative users, shifts, traffic and route conditions.

The ChatField technology page explains the architecture without promising unlimited capacity.

Request security and lifecycle information

NIST recommends that IoT buyers define required device and manufacturer capabilities, including identification, configuration, data protection, interface access, updates, status awareness, documentation and support.

Ask who can configure groups, how access is removed, how software is updated, which versions are supported, what customer data is collected, which external services are involved and what happens at end of support. Put required answers in the RFQ schedule.

Do not accept secure, encrypted or enterprise-ready without a defined scope and evidence.

Itemize the physical kit

Request exact quantities for terminals, cables, attachment hardware, cases, chargers or approved power accessories, labels, printed materials, cartons, spares and any test fixtures. State clearly whether smartphones are included.

Define connector, input-power and packaging expectations without assuming an accessory shown in a photograph is included. Ask for packed dimensions, weight and battery configuration for logistics planning.

The current J25 product page is a starting point, not the final quotation bill of materials.

Address lithium-battery transport

PHMSA explains that lithium-battery transport requirements depend on battery type, size, configuration and mode. Ask the supplier for battery specification, applicable test summary, package configuration, markings, documentation and shipping assumptions.

Do not assume that a single-unit sample route applies to a 100-unit shipment. Destination, carrier, air or vessel mode, batteries packed with equipment and replacement batteries can change the plan.

Assign the responsible shipper and compliance review in the quotation.

Separate standard product and customization

Create separate lines for standard J25, logo or label work, packaging, manuals, accessories, application branding, integration and custom system development. A branded carton is not the same project as changing radio behavior or building a customer-specific application.

Require scope, one-time engineering charges, minimum quantity, sample approval, intellectual-property terms, test responsibility and schedule for each change. Custom application and system-development time should never be hidden inside the standard production lead time.

Define quality and acceptance records

Ask for the controlled hardware, firmware and application versions; incoming and final checks; identifier control; pairing test; charging test; functional test; sampling plan; defect handling; and shipment release record.

State who witnesses acceptance, where it occurs, what constitutes a defect and whether rework triggers retest. Require pass, fail, exception and corrective-action fields rather than a simple inspected stamp.

Write commercial terms clearly

Include currency, price basis, quote validity, payment milestones, taxes, duties, Incoterm, production start condition, sample approval, change control, packing, insurance, shipping method, destination, warranty, repair route and spare-unit plan.

Separate factory completion from port departure, international transit, customs clearance and final delivery. A production target is not a delivered-to-site date.

Use the ChatField procurement contact to provide the completed schedule and request clarification.

Compare suppliers on evidence

Create a compliance table with required, offered, exception, evidence reference and commercial impact columns. A supplier that identifies a limitation may be safer than one that marks every row compliant without detail.

NIST's 2026 due-diligence guide highlights supplier provenance, resilience, foundational cyber practices and supply-chain tiers as useful assessment areas for information and communications technology suppliers.

Score the whole operating and support package, not only device price.

100+ unit RFQ checklist

  • Users, roles, routes and operating problem
  • Complete phone, Bluetooth, terminal and application path
  • Destination country and exact radio variant
  • Production, pilot and spare quantities
  • Direct and supported relay acceptance tests
  • Message mix, delay and capacity criteria
  • Security, update, support and end-of-life answers
  • Complete accessories and packed configuration
  • Battery transport evidence and responsible shipper
  • Standard product and custom work separated
  • Quality records, defects and retest rules
  • Price, payment, Incoterm, delivery and warranty

Sources reviewed

NIST, FCC and PHMSA do not endorse ChatField or J25. Their material provides procurement, equipment-authorization and transport context, not a universal approval or quotation.

Back to blog