Skip to main content

Configuring FastBound Settings

Once your FastBound account is connected, there are several additional settings to configure. These control how CloudFFL interacts with FastBound for auditing, webhooks, POS integration, and compliance product tracking.

Audit User

Every API call CloudFFL makes to FastBound includes an Audit User header. FastBound uses this to record who made each change in the audit trail — acquisitions, dispositions, and configuration updates all log this value.

Important: The Audit User must be the email address of a real FastBound user who has access to your FastBound account. This is not a free-text label — FastBound validates it against your account's user list. If the email does not match a valid user, API calls may fail or audit records may not be attributed correctly.
  1. Go to FastBound → Configuration → FastBound Accounts
  2. Open your active configuration
  3. Set the Audit User field to the email address of a FastBound user on your account (for example, [email protected])
  4. Click Save

This email will appear in FastBound's audit logs any time CloudFFL creates or updates a record. For ATF inspection purposes, it identifies which system or person initiated the action.

Tip: Many shops create a dedicated FastBound user (e.g., [email protected]) specifically for API access. This keeps CloudFFL's automated actions separate from individual employee actions in your FastBound audit trail.

Webhook Configuration

Webhooks are how FastBound sends information back to CloudFFL. The most important webhook is the 4473 completion event — when a customer's 4473 form is approved or denied in FastBound, the result is sent to CloudFFL automatically.

Webhook setup is a two-step process after activating your FastBound account:

  1. Click the Setup Standard Webhooks button on your FastBound configuration form. This creates the webhook configuration records in CloudFFL.
  2. Click the Sync Webhooks button to register the webhooks with your FastBound account. This tells FastBound where to send events.
  • The webhook endpoint is: /fastbound/4473_form_complete
  • You can view all received webhook events at FastBound → Configuration → Webhook History

Tip: Check the Webhook History periodically to make sure events are flowing. If you see no recent entries but have been processing 4473 forms, there may be a connection issue that your administrator needs to investigate.

POS Integration

If you sell firearms at the point of sale (POS), you need to link your POS configuration to FastBound:

  1. Go to Point of Sale → Configuration → Point of Sale (or your POS settings)
  2. Find the FastBound Account field
  3. Select your active FastBound configuration
  4. If you want POS sales to automatically commit dispositions when payment is collected, enable the Auto-Dispose on Payment option
  5. Click Save

Compliance Product Categories

Not every product you sell needs to go through FastBound. Only firearms and other regulated items require compliance tracking. You control this through product categories:

  1. Go to Inventory → Configuration → Product Categories
  2. Open the category for your firearms (for example, "Handguns" or "Long Guns")
  3. Check the Requires FFL Compliance flag
  4. Click Save

Any product in a compliance-flagged category will automatically trigger FastBound workflows when acquired or sold. Products in non-compliance categories (like ammunition, holsters, or cleaning kits) will not.

Tip: Individual products can also have the Requires FFL Compliance flag set directly on the product form, independent of the category. This is useful for one-off items that need compliance tracking but do not belong to a compliance-flagged category.

Important: Make sure all your firearm product categories have the "Requires FFL Compliance" flag enabled. If this flag is missing, firearms in that category will be sold without creating FastBound records, which means missing bound book entries — a compliance violation.

Back to top