US915 vs. EU868: What LoRa Device Buyers Should Check Before Importing

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

A LoRa product offered as a U.S. version and a European version may look identical while using different radio configurations. Selecting the wrong version can create compatibility, performance, support and regulatory problems.

US915 and EU868 are common shorthand labels in LoRaWAN discussions, but a buyer still needs the exact supported frequency plan, finished-product hardware and destination evidence. A non-LoRaWAN LoRa mesh product also requires a model-specific regional review.

This article is a procurement checklist, not legal advice. Rules and standards can change, and the manufacturer or importer should confirm current requirements for every destination.

Short answer

Do not assume a US915 product can be used in Europe or an EU868 product can be used in the United States. The regions use different portions of spectrum and different technical constraints. Hardware tuning, antenna design, firmware, channel configuration, transmit behavior and compliance documents may differ.

Place the destination country on the purchase order and require the supplier to identify the exact regional model before payment and shipment.

What US915 and EU868 mean

Within LoRaWAN, the LoRa Alliance Regional Parameters document defines channel plans for different regulatory regions. US915 is associated with the U.S. 902–928 MHz plan. EU868 is associated with European operation in the 863–870 MHz area under applicable regional and national requirements.

Those labels are useful for configuration, but they do not replace product documentation or regulatory approval. The ChatField technology overview explains the radio layer without turning a regional label into a global-use claim.

The frequencies are different

A U.S. device and European device may not listen or transmit on the same channels. Even a broadly tunable radio chip does not prove that the finished device, antenna and firmware support both versions.

Ask for the supported frequency range of the finished product, not only the semiconductor datasheet. Confirm whether regional selection is factory-set, firmware-controlled or available as separate hardware.

Do not instruct users to change hidden settings to reach an unsupported band.

The channel plans are different

LoRaWAN regional parameters specify more than a center frequency. They cover channel frequencies, data rates, output power, dwell time and related behavior. A gateway, end device and network configuration must use compatible regional settings.

For a product-specific LoRa mesh, the manufacturer should provide equivalent configuration information and a supported deployment method. Do not assume that a LoRaWAN channel-plan name fully describes a non-LoRaWAN mesh protocol.

The ChatField signal-path page helps buyers identify which devices need matching radio configurations.

Power and spectrum-access rules differ

The United States permits certain unlicensed devices in the 902–928 MHz ISM band under FCC Part 15 rules and applicable equipment requirements. European short-range-device rules and harmonized standards use different sub-bands, power limits and spectrum-access conditions, which can include duty-cycle or listen-before-talk behavior.

Therefore, a transmitter setting accepted in one market should not be copied into another. The final assessment depends on the product, bandwidth, modulation, antenna and intended use.

Do not market “license-free” as “rule-free.” Unlicensed operation remains subject to technical and interference conditions.

Antenna design may change

An antenna optimized around one regional band may perform poorly in another. The connector, internal antenna, matching network, enclosure and body-worn placement all affect the finished result.

Ask whether the regional versions use different antennas or component values. If an external antenna is permitted, require the approved antenna type and gain limits.

A frequency menu alone does not retune the physical antenna.

Firmware and application behavior may change

Regional firmware can control channels, power, timing and network parameters. App setup may ask for a region or hide it according to the shipped model.

Record the hardware revision, firmware build and selected region during evaluation. Test restart, factory reset and update behavior to ensure the device does not return to an incorrect default.

Ask whether one update file serves every region and how the software prevents invalid configurations.

Certification documents must match the model

For the United States, verify the FCC identifier and exhibits for the exact device under review. For the European market, request the applicable declaration, test documentation and product information required for the intended market. A supplier should not substitute a component report for finished-product evidence without explaining the scope.

LoRaWAN certification is separate from national or regional radio compliance. It can support protocol interoperability but does not replace the relevant market authorization.

The current J25 product page and J25 specifications identify FCC ID 2BVP9-J25 as U.S. evidence for J25. They do not establish an EU version or apply to a future product.

Do not use one range result globally

Range can change with permitted power, antenna, channel settings, interference, terrain and carrying method. A test completed with one regional version should not be copied onto another version without matching conditions.

Require the campaign to label the region, hardware, firmware, antenna, terrain and test method beside every distance statement. Treat theoretical link budget and actual field performance as separate evidence.

The off-grid communication page explains why terrain and system boundaries must accompany range language.

Confirm destination before fulfillment

Crowdfunding surveys often collect addresses after the campaign. The creator should map each supported destination to a validated regional SKU before locking production.

Backers who move between pledge and fulfillment should update the shipping country. A warehouse should not select the version from language, currency or plug type alone.

If a destination is unsupported, the campaign should disclose that before accepting or confirming the order.

Plan cross-border team operations

A company may own equipment for U.S. and European teams. Keep the regional fleets separately labeled, inventoried and configured. Do not assume that taking a U.S. unit on a European trip is acceptable because the device is privately owned.

For multi-country projects, identify the local responsible party, permitted configuration, support process and replacement inventory for each country.

Regional-version purchase checklist

  • Destination country and intended operating locations
  • Exact product model, SKU and hardware revision
  • Supported frequency range and channel plan
  • Factory-set or user-selectable regional configuration
  • Antenna type, tuning and approved accessories
  • Firmware build and regional safeguards
  • Applicable FCC, European or other destination evidence
  • LoRaWAN certificate where the product claims LoRaWAN compliance
  • Range evidence labeled with the tested regional version
  • Packaging and device labels that identify the version
  • Fulfillment controls that map address to SKU
  • Update, replacement and cross-border support policy

Questions for a crowdfunding campaign

  • Which countries will receive rewards?
  • Which regional hardware versions are production-ready?
  • Are US915 and EU868 separate SKUs?
  • Which compliance documents match each SKU?
  • Does the antenna or enclosure differ?
  • How does the app prevent an invalid region setting?
  • What happens when a backer changes countries?
  • Are prices and delivery estimates different by region?
  • Which field tests were completed for each version?
  • Which regional versions remain development targets?

ChatField regional boundary

Use the ChatField contact page to identify the destination and request current regional availability. Public J25 FCC evidence supports the identified U.S. model evidence; it must not be described as proof of EU market readiness or future-product compliance.

Sources reviewed

The LoRa Alliance, FCC and ETSI do not endorse ChatField or its products. Their materials are cited for regional configuration and regulatory context. Buyers should verify the current rules applicable to their destination.

Regresar al blog