We build software for an industry generic POS wasn’t built for.
Firearm retail runs on federal compliance requirements that most retail software treats as an afterthought. We built FFL-POS to treat them as the starting point instead.
Most point-of-sale software is built for retail in general, then has compliance features bolted on afterward — a bound book plugin here, a hold workflow there. We started from the other direction: design the register, the storefront, and the bound book around the fact that a share of what you sell is a regulated transfer, not an ordinary sale.
That means a firearm can’t leave the store just because it’s been paid for. It means a bound book entry isn’t a separate spreadsheet — it’s the same record the register and the storefront already touched. And it means the requirements that come from how FFLs actually operate shape the software before counter-convenience does, not after.
A short list of things we won’t compromise on
Compliance comes first
The hold, the NICS check, and the bound book entry are enforced in the code itself — not left to staff remembering the rules.
You own your data
Everything runs on a standard PostgreSQL database — self-hosted or hosted for you. Export your inventory and bound book any time.
Boring technology, on purpose
We'd rather ship on tools that are well understood and easy to operate than chase whatever's trendy this year.
Built to run anywhere
Any modern browser, or installed as a standalone Windows app for the counter — your call, not ours.
Want to see it running on your own inventory?
We'll walk through the register, the storefront, and the bound book with your actual product mix — no obligation, no pressure.