How FastBound Works with CloudFFL

How FastBound Works with CloudFFL

FastBound is not a separate system you have to switch to. It is integrated directly into CloudFFL through a set of Odoo modules that connect to the FastBound cloud API. Here is how the pieces fit together.

The Connection

FastBound connects to CloudFFL through a secure API. Your administrator configures the connection once (entering your FastBound API Key and Account ID), and from that point on, data flows automatically between the two systems. The configuration lives at FastBound → Configuration → FastBound Accounts.

What Happens Automatically

• Receiving a Purchase Order with firearms → When you validate the receipt, CloudFFL automatically creates an acquisition in FastBound. The serial numbers, manufacturer, model, caliber, and type are all sent over.
• Selling a firearm → When a sales order includes compliance items, CloudFFL creates a disposition in FastBound and triggers the 4473 workflow.
• 4473 completion → When the customer's 4473 is approved in FastBound, a webhook fires back to CloudFFL. The system automatically downloads the 4473 PDF and attaches it to the sales order.
• Serial number tracking → Every firearm's serial number is tracked in Odoo's stock system with a linked FastBound ID, item number, and status (acquired, disposed).

The Module Architecture

CloudFFL's FastBound integration is built from four modules that work together:

Module	What It Handles
fastbound_core	API connection, configuration, partner sync, SmartList reference data, webhooks
fastbound_acquisition	PO receipts, dealer transfers in, customer trade-ins, walk-in direct buys, serial number tracking
fastbound_disposition	Sales with 4473 tracking, NFA transfers, theft/loss reporting, POS integration, trade credits
fastbound_reporting	Stock reconciliation, serial audits, product reports

How Products Trigger Compliance

Not every product in your shop requires FastBound tracking — ammunition, accessories, and apparel do not need bound book entries. Only products in a category marked with the "Requires Compliance" flag will trigger FastBound workflows. When you sell or receive a product in a compliance category, CloudFFL knows to create the appropriate FastBound records.

Reference Data Sync

FastBound maintains master lists (called SmartLists) of manufacturers, calibers, item types, conditions, and more. CloudFFL syncs these lists so that when you create products or log transactions, you are choosing from the same standardized values that FastBound uses. This prevents mismatches and ensures your records are consistent.

The Big Picture

Here is the typical flow for a firearm through your shop:

1. Order — You create a Purchase Order for firearms from a distributor
2. Receive — You validate the receipt, entering serial numbers. CloudFFL creates the FastBound acquisition.
3. Stock — The firearm sits in your inventory, tracked by serial number in both Odoo and FastBound
4. Sell — A customer wants to buy. You create a Sales Order. CloudFFL creates a FastBound disposition.
5. 4473 — Customer completes the ATF Form 4473. FastBound processes it and sends the result back via webhook.
6. Transfer — NICS approved, you hand the firearm to the customer. The disposition is complete.

All of this is tracked, recorded, and searchable — exactly what the ATF expects from a compliant FFL dealer.