Questions to ask before switching FFL software

Record counts alone are not enough. Ask which totals will be compared, how open inventory will be checked against physical inventory, how dispositions will be sampled, how rejected rows are reported, who signs off, and whether the store receives an exception list.

Every system has manual steps. Paper forms may need scanning. The store may need to request exports, resolve bad source data, confirm distributor accounts, prepare hardware, send required notices, or finish in-progress transactions in the old system.

Ask for a responsibility list with three columns: store, current vendor, and new vendor. Put an owner and due date beside every task. "We help with onboarding" should become a sequence of named actions. Review the e4473 onboarding process as an example of what to clarify.

Do not evaluate the 4473, point of sale, background check, inventory, and A&D Book as separate demo sections. Ask the vendor to run one realistic transaction through all of them.

• Where do buyer and firearm details first enter?
• Which fields carry forward, and where does staff re-key information?
• When does the A&D Book update, and how is status shown?
• How are corrections and exceptions handled?
• What can a manager see, and how is the completed record retrieved later?

Then request a less tidy example such as a delay, correction, return to the process, or another exception common to your store. Normal-path demos show polish. Exception demos show whether the process survives a busy Saturday.

Ask what the software checks, when it checks it, whether unresolved items stay visible, and what still depends on store policy and training. No software removes the licensee's responsibility. The question is whether the system makes the correct path clear and preserves a record of what happened.

Do not accept broad promises. Ask the vendor to demonstrate the control and explain its limit.

• Will historical data load before go-live?
• How are transactions in progress handled?
• Is there a freeze period for the old system?
• What happens if validation takes longer than expected?
• Who is present for the first live transactions?
• How will the team avoid the store's busiest period?

A cutover needs a go or no-go decision and a contingency path. Confidence comes from knowing what the team will do if something is late, not from assuming nothing will be.

Counter staff, managers, owners, and recordkeeping staff do not need identical training. Ask whether instruction uses your transaction types, whether staff can practice before go-live, what documentation remains afterward, how new employees are trained, and how competency is checked.

Attendance is not the same as readiness. Also ask who updates training when forms, requirements, or product processes change.

When one vendor provides the point of sale and another provides compliance software, support boundaries matter. If a record fails to pass between them, will the owner need to open two tickets and explain the same transaction twice?

• Who is the first contact, and which support hours and channels apply?
• What information should staff collect during a live counter issue?
• Who owns an integration problem?
• When does the case move to a specialist?
• How is the resolution documented?

Ask the same questions when one provider owns the full process. A single vendor relationship helps only when accountability is clear.

Compare the same boundary across vendors: point of sale, electronic 4473, A&D Book, storage, integrations, payment or hardware requirements, onboarding, migration, training, support, and usage-based charges. Add your internal work for export preparation, cleanup, scanning, reconciliation, training, and reduced capacity during cutover.

Do not rely on a public list price or verbal estimate. Ask for a store-specific written proposal that identifies assumptions, optional items, and what may change later. The electronic 4473 cost guide provides a consistent comparison boundary.

Ask the vendor to retrieve an older record during the demo. Confirm search, permissions, access logging, backups, and outage procedures. Verify current electronic-storage and notice requirements with authoritative guidance for your store's situation.

• Can the store export records in a usable format?
• Which fields and attachments are included?
• Is there a fee or notice period, and how long does export take?
• What access remains after termination?
• How is deletion handled while retention duties still apply?

A reference is most useful when the operating context matches. Ask for a store with similar transfer volume, locations, transaction types, and starting system. Ask what took more work than expected, what did not migrate cleanly, how the first week affected the counter, which manual steps remain, and what the store would do differently.

The goal is not a perfect endorsement. It is a realistic preview.

A useful evaluation produces a record inventory, sample-export review, validation method, responsibility list, training plan by role, cutover and contingency plan, support escalation path, complete written cost, and export terms. If those items remain vague, the decision is not ready.

Use the free FFL Software Switching Planner to capture the answers. A polished demo shows what software does. A switching plan shows whether the vendor understands what your store is putting at risk.