FFL and Firearms Compliance
Summary
Flxpoint handles firearms compliance for FFL (Federal Firearms License) transfers β it identifies firearms and serialized components, collects and validates FFL information during fulfillment request generation, splits firearm and non-firearm orders, and routes FFL data to suppliers.
This guide covers how Flxpoint handles firearms compliance for FFL (Federal Firearms License) transfers. Flxpoint identifies firearms and serialized components, collects and validates FFL information during fulfillment request generation, splits firearm and non-firearm orders, and routes FFL data to suppliers. Serialized components (like AR-15 lower receivers) trigger FFL requirements; non-serialized parts (like upper receivers) do not.
How do I stop firearms from importing into my catalog if I do not hold an FFL? Use a Post-Mapping workflow rule to set Do Not Import for firearm categories (for example, product type Firearms), and do not enable listing of those products. This prevents whole firearms from syncing into your storefront when you cannot legally sell them.
Why did my firearm order get placed on hold? The FFL validation workflow found incomplete information: a missing FFL License Number, Expiration Date, or address/contact detail. Complete the missing FFL fields and rerun validation to release the order.
A supplier like GunBroker needs FFL data in a specific format. How does Flxpoint send it? Flxpoint maps FFL fields to the vendor's required format automatically, with optional manual PDF or CSV upload for suppliers that need manual processing, plus status monitoring to confirm the data was transmitted.
FFL information not making it to a specific distributor. The order reaches the supplier (for example, RSR) without the FFL attached, even though FFLs are updated in Flxpoint. Check the source's FFL field mapping and submission format for that distributor so the required data is included in the payload.
Firearm orders not processing properly (FFL added manually). Recent firearm orders fail to process and staff add FFL info by hand. This is usually incomplete validation data or a mapping gap holding the order. Complete the required FFL fields and confirm the firearm identification workflow is enabled on the source.
GunBroker category mismatch. The FFL flag does not match the category settings, so orders are miscategorized. Update the mapping templates to align the categories with the FFL flag.
Vendor submission format error. A format mismatch for API or PDF submissions blocks the FFL data from being accepted. Adjust the export format to match the vendor's requirements.
