FAQ

Frequently asked questions

• What is ImportPreflight?

  A web app that pre-screens product catalogs for HTS mapping and regulatory flags (FDA/IA, UFLPA, Entity List, etc.) and gives you a HOLD/REVIEW/CAUTION/CLEAR queue with exportable rationales. It is not an ACE filer (see About).

• Who is ImportPreflight for?

  Customs broker teams, compliance groups, and importers with large item masters who need a documented pass before the broker files — not a consumer app.

• Does ImportPreflight file entries with CBP?

  No. There is no link to ACE in the product. You export or copy results into your existing ABI workflow.

• Is ImportPreflight a replacement for my broker?

  No. It is a software pre-check. Licensed broker judgment and final filing are still on your side.

• How accurate is the classification?

  The app uses a deterministic, keyword-driven HTS mapping and rule engine with public datasets; it will miss edge cases a human would catch. Use output as a screening and documentation aid, not a final legal determination of classification.

• What regulatory sources does ImportPreflight check?

  In the current pipeline: FDA/Import Alert heuristics, UFLPA priority/entity path, BIS Entity List name matching, and a USITC-based HTS mapping, per the open-source rules and data folders in the repo. Exact refresh cadence depends on the operator runbooks.

• How fresh is the data?

  Bundled snapshots and CLI update commands in the repository describe the refresh process; the UI does not auto-fetch CBP in real time during analysis.

• How is my data secured?

  The product uses Supabase (Postgres + RLS) and a private file bucket. Server-side service keys never ship to the browser. For a formal program (SOC 2, etc.) talk to the operator; not claimed here.

• Can I export to CargoWise / Descartes?

  You get CSVs from the product UI. Import paths into CargoWise, Descartes, or your ABI are on your side — the exports are not vendor-specific file formats in Step 50.

• What happens when I dismiss a job?

  The row is marked dismissed and hidden from the default queue; it remains in the database. You can restore with bulk actions and filters, per the queue docs.

• Can my whole team use one log-in?

  No — each person should have their own account, using org membership and roles. Shared passwords defeat audit.

• How do I report a bug?

  Use Report issue in the in-app nav or the public /report-issue page. Include steps and, if you can, the job or SKU in question.