Updated October 28, 2026. A commercial drone-delivery network needs more than an aircraft and a dispatch application. Its ground endpoints must let merchants hand off eligible packages, position or recharge aircraft, manage the public interface, recover from faults, and give the operator evidence that the next flight can be launched safely. A rooftop dock, charging tower, micro-hub, secure delivery station and package portal solve different parts of that problem. They are not interchangeable products.
This independent procurement guide is for retailers, hospitals, logistics networks, property owners and integrated-UAV-system buyers planning a U.S. deployment. It provides a copyable request-for-proposal (RFP) scope, installation questions, an acceptance-test matrix and a vendor scorecard. It does not assert that any station has FAA approval merely because its manufacturer advertises autonomous operation; the operator’s actual flight authority and each site’s approvals must be confirmed separately.
For a broader package-level specification, start with the complete UAV system RFQ template and UAV Systems intelligence hub. This article focuses on the fixed or semi-fixed ground endpoint.
- Choose the ground-endpoint architecture before buying hardware
There are at least five useful patterns. A network may combine them.
| Endpoint model | Primary job | Main procurement risk |
|---|---|---|
| Aircraft dock or rooftop perch | Receive, position, protect or stage the aircraft between jobs | Mounting, access, weather, serviceability and aircraft compatibility |
| Charging or battery-service station | Restore energy and track readiness | Electrical capacity, battery condition, thermal controls and fault recovery |
| Merchant loading interface | Get a verified order from employee to aircraft or pod | Package dimensions, custody transfer, human factors and incorrect loading |
| Secure receiving locker or parcel portal | Receive or release goods while separating customers from flight hardware | Access control, identity, failed deliveries and chain of custody |
| Multi-aircraft micro-hub | Coordinate aircraft, staff, inventory and dispatch at a location | Throughput bottlenecks, noise, land use and maintenance logistics |
For example, Matternet’s September 28 M3 announcement describes an aircraft, a storage-and-charging dock and a separate package portal. Matternet targets commercial M3 service in the second half of 2027: the announcement is a forward-looking system plan, not evidence that the M3 is commercially operating today. By contrast, September 2026 reporting describes Flytrex placing aircraft at restaurant rooftop docks and using a lowered hook for merchant loading. This illustrates a different handoff workflow; reported cost reductions are supplier claims rather than independently audited results.
Do not select a dock from a catalogue before answering whether the network uses an aircraft landing, a tethered parcel lowering system, a detachable delivery pod or a secure handoff station. Those choices determine the entire physical design.
- Copyable RFP: specify the operating mission and site
Send the same completed information to each vendor:
- Commercial mission: retail goods, prepared food, medical supplies, field-service parts or another defined shipment category; note any special handling or prohibited goods.
- Expected flow: average, peak-hour and peak-day completed transfers; peak simultaneous arrivals; forecast by month, not just a single annual estimate.
- Aircraft interface: operator, approved aircraft type, size and mass, landing or hovering method, charging interface, navigation aids and any proprietary dependencies.
- Parcel interface: maximum loaded dimensions and weight, approved packaging, loading height, barcode or order verification and secure release method.
- Property information: site plan, roof or ground area, height, clearances, access routes, structural drawings, available electrical service, connectivity and fire-protection conditions.
- Environment: wind, temperature, precipitation, snow/ice, dust, lightning exposure, wildlife and the consequences of station downtime.
- Operating model: staffed versus unattended; hours of service; maintenance response windows; remote monitoring; customer-access restrictions.
- Authority and liability: named Part 135 operator where applicable; approved flight and ground procedures; local zoning, property consent, site/building/fire review and required environmental analysis.
- Data and integration: order management, dispatch, aircraft telemetry, access events, inventory, incident records and cybersecurity responsibilities.
Ask the vendor to return a line-by-line compliant / exception / proposed alternative / evidence response. A marketing brochure is not a test report. A generic reference installation is not evidence that the proposed roof, aircraft and parcel workflow are compatible.
- Site engineering and local approvals: six diligence gates
Gate A — property rights and land use. Confirm rooftop/ground access, lease and landlord consent, zoning and municipal procedure. A successful FAA flight certification does not automatically authorize a specific hub at a specific address. The FAA’s package-delivery guidance distinguishes operator and aviation permissions from local land-use and community requirements. The Westborough site-permitting case shows why separate state and local reviews must be tracked.
Gate B — structure and physical access. Obtain a site-specific engineering assessment for anchor loads, vibration, roof membrane, wind exposure, penetrations, drainage, maintenance fall protection and safe separation from equipment. Never substitute a vendor’s statement that a dock is “roof-ready” for an engineer’s evaluation of an actual roof.
Gate C — electrical and thermal safety. Define continuous and peak load, charging power, protective devices, grounding, disconnects, surge protection, backup behavior, battery fault detection and local fire-code review. Ask who owns the design, permit, inspection and maintenance record. Do not invent a universally applicable battery spacing or suppression requirement: the authority having jurisdiction and the adopted code determine the site obligations.
Gate D — people, parcels and wildlife. Document worker loading positions, public exclusion areas, drop-zone control, retrieval rights, wildlife observations, signage and contingency landings. Model noise and daily operating windows, including the potential effect on neighboring homes or schools.
Gate E — communications and resilience. Survey actual primary and backup connectivity at the height and position of the endpoint. Specify fail-safe behavior for broadband outage, power interruption, clock drift, lost aircraft connection, delayed orders and failed access-control checks. The FCC’s scheduled October 29, 2026 consideration of additional 800 MHz cellular access may expand future communications options, but the vote has not occurred as of this article’s date, and spectrum rules would not replace FAA authorization. See the site’s FCC 800 MHz policy watch.
Gate F — operational approval. Require a responsibility register identifying who obtains the applicable Part 135 authority, exemptions/waivers, airspace permissions, environmental review, site permissions, procedures and customer communications. The proposed Part 108 BVLOS framework must not be described as a current blanket operating authorization.
- Define handoff and custody as a state machine
A delivery endpoint is an operations system. A useful procurement contract should spell out the allowed transition of each package and the evidence retained at every step:
- Order accepted: merchant and operator agree the item, address and weather/airspace conditions are eligible.
- Package prepared: weight, dimensions, seals and any special handling constraints are checked.
- Handoff requested: the employee receives a specific loading instruction tied to the order ID, station ID and authorization window.
- Transfer verified: a scan, verified latch event or other agreed method confirms correct goods and custody status. A camera alone may not establish legal custody.
- Aircraft or pod ready: the system confirms the relevant health, battery, load and station conditions; the authorized operator controls the operational release.
- Delivery or exception recorded: evidence distinguishes completed delivery, retry, damaged cargo, failed release and handoff to a ground courier.
- Reconciliation closed: the merchant’s order system, carrier ledger and customer status have a consistent final outcome.
Insist on idempotent event handling: duplicate webhooks or reconnects must not accidentally issue a second package or charge the merchant twice. Give every event a stable identifier, timestamp, source, order reference and station reference. Include an operator-controlled manual override with traceable authorization and fail-closed rules for safety-critical commands. The merchant integration guide and UAV Systems hub cover adjacent systems; this document’s focus is the physical and custody boundary.
- Security and serviceability are procurement requirements
A commercially useful dock has to remain secure and supportable for years. Request written evidence for:
- Identity: named roles for store employee, aircraft operator, site host, support provider and remote administrator; least-privilege access and rapid credential revocation.
- Data: event-log retention, restricted access, clock synchronization, personal-data minimization, evidentiary export and contractual rights to retrieve records after termination.
- Connectivity: encrypted interfaces, device authentication, key lifecycle management, network segmentation, remote access limits and degraded-mode behavior.
- Maintenance: documented preventative service, approved parts, spares, technician response, support hours and update/rollback process.
- Software change control: version compatibility for dock controller, aircraft, package portal and dispatch interface; test procedure before production rollout.
- Cyber incident handling: who can isolate a compromised endpoint, suspend launches, notify counterparties, preserve logs and restore normal operation.
NIST’s Cybersecurity Framework 2.0 and SP 800-82 Rev. 3 on operational-technology security provide useful risk-management references, not a special mandatory certification for every drone dock. NIST announced a draft Revision 4 in September 2026; buyers should distinguish final guidance from drafts.
- Acceptance tests: do not sign off on a showroom demonstration
Write acceptance criteria before placing orders. Test at an agreed pilot location, with the actual aircraft, packages, staff and network interfaces; no real flight may occur without the operator’s applicable authority. Use at least these twelve tests:
| Test | Required evidence |
|---|---|
| 1. Station identity | Installed serial, ownership, network identity and approved configuration match contract |
| 2. Site readiness | Engineering, electrical, property and applicable local approvals are documented |
| 3. Correct-order handoff | Valid order and package accepted with custody event and traceable ID |
| 4. Wrong package / overweight | Unsafe or unauthorized parcel rejected without dispatch |
| 5. Duplicate message | Replayed event cannot cause duplicate release or billing |
| 6. Power interruption | Endpoint enters specified safe state and recovers via documented procedure |
| 7. WAN or cellular loss | No unsupported release; alerts and resynchronization verified |
| 8. Charging fault | Battery/charger fault triggers isolation, alert and maintenance workflow |
| 9. Lost access credential | Revoked account cannot access station or release parcel |
| 10. Weather stop | Station or operator inhibits operations at approved thresholds |
| 11. Emergency stop | Responsible operator can inhibit flight or loading according to approved procedures |
| 12. Failed delivery | Return, retrial, disposal or ground fallback recorded with custody intact |
Set numeric thresholds in the contract—for example, authorized package weight, required logging latency, support response and uptime measurement window—using evidence specific to the aircraft and business. There is no universal vendor-neutral success rate that proves every site safe or commercially viable.
- Evaluate price per completed delivery, not dock price alone
An inexpensive dock can be costly when it delays loading or demands permanent staff; a feature-rich station can be economically wasteful at low throughput. Ask for an itemized five-year estimate with the following categories: hardware, site construction, electrical/connectivity works, permits, recurring software and carrier connectivity, power, inspection, maintenance, labor, spares, insurance allocations, security, removal/restoration and decommissioning.
Use this simple planning equation, with all terms measured over the same period:
Endpoint cost per completed order = (annualized installation and hardware + annual operating and maintenance costs + endpoint-specific exception costs) / annual successfully completed orders at the site.
For illustration, if a site allocates $24,000 annually to infrastructure and maintenance and records 12,000 completed deliveries, its modeled endpoint contribution is $2.00 per completed delivery. At 3,000 deliveries, the same fixed spend contributes $8.00. These are hypothetical examples, not quotations or operating results. They exclude aircraft, air-carrier staff, line-haul, insurance beyond the stated endpoint allocation and customer acquisition. The site’s drone-delivery cost-per-order worksheet provides the broader model.
Request pricing under both an expected and a low-utilization case. Require a termination scenario covering roof restoration, ownership of telemetry and order records, equipment removal, and whether the next operator can reuse power, mounting and network infrastructure.
- Weighted vendor scorecard (100 points)
| Dimension | Weight | Evidence to demand |
|---|---|---|
| Aircraft and package-interface compatibility | 20 | Validated interface and approved loading procedure |
| Site engineering and safety case | 20 | Site drawings, review ownership and hazard mitigations |
| Security and operational resilience | 15 | Outage tests, access model, audit logs and cyber process |
| Throughput and workflow performance | 15 | Measured peak-hour handoff and exception performance |
| Service and lifecycle economics | 15 | Itemized five-year cost, spares, SLA and exit obligations |
| Compliance accountability and documentation | 10 | RACI covering FAA, local, property and environmental gates |
| Interoperability and data portability | 5 | API schema, export rights and lock-in disclosures |
| Total | 100 | Do not score missing critical safety or legal evidence as a tradeable price advantage. |
Score each dimension against a common evidence scale: 0 = absent, 1 = claim without demonstration, 2 = documented partial compliance, 3 = demonstrated compliance with exceptions, 4 = demonstrated compliance to agreed acceptance criteria. Weighted points equal weight multiplied by the 0–4 rating divided by four. Treat unresolved aviation authority, structural safety or unsafe loading as a hard stop, even if total points are high.
- Twelve questions to send every bidder
- Which aircraft, firmware and parcel interfaces have been validated with this exact dock or portal?
- What is included in hardware pricing, installation, civil/electrical work and recurring subscriptions?
- Who signs the site engineering documents, and who obtains property, municipal and fire approvals?
- What limits apply to loaded weight, size, center of gravity and package capture or release?
- What is the demonstrated handoff throughput under the stated labor model?
- How do battery health, charger faults, fire risk and incident isolation work?
- What happens during loss of power, internet, operator link or cloud service?
- What records show acceptance, custody, dispatch, attempted delivery and return?
- What third parties can access the endpoint, logs, imagery or customer information?
- Which updates require fresh safety testing or regulatory coordination?
- Who supplies spare parts, on-site response and uptime service credits, and where are support personnel located?
- What data, hardware, integration and roof-restoration obligations survive contract termination?
- Procurement handoff and next steps
A strong RFP is a shared set of deliverables, not a promise that automation eliminates permits or staff. For each proposed site, require a site survey; preliminary drawing; responsibility matrix; load/power and network plan; cybersecurity and safety documentation; workflow map; measurement and acceptance protocol; commercialization schedule; five-year cost model; and written exceptions. Pilot one real location before copying the design across a region.
For a vendor-neutral picture of the broader sector, see the commercial delivery ecosystem, operator and market tracker, and drone delivery regulation overview. These resources distinguish operating sites from proposed deployments and individual approvals from general market announcements.
Editorial independence: UAVPackage.com is not affiliated with or endorsed by any provider named here. Product announcements and claimed benefits are attributed to their sources; no performance promise or legal conclusion is implied. Organizations evaluating the developed domain and editorial asset may use the private strategic acquisition inquiry page. This does not affect coverage or rankings.
Sources and update boundaries
Primary FAA guidance: Package Delivery by Drone (Part 135). Technical and commercial examples: Matternet M3 announcement, September 28, 2026; Flytrex rooftop dock coverage, September 17, 2026; DoorDash Air system announcement, September 30, 2026. Cybersecurity references: NIST CSF 2.0 and NIST SP 800-82 Rev. 3. Connectivity context: FCC October 29 agenda reporting. Claims and procedural status checked October 28, 2026; recheck FCC outcomes and operator launches before publication after that date.
