Best AMS Filing Software in 2026: 8 Tools Compared

When an AMS filing fails, and what CBP does about it

An AMS filing is not paperwork you can fix later. It is a timed transmission, and the penalties for getting it wrong are written into the regulation.

Late or missing ocean AMS. Cargo data has to reach CBP at least 24 hours before it is loaded at the foreign port. Miss that window and CBP can issue a do-not-load message, assess liquidated damages against the carrier or NVOCC bond, and hold the container on arrival. The forwarder that caused the delay usually eats the cost.

Air AMS and ACAS gaps. Air Cargo Advance Screening data must be sent before wheels-up at the foreign airport on short flights, or at least four hours before US arrival on longer ones. An ACAS referral can ground a shipment for screening. Repeated failures put a filer’s status at risk.

Rejections and change requests. Most day-to-day pain is not a total miss. It is a CBP rejection for a bad SCAC, a bill mismatch, or a weight discrepancy, and a filer racing to correct and refile inside the deadline. Software that surfaces the rejection clearly and lets you amend on the same record is worth more than any feature list.

Air AMS versus ocean AMS, filed under different rules

Buyers often assume one AMS tool covers both modes. Some do. Many are strong in one and thin in the other, so match the tool to your actual traffic.

Ocean AMS is a manifest filing from the carrier or NVOCC, keyed off the master and house bills, transmitted through ACE well before loading. The data set is stable and the timing is predictable. Most forwarding suites in this list handle ocean AMS natively, including CargoEZ, CargoWise, Magaya, and GoFreight.

Air AMS is bound up with ACAS, a security-screening program with tighter, flight-length-dependent timing and a different message format. It rewards a filer with high-volume airline connectivity and fast turnaround on CBP responses. Descartes and CustomsCity are built for this; the general forwarding suites cover it to a shallower degree.

If you run both, confirm during the trial that a single platform files each mode to the depth you need, or plan to run a dedicated air filer alongside your ocean system. Do not take a demo checkmark as proof of parity.

Native filing, integrated bridge, or service bureau

There are three ways to get manifest data to CBP, and the right one depends on your volume and whether you want EDI staff.

Native filing means AMS lives inside your forwarding platform and pulls straight from the shipment file. CargoEZ, CargoWise, Magaya, and GoFreight work this way. The upside is no rekeying and rejections that land back on the file. The downside is you are tied to that platform’s filing roadmap.

A standalone bridge is a dedicated filer such as CustomsCity or Artemus that connects to your operations system by API or EDI. You get deeper filing features and mode coverage, at the cost of maintaining an integration and reconciling two systems.

A service bureau transmits on your behalf. CustomsCity’s service center, Descartes’ hosted option, and Info-X’s managed model all let a forwarder file without building EDI. It is the fastest way to start and the easiest to scale down, though per-filing cost and turnaround need to be fixed in the contract.

What to run through an AMS filing trial

Test with your own bills, your own lanes, and a deliberate error or two. A clean demo file proves nothing.

One, file a real ocean AMS end to end. Take an actual master and house bill set, transmit to the ACE test environment, and confirm the SCAC, bond, and bill structure map without rework. Time how long the CBP response takes to appear.

Two, force a rejection. Submit a filing with a known bad element, a wrong weight or a duplicate bill, and watch how the system reports the rejection. Check whether you amend on the same record and how many clicks the refile takes.

Three, test air AMS with ACAS if you fly. Confirm the platform sends ACAS data in the correct format and timing for both short and long flights, and check airline coverage on your actual routes.

Four, run an ISF alongside. File an ISF-10 that shares data with the AMS filing and confirm the two stay consistent without double entry.

Five, check the service-bureau path. If you may outsource, get a written per-filing price, a turnaround commitment, and an escalation contact for a filing stuck near deadline.

Six, pull the audit trail. Export a month of filings with timestamps, statuses, and amendments. You will need this the first time CBP asks why a filing was late.

Switching AMS filing providers without a gap in coverage

Changing filers is riskier than changing most software because a missed transmission window has a hard cost. Plan the cutover around live shipments.

Run parallel for two to four weeks. File through both the old and new systems for a set of shipments and reconcile CBP responses line by line. Do not cut over until the new system matches the old on every filing in that window.

Move your SCAC and bond details early. Confirm the new provider has your filer code, SCAC, and continuous bond correctly set up in the ACE production environment before the first real filing, not on the day.

Keep the old system read-only for a year. CBP inquiries and liquidated-damages claims can arrive months later. You need access to the original filings and their timestamps.

Rebuild integrations before, not during. If AMS was fed by EDI from your TMS, have the new feed built and tested against ACE certification before the parallel run starts.

Brief operations staff on the new rejection workflow. The single biggest source of a post-migration miss is a filer who does not recognize a rejection message in the new interface and assumes the filing went through.

Final pick by filer profile

• Small US forwarder or NVOCC wanting filing inside operations: CargoEZ, for air and ocean AMS, ACAS, and ISF on the same platform that runs the file.
• Mid-market US forwarder on cloud software: GoFreight, for the 4.8/5 G2 record and AMS and ISF pulled from the shipment file, with a fast go-live.
• SMB forwarder with a bonded or CFS warehouse: Magaya, so manifest, in-bond, and warehouse data come from one set of records.
• High-volume air carrier, GSA, or large NVOCC: Descartes Global Logistics Network, for carrier-grade air AMS and ACAS transmission at scale.
• Mixed-mode filer wanting one standalone tool: CustomsCity, for ACE air, ocean, and highway eManifest plus a service-center fallback.
• Multinational forwarder standardizing one system: CargoWise, accepting the long implementation and the 2025 repricing.
• Cost-conscious shop wanting a dedicated, proven filer: Artemus Group, for web-based AMS filing with full EDI and a record going back to 1999.
• Forwarder that would rather outsource filing: Info-X, for a managed AMS and ISF service on an integrated platform.

How we research AMS filing platforms

CEOPickz does not accept paid placements in rankings. Order reflects a weighted view of filing depth across air and ocean, ACAS capability, validation and rejection handling, connectivity model, third-party review evidence where it exists, and pricing accessibility.

Where a vendor carries a G2 or Capterra score, it was read from the live product page in August 2026 and is linked in that tool’s card. Several dedicated filing vendors carry no aggregate rating; those cards say so plainly and lean on product documentation and CBP program scope instead. Pricing signals were checked on the same date, with ranges noted where vendors publish no numbers.

This comparison does not include tools we have not researched. The excluded and honorable mention lists record what we evaluated and why each did not make the primary eight. Vendor blogs and vendor-run comparison pages were not treated as neutral sources.

For corrections, vendor disputes, or feedback, email hello@ceopickz.com . Pricing and review data are verified each time this page is updated; the next scheduled refresh is November 2026.