UTF-8 only
Invalid byte sequences are rejected with an export-as-UTF-8 recovery path. UTF-8 with BOM is accepted.
Format register ยท last tested August 11, 2026
Supported Means Tested.
A vendor name alone is not a source profile. This register separates the generic CSV workflow we can reproduce from named formats that still need representative export fixtures.
Profile register
One supported route. No invented compatibility.
Use Generic CSV for any reasonable UTF-8 export and inspect the mapping yourself.
| Profile | Status | Version tested | Required columns | Evidence | Known limitations | Last tested |
|---|---|---|---|---|---|---|
| Generic CSV | SUPPORTED | Rule set 2026.08.1 | Manual mapping to manufacturer, model, serial, type, caliber/gauge, acquisition date, and acquired from | Ten synthetic fixture classes, deterministic parser/mapping/rule tests, browser QA, and performance benchmarks | Does not infer proprietary semantics; UTF-8 and one header row required | August 11, 2026 |
| FastBound export | NOT YET VERIFIED | None | Not published | No representative vendor export fixture in this release | Use Generic CSV; verify every field and transformation | Not tested |
| FFL Boss export | NOT YET VERIFIED | None | Not published | No representative vendor export fixture in this release | Use Generic CSV; verify every field and transformation | Not tested |
| Orchid eBound export | NOT YET VERIFIED | None | Not published | No representative vendor export fixture in this release | Use Generic CSV; verify every field and transformation | Not tested |
| Bravo Store Systems export | NOT YET VERIFIED | None | Not published | No representative vendor export fixture in this release | Use Generic CSV; verify every field and transformation | Not tested |
Profile promotion rule: a named format becomes supported only after a representative export/version is documented, transformed fields are explicit, synthetic or permission-safe fixtures cover edge cases, and deterministic results pass in both code and browser QA.
Generic target fields
Map meaning, not column order.
The source header may use any reasonable name. These are the target fields the current BoundStack record workflow understands.
ManufacturerRequired
ImporterOptional
ModelRequired for this workflow
Serial numberRequired
TypeRequired
Caliber / gaugeRequired
Acquisition dateRequired
Acquired fromRequired
Source FFL numberOptional, review
Disposition dateOptional unless disposed
Disposed toOptional unless disposed
Recipient FFL numberOptional, review
Record statusOptional
NotesOptional, redacted in report
Current safety envelope
Known limits are part of support.
Limits are resource controls, not recommendations about how a dealer should divide records.
Conventional table
One header row, at most 120 columns, consistent row width, and standard quoted CSV fields.
10 MiB / 100,000 rows
The browser safety caps are enforced and tied to the measured synthetic browser run in this release.
Have a CSV that is not on this list?
Use Generic CSV and inspect every target assignment. Do not infer vendor support from a successful parse.