FFL Transfer Tracking and Notification Workflow
BoundStack tracks an incoming transfer from expected arrival through pickup and stores buyer, firearm, source, status, and notification context. Message delivery is separate from drafting and depends on a configured SMS provider.
Best Fit
Independent dealers who need a visible transfer queue and a deliberate notification workflow.
Evaluation Rule
Test this workflow with representative records and current requirements. Product output is evidence to review, not a legal conclusion.
Implemented Scope
- Create transfer intake records with buyer and firearm details.
- Mark arrival and prepare a notification message for dealer review.
- Record sent or failed delivery only after the SMS provider returns a result.
- Track expected, arrived, notified, ready-for-pickup, picked-up, and cancelled states.
Delivery is provider-dependent
When SMS is not configured, BoundStack returns an error and does not mark the buyer as notified. A saved message is a draft, not proof of delivery. Dealers should verify the recipient, consent, provider response, and final transfer status.
Test the state transitions
Create a test transfer, mark it arrived, save a message, simulate an unavailable provider, and confirm that the status remains failed or ready for review. Only a real provider response should produce a sent state.
FAQ
Does BoundStack always send an SMS?
No. SMS delivery requires a configured provider. Without one, the request fails and the transfer is not marked notified.
Can I track a transfer without SMS?
Yes. Intake, arrival, pickup, and manually managed status fields do not require SMS delivery.
Related Guides
Evaluate BoundStack Conservatively
Review the Free and Pro scope, create a Free account, and test only with records suitable for product evaluation.
Review Plans