CloudFFL Finder For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download

No ratings yet

Free

Follow for free plugins, new theme releases and theme news

Plugin Description

CloudFFL Finder for WooCommerce supports dealer selection and order routing for products you configure as requiring an FFL transfer. It looks up dealer records through the CloudFFL API and records the selected dealer on the order. An active CloudFFL API key is required for dealer search and verification. Merchants remain responsible for determining applicable transfer, shipping, age, and other legal requirements; the plugin does not certify legal compliance.

The plugin is free and is developed and maintained by CloudFFL, operated by Longhorn Web Solutions, LLC, the provider of the paid CloudFFL API service. API service charges are billed separately by CloudFFL; there is no separate plugin license fee.

Key Features:

Easy Setup – Enter your CloudFFL API key and you’re ready to go
Product Flagging – Mark individual products as requiring FFL transfer
Category-Level FFL – Flag entire product categories (e.g., Firearms, Suppressors) to require FFL
Ammunition State Restrictions – Configure which states require FFL for ammunition categories
Smart Cart Detection – Automatically detects FFL items and prompts for dealer selection
State-Based Ammo Gate – Dynamically shows FFL finder based on shipping state for ammo
Intuitive Dealer Search – Search by ZIP code, city, or dealer name
Interactive Map – Optional Leaflet/OpenStreetMap integration (no API key required)
Order Integration – FFL dealer info saved to orders and included in emails
Admin Dashboard – View selected dealer details on every order

How It Works:

Mark products as “FFL Required” in the product editor, OR configure FFL-required categories in settings
When a customer adds FFL items to their cart, they’re prompted to select a dealer at checkout
The customer searches for nearby dealers and selects one
The dealer’s address becomes the shipping address
Order confirmation and admin views show the selected dealer details

Category-Level FFL:

For stores with large catalogs, you can flag entire categories instead of individual products:

Go to WooCommerce > CloudFFL > FFL Required Categories
Select categories that contain FFL items (e.g., Firearms, Suppressors, Receivers)
Any product in those categories will automatically require FFL dealer selection
Child categories are automatically included when a parent is selected

Ammunition State Restrictions:

Configure ammunition routing according to your store requirements:

Configure which product categories contain ammunition in plugin settings
Select the states for which your store requires FFL shipment for ammunition
When a customer ships to a restricted state with ammo in cart, they must select an FFL dealer
Works alongside product and category flags; review these settings for your catalog and destinations

Requirements:

WordPress 5.8 or higher
WooCommerce 6.0 or higher
PHP 7.4 or higher
CloudFFL API key (create a CloudFFL account, then open API Keys)

External Services

CloudFFL FFL API

This plugin connects from your WordPress server to https://api.cloudffl.com/api/v1 (or the API endpoint configured by the merchant) to search for dealers and verify a selected dealer before saving it to an order. A CloudFFL account and API key are required; service access is governed by your CloudFFL plan.

Requests occur when a shopper or administrator searches for dealers, when a dealer selection is verified during checkout or admin assignment, and when an administrator clicks Test Connection. Search requests send the entered ZIP code, city/state, dealer name or latitude/longitude, search radius, result limit and active-status filter as applicable. Verification requests send the selected dealer ID. Test Connection sends a fixed ZIP search (90210, radius 5, limit 1). Requests include the merchant’s API key for authentication and ordinary server HTTP metadata, including server IP and user agent. These API methods do not send the cart, payment details, or a complete customer billing/shipping profile. A search ZIP or other location input may originate from the shopper’s address.

Returned dealer identity, license and address data are used to display results and populate order dealer/shipping details. See the CloudFFL Terms of Service, FFL API Addendum and Privacy Policy for the service’s policies. If you configure a different API endpoint, review that provider’s policies too.

OpenStreetMap map tiles

When an enabled dealer map is displayed, the visitor’s browser requests map images directly from tile.openstreetmap.org. Tile coordinates and zoom identify the viewed area; requests also disclose the visitor’s IP address, browser/user agent and referrer information as permitted by the browser/site policy. Requests continue when the map is panned or zoomed. This service supplies the base map; dealer records come from CloudFFL. The plugin does not send the CloudFFL API key, order contents or payment data to the tile service.

Map data attribution: (c) OpenStreetMap contributors, available under the Open Database License. Keep this attribution visible on maps. Service use is subject to the OSMF Terms of Use, Privacy Policy and Tile Usage Policy. Public tile availability is not guaranteed. Disable Map View in plugin settings if you do not want map-tile requests.

Source and Build Instructions

The distribution includes readable Block Checkout source in src/, Classic/admin source in assets/js/ and assets/css/, webpack.config.js, package.json, package-lock.json. Development tests and release/check scripts remain in the source checkout. BUILDING.txt describes dependency installation, asset compilation and release checks. Leaflet 1.9.4, its readable source, source maps, images and BSD-2-Clause license are bundled in assets/vendor/leaflet/. See THIRD-PARTY-NOTICES.txt for source provenance and licensing.

Copyright and License

Copyright (C) 2026 Longhorn Web Solutions, LLC. Developed under the CloudFFL brand. Original plugin code is GPL-3.0-or-later; see COPYRIGHT.txt and LICENSE.txt. Leaflet retains its original BSD-2-Clause license and copyright notices. Third-party provenance and map attribution are documented in THIRD-PARTY-NOTICES.txt. The hosted API service terms are separate from the plugin’s GPL license.