Pulling Pending 4473 Orders from FastBound
Sometimes a 4473 process is started in FastBound outside of CloudFFL — for example, if a disposition was created manually in FastBound, or if a customer began a 4473 on a previous visit before a Sales Order was created. The Pull Pending Orders wizard imports those open FastBound dispositions into CloudFFL so they can be tracked, completed, and invoiced through the standard workflow.
When to Use This
- You have open dispositions in FastBound that were created manually or outside the CloudFFL Sales Order process and you want to bring them into CloudFFL for tracking and invoicing.
- A customer has a pending 4473 from a previous interaction that you need to link to a new Sales Order.
- You are setting up CloudFFL for the first time and need to import existing open FastBound transactions so nothing falls through the cracks.
Step by Step
After Import
Once a disposition is linked to a Sales Order in CloudFFL:
- If the 4473 is already approved in FastBound, the Sales Order shows Is 4473 = Yes and the NTN is already populated. You can proceed directly to delivery and invoicing.
- If the 4473 is still pending, the Sales Order shows Pending 4473 status. Monitor the 4473 progress and wait for the NICS determination before delivering the firearm.
- Process delivery, create an invoice, and record payment through the standard Sales Order workflow once approved.
Use Pull Pending Orders as a daily check. Running this wizard at the start of each day catches any FastBound dispositions that were started outside the normal CloudFFL workflow — ensuring every open transaction has a matching Sales Order for invoicing and inventory tracking.
Check for duplicates before importing. Before pulling a disposition, verify that a Sales Order does not already exist for the same customer and firearm. Importing the same disposition twice creates duplicate records that will need to be cleaned up manually.