27 CFR § 478.125
The federal regulation that defines what an A&D record must contain. BoundPro's ledger schema matches the required fields column-for-column.
We're building modern compliance software for Federal Firearms Licensees — fast, clean, and designed around the way you actually run your gun shop.
Most A and D Software for FFLs was designed before the iPhone. The bound book gets done, but the workflow around it — finding a record, completing a 4473 between customers at the counter, catching a 3310.4 deadline before it lapses, exporting an inspection pack at 8 PM the night before ATF shows up — feels like it was bolted on after the fact.
BoundPro is the version that wasn't bolted on. We started with the actual regulation (27 CFR § 478.125 and the ATF rulings that authorize electronic bound books), worked outward to the workflows real FFLs run dozens of times a day, and built the UI for the device the back-counter clerk actually has in their hand — usually a phone or a tired laptop, not a dedicated kiosk.
Honest claims, cited. Every feature comparison we make is sourced. Every legal claim about the ATF references the actual regulation. We'll never claim a feature we haven't shipped.
Your data is yours. Full CSV and PDF export at any time, no friction. If you decide BoundPro isn't for you, your bound book leaves with you in one click.
Real humans. Support is staffed by people who can read 27 CFR fluently and have actually completed a 4473 themselves. No tier-1 script readers.
Stay independent. BoundPro is not affiliated with the ATF, FastBound, Orchid, Easybound, AIM, or Silencer Shop. We don't take vendor money, we don't sell customer data, and our pricing isn't engineered to push you to call sales.
BoundPro was designed against the text of 27 CFR § 478.125 and ATF Ruling 2016-1 (the rulings that authorize cloud-based electronic bound books). Every column, every status, every retention rule maps to specific regulatory language.
The federal regulation that defines what an A&D record must contain. BoundPro's ledger schema matches the required fields column-for-column.
Authorizes cloud-based electronic bound books with specific safeguards. BoundPro's hash chain, immutable audit log, and US data hosting are designed to those exact requirements.
The multiple-handgun-sale (3310.4) and border-state long-gun (3310.12) reporting requirements. BoundPro's auto-detection runs against every transaction in real time.
If you're evaluating BoundPro for a multi-store rollout or a Class III shop with a non-trivial migration, drop us a line — a real human (probably a co-founder) will reply.