How to Write an RFQ for a J25 LoRa Mesh Pilot
Prepared by ChatField Editorial Team. Published August 4, 2026.
A useful request for quotation for off-grid team communication does more than ask for unit price and maximum range. It defines the pilot users, phone environment, routes, acceptance evidence, compliance documents and commercial decision that will follow the test. This guide shows U.S. B2B buyers how to write an RFQ for a phone-paired LoRa mesh pilot without turning best-case specifications into guaranteed field performance.
Start with the business decision
State what the pilot will decide. Examples include whether a defined team can exchange voice and messages along a work route without cellular service, whether supervisors can maintain team visibility at selected checkpoints, or whether a distributor has enough technical evidence to consider a sample-to-volume discussion.
Avoid broad requirements such as “works everywhere” or “emergency grade.” They are not measurable. An RFQ should name the users, operating area, test duration, shift pattern and evidence that will support a purchase, rejection or revised test.
Describe the phone-paired architecture accurately
ChatField J25 is a phone-paired LoRa mesh communication terminal, not a conventional standalone handheld radio. The smartphone remains the interface for push-to-talk, text messages, offline maps and team location. Bluetooth connects the phone to J25, and the J25 terminals create the local LoRa mesh link between equipped participants.
Put that architecture directly in the RFQ. It prevents a supplier response from being evaluated against the wrong device category. Buyers can review the operating model on the Technology page before defining the pilot.
Name the exact product and evidence
Require the quotation to identify the model, hardware version if applicable, application version, included accessories and regulatory evidence. For J25, the FCC ID is 2BVP9-J25. The applicant and grantee shown in the FCC documents is Jingxi Box (Shenzhen) Intelligent Technology Co., Ltd.; ChatField is the product brand.
J25 is the current product for this evaluation. J28 is a separate next-generation development project and should not be substituted into the RFQ unless the buyer intentionally requests a separate J28 discussion. Review the Compliance page and ask the supplier to match every document to the quoted model.
Define the phone and application matrix
List the phone models and operating-system versions that the pilot will use. Include the number of devices per phone type, Bluetooth permission settings, application installation owner and the recovery procedure after a phone restart, application restart or Bluetooth interruption.
- Phone manufacturer and model
- Operating-system version
- Application version
- Bluetooth and location-permission setup
- User login or team-joining procedure
- Recovery steps and maximum acceptable recovery time
Write route scenarios instead of a universal range requirement
The RFQ should describe the actual checkpoints, terrain, buildings, vehicles and expected user movement. ChatField's bounded language is up to 10 km in ideal open terrain and about 5 km in urban testing with high buildings and structural obstruction. Buyers may evaluate up to two participating relay nodes. These are evaluation references, not universal guarantees.
Ask for a route test with recorded conditions. Note the device positions, relay participation, antenna placement, weather where relevant and whether cellular data was disabled. The J25 Specifications page should be read together with field evidence rather than used as a substitute for it.
Set acceptance evidence before the quotation is approved
Define what the buyer must receive at the end of the pilot. A procurement-ready evidence package can include:
- a device and phone assignment sheet;
- a route map with planned checkpoints;
- voice and message delivery observations;
- location-update observations at defined intervals;
- Bluetooth interruption and recovery results;
- charging, battery and shift-handoff records;
- exceptions, failed scenarios and retest decisions; and
- the exact FCC evidence reviewed for the quoted model.
The RFQ should not require a vendor to invent a success rate before conditions are known. It should require transparent results against the buyer's documented scenarios.
Separate technical acceptance from commercial terms
Price, minimum order quantity, lead time, warranty, support, branding and OEM or ODM questions belong in the quotation, but they should not determine whether the pilot technically passed. Use two decision sections: technical acceptance and commercial review.
For the commercial section, request sample quantity, sample price, estimated volume tiers, accessory list, production lead-time assumptions, warranty process, application-support scope and the legal entity that will appear on the quotation and invoice. Do not assume the brand, FCC grantee and contracting entity are automatically the same.
Use a controlled next step
A strong RFQ ends with a defined decision meeting. State who will review the evidence, when exceptions must be resolved and what conditions would justify a larger test or bulk-order discussion. Keep failed scenarios in the record; they often identify training, route or configuration changes that should be tested before scale-up.
To prepare a buyer-specific pilot request, review the available Products information and contact ChatField with your team size, phone matrix, route description, test dates and required evidence. ChatField can then discuss a controlled sample-evaluation scope without presenting a best-case claim as a guaranteed deployment result.