Back to resources

How to Evaluate FTZ Software in 2026: A Buyer's Checklist

Evaluate FTZ software on five things: which CBP filings it prepares and transmits, how it gets data from your ERP and WMS, how completely it controls inventory and zone status, what its automation actually does, and how it proves your opening balances before you switch. Ask every vendor the same questions and ask to see your own data, not a demo dataset.

Get a recovery estimate

1. Filing coverage

List the transactions your zone files and ask the vendor to state, for each, whether the software prepares it, transmits it to CBP directly, or relies on a partner.

TransactionWhat to confirm
E-214 admissionDrafting, transmission, and CBP response handling
3461 weekly estimateCoverage monitoring and supplemental estimates
7501 Type 06 entry summaryLine grouping, duty and fee calculation
7512 in-bond or zone-to-zone transferPreparation and transmission
Annual reconciliation and FTZ Board annual reportReport generation from the ledger

Ask whether the vendor is listed for the relevant ABI transaction sets, and for which environments.

2. Data integration

Most FTZ effort goes into getting data in, not into the filing itself.

  • Which ERP and WMS sources are supported, and in what form: extracts, files, APIs, or documents?
  • Who builds and maintains the mapping: your IT team, a consultant, or the vendor?
  • What happens when a required field is missing or two sources disagree?
  • Can every value in a filing be traced back to the source record it came from?

3. Inventory control and zone status

  • Does the system keep an ICRS that meets 19 CFR 146.21 through 146.26 on its own, or does it depend on another system of record?
  • Is zone status held per inventory layer through every movement?
  • Which inventory methods are supported, such as FIFO or specific identification?
  • Does it support manufacturing, including inverted-tariff treatment under production authority?
  • How are corrections recorded: overwrites, or revisions with history?

4. Automation and AI

"AI-powered" means different things. Ask what runs without a person and what waits for one.

  • What does the system do on its own each day: intake, matching, checks, reconciliation, drafting?
  • What does it flag, and does each flag include the evidence and a proposed fix?
  • Which decisions always require an authorized person, such as status elections and filings?
  • Are duty and fee amounts computed by deterministic rules, with AI limited to preparing and explaining?

Ready to find out what you've been missing? Book a call with the Pax team.

Talk to an expert

5. Migration and proof

  • How are opening balances, layers, and statuses loaded from your current system?
  • Can the vendor run in parallel with your current process and compare outputs before cutover?
  • What does migration cost, and who does the work?

6. Analytics and reporting

  • Can you see duty deferred on inventory, liability if all inventory were withdrawn today, and savings by lever?
  • Are custom reports available without a support ticket?

A simple scoring sheet

Score each vendor from 1 to 5 on each area, weighted to your operation.

AreaWeight for a distribution zoneWeight for a manufacturing zone
Filing coverageHighHigh
Data integrationHighHigh
Inventory and zone statusMediumHigh
Automation and AIMediumMedium
Migration and proofHighHigh
AnalyticsMediumMedium

See how Pax answers

Pax FTZ is AI-native foreign-trade zone software. It works from your existing ERP, WMS, and broker data, reconciles inventory, flags conflicts between sources, and drafts E-214 admissions and weekly entries with every field traced to its source. Migration from most FTZ systems is complimentary and validated before go-live. For background, see What is FTZ software?

Ready to find out what you've been missing? Book a call with the Pax team.

Talk to an expert

More resources like this one