FFL and Firearms Compliance

July 20, 2026

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.

Overview

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.

Important notes

Note: Serialized components determine FFL requirements. A lower receiver requires an FFL transfer; an upper receiver does not. Antique (pre-1899) and black powder firearms are generally exempt. Flxpoint workflows distinguish these automatically.

Note: Enable “May Contain Firearms” per source. Turn on May Contain Firearms in the source settings, then use If-Then rules (for example, Category = Handguns → Firearm = True) so firearms are identified and flagged.

Note: Mixed orders are split automatically. Orders with both firearm and non-firearm items split so non-firearm items ship immediately, while firearm items hold until FFL validation completes.

Note: Validation holds incomplete orders. FFL License Number, Expiration Date, and address/contact details are validated at fulfillment request generation. Orders missing data are held for manual review.

Note: Requires FFL flag in mapping templates. The Requires FFL flag is now exposed in the inventory data layer. You can use this field in your default mapping templates to identify compliance requirements for specific inventory items as they flow from your source into the Flxpoint Master Catalog.

FAQs

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.

How do I manually add FFL information to an order?

To add FFL details, navigate to the specific order in the Flxpoint UI and locate the FFL section. You must provide the FFL license number, dealer name, and full address. This information can be entered manually if it was not captured during checkout or pulled from a customer record, and it is required to release orders held for validation before they are routed to your fulfillment partner.

Common issues

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.

FFL attached to an order is not recognized by the fulfillment request?

Fulfillment requests typically inherit FFL data from the parent order automatically. If the data is missing, ensure all required FFL fields (License Number, Expiration, and contact details) are fully populated on the order before generating the request. Note that manual PDF FFL attachment directly to a fulfillment request is currently only supported for the Iron Valley integration; for other suppliers, FFL data must be mapped and validated at the order level.

Mapping the Requires FFL flag

What it does

The Requires FFL flag is a backend data field in Flxpoint that identifies inventory items requiring a Federal Firearms License for shipment. This field is now exposed in the inventory data layer, allowing you to automate compliance workflows by identifying regulated items during the inventory import process.

Mapping the FFL flag

To use this data, you must map the incoming field from your source to the corresponding attribute in Flxpoint. The default mapping templates have been updated to include this field as a standard option.

Navigate to your Source settings and select Mapping Templates.
Locate the Get Inventory mapping template.
Find the Requires FFL field in the Flxpoint destination column.
Map it to the appropriate column or attribute provided by your supplier's data feed (e.g., a boolean true/false or a specific compliance code).
Save the template.

Technical details

This update is a backend data exposure change. While the field is available for mapping and automated workflows, please note the following:

UI Visibility: There are currently no dedicated UI toggles for this flag; it is managed strictly through data mapping and backend attributes.
Data Flow: Once mapped, this attribute can be used to trigger specific automation rules or routing logic tailored to firearms compliance.

Note: Ensure your source data consistently provides this flag to prevent regulated items from being processed as standard inventory.

BigCommerce FFL order processing with Master FFL

OVERVIEW

If you sell firearms through BigCommerce and use the Master FFL (FFL360) app to collect FFL dealer information at checkout, this connects Master FFL to Flxpoint. FFL details are pushed to Flxpoint by webhook and attached to the order on import, so firearm items route to the FFL dealer while accessories ship normally, without manual sorting.

SETUP

Step	What to do
1. Channel ID	In Connections → Sales Channels, open your BigCommerce channel and note the numeric Channel ID.
2. Webhook URL	In Master FFL, set the webhook to https://api.flxpoint.com/public/webhook/masterffl/{channelId}/ingest as an HTTP POST.
3. Enable import	In the channel's Get Orders Advanced Configuration, enable Import FFL details from BigCommerce via Master FFL and enter your MasterFFL API Key.

HOW THE FLOW WORKS

Checkout in BigCommerce: the shopper selects an FFL dealer in the Master FFL app.
Webhook ingest: Master FFL sends an HTTP POST to the ingest endpoint; it must complete within 20 seconds and returns HTTP 204 on success.
Payload staged: Flxpoint stores the FFL payload keyed by order and channel, even before the order imports.
Order imports: Get Orders imports the order and checks staging for a matching FFL payload.
FFL applied: the FFL details are attached to the order and the staged record is removed.

IMPORTANT NOTES

Note: The webhook URL and method must be exact, sent as HTTP POST with the numeric Sales Channel ID. Success returns HTTP 204; any other status is treated as a failure by Master FFL.Note: Firearm items receive the FFL dealer shipping address derived from the FFL details, while accessory items keep the standard checkout address. No manual sorting is required.Note: Even when MasterFFL data arrives, an order can still be flagged Additional Info Required depending on your FFL validation settings. Turning off automatic validation does not remove the need for validation; it just shifts it to a manual step.

COMMON ISSUES

Master FFL reports a 404 when testing the webhook

Re-check that the URL matches the format exactly, that the channel ID is the correct numeric Flxpoint Sales Channel ID, and that the webhook is configured as HTTP POST.

An FFL field (for example the image URL) is not importing on firearm orders

If FFL data mostly imports but a specific field is missing across all firearm orders, confirm Master FFL is populating that field on its side and that the integration is enabled in the BigCommerce channel settings. Provide an example order to support so the payload can be checked.

Firearm orders are not processing and FFL has to be added manually

When firearm orders repeatedly arrive without complete FFL details, they are flagged for manual review. Verify that the FFL was selected from the app's dealer network at checkout and that the webhook is delivering successfully; incomplete data (for example a missing expiration) forces the manual step.

FAQS

Do I need Master FFL?

Only if you sell firearms through BigCommerce and collect FFL dealer information at checkout. It is what makes FFL details appear automatically on the imported order instead of being chased down.

Why is a firearm order still flagged for manual review when FFL data came through?

Depending on your validation settings, the fulfillment request can be marked Additional Info Required so a person confirms the FFL, even when the data was received successfully.

Can I add or correct FFL details after the order is placed?

Yes. You can edit the FFL data in Flxpoint, and the system re-checks compliance before finalizing the shipment.

Back to Firearms & Tactical