CargoWise vs Magaya: 2 ACE AES Filing Paths 2026

CargoWise vs Magaya for ACE, AES, and 7501 filing is a forwarder operating-system choice, not a visibility-tower choice. Automated Commercial Environment (ACE) is CBP’s single window for import and export processing. The Automated Export System (AES) is how filers send Electronic Export Information. Form 7501 is the Entry Summary CBP uses to collect duties and statistics on imports.

A one-sentence definition: ACE/AES/7501 filing software is the forwarder or broker system that builds, transmits, and stores those customs messages so a shipment can clear without a side spreadsheet.

US logistics industry costs: $2.3T (8% of GDP, 2024) according to the Council of Supply Chain Management Professionals 35th Annual State of Logistics Report (2024). That is the book these two systems sit on. This page compares CargoWise and Magaya on filing depth, implementation, and TCO, then shows where a workflow hop belongs after the OS accepts a status. Detention and demurrage reasonableness under OSRA 2022 is a different recipe; see detention and demurrage charges. No vendor paid for inclusion.

TL;DR: CargoWise is the enterprise forwarder OS with deep customs modules and a longer implementation. Magaya is the mid-market forwarder OS with AES/ACE paths that a smaller brokerage can stand up without a global SI. Neither one is a control-tower. Pick the OS that already owns the shipment, then decide whether rejected AES lines and 7501 holds need a human-review hop.

ACE, AES, and Form 7501 are three jobs

ACE is the import and export processing system CBP requires trade to use as the Single Window, according to U.S. Customs and Border Protection (2026). AES is the export filing path for Electronic Export Information; Census still documents AESDirect for filers who transmit EEI, according to the U.S. Census Bureau (2026). Form 7501 is the Entry Summary on CBP’s entry-summary program page. One platform that “does customs” may still be weak on one of those three.

Related work that is not this page: freight claims, freight audit, and logistics lead management.

Who should read this forwarder OS comparison

This page is for a US freight forwarder or customs brokerage ops lead whose system of record is already CargoWise or Magaya (or who is choosing between them) and whose pain is AES rejects, ACE holds, and 7501 status that never reach billing. You already file. You are not asking what an ITN is.

Red flags: you are a shipper with no filer bond and a forwarder who already files; you run a visibility tower and think that is a customs OS; you have no licensed broker on staff and no NVOCC operation. When NOT to use a new OS: if your current tenant already files ACE/AES/7501 cleanly and the only gap is emailing a hold to ops.

How we scored CargoWise vs Magaya

We weighted customs filing depth, forwarder OS completeness, implementation, and public price. We did not run a private CATAIR certification lab. G2 hosts buyer reviews for both products; use them as sentiment, not as a filing-accuracy score. CargoWise reviews live on G2 (2026). Magaya reviews live on G2 (2026).

OSRA 2022 detention and demurrage reasonableness is already live as a separate G recipe and is not this page’s payload, according to the Federal Maritime Commission OSRA 2022 page (2022). Do not buy CargoWise or Magaya because you saw a demurrage slide.

Filing depth, TCO, and orchestration numbers

Both vendors are contact-vendor for list price as of 2026-09-06. The USTA column is public self-serve from US Tech Automations pricing fetched the same day.

CargoWise

Best fit: multi-branch forwarders and brokers who need a global OS, eAdaptor integrations, and customs modules in the same tenant as ocean/air/road. Limitations: cost, implementation length, and a learning curve that shows up in G2 qualitative reviews. Implementation: plan in months, not a weekend. Primary evidence: WiseTech public materials plus G2 reviews. Disqualifier: a 15-person NVOCC that only needs AES and a house bill should not buy an enterprise OS to “be ready.”

Magaya

Best fit: mid-market forwarders who want warehouse, cargo, and customs in a more approachable OS. Limitations: global multi-entity depth and some enterprise customs edge cases; confirm ACE/7501 in your exact license. Implementation: typically shorter than CargoWise for a single-country brokerage. Primary evidence: Magaya public materials plus G2 reviews. Disqualifier: if you already live in CargoWise and the only gap is a hold notification, switching OS is the expensive way to send a Slack.

After the entry summary is accepted

A 42-person forwarder that files 86 AES shipments a week at $4,200 average freight still misses the Friday 7501 hold when the status sits in the customs module. When CargoWise eAdaptor emits a DataContext.EventType update on those 86 rows, a proposed US Tech Automations recipe could match shipment_id to the AES ITN, flag any reject in under 15 minutes, and hold a packet for the licensed broker before ops invoices the customer. Prerequisites: eAdaptor or API credentials, a mapping of event types you actually receive, and a named broker who will not auto-clear a PGA hold. This is a configurable design, not a live deployment.

US Tech Automations will not transmit AES or 7501. On agentic workflows it would subscribe to OS events, diff status, and hold. Growth’s $372/mo, 5 flows, and 150 API calls per flow per day are sized for exception routing. Scale at $1,371/mo (10 flows, 500 API calls/flow/day, 90-day history) is the public SKU if hourly polling matters; it is still not a customs engine.

When NOT to use US Tech Automations: if CargoWise or Magaya already pages the broker on AES rejects and 7501 holds, stay in the OS. If a Make, Zapier, or n8n scenario already posts eAdaptor events to a queue with retries and a run history, keep it. Those tools can do error branches and audit logs; you own idempotency (one hold per shipment_id), who is allowed to clear a PGA flag, retention of EEI artifacts, and access control. A proposed US Tech Automations design would add a human hold and a written “this flow does not file.”

Decision checklist

• Does the OS transmit AES and return an ITN onto the same shipment record?

• Can a broker complete a 7501 without a second ABI desktop?

• Who owns a PGA hold at 6 p.m. Friday?

• Can you export 24 months of filings if you leave?

• Are you buying an OS, or did a salesperson demo a track-and-trace map?

A filing cutover sequence that does not miss the vessel

Do not migrate a forwarder OS during peak AES week. Sequence the work so Friday’s ITN still comes back onto the same house bill.

Week 0: inventory every AES filer ID, ACE portal account, and 7501 broker of record. If those three names do not match the people who will log into the new OS, stop.

Week 1–2: stand up a non-production tenant. Transmit one AES test, one ACE cargo-release test, and one 7501 test. The test is not “the demo looked nice.” The test is an ITN, a release, and an accepted summary on a dummy or low-risk file.

Week 3–4: map eAdaptor or Magaya API events you will actually consume. DataContext.EventType is only useful if you know which values mean reject, hold, and PGA. Write those values down. If the vendor cannot list them, you will automate silence.

Week 5–6: parallel-run. File production in the old OS. Mirror in the new OS without transmitting, or transmit a defined subset with a named broker watching both. Compare ITNs and 7501 numbers daily.

Week 7: cut AES first if export cut-offs are your pain, or 7501 first if duty is your pain. Do not cut both on the same Friday unless staffing is doubled.

Glossary:

• ACE: CBP’s Single Window for import/export processing.

• AES / EEI: export information transmitted for Census/CBP.

• ITN: Internal Transaction Number returned after AES accept.

• Form 7501: Entry Summary for duties and statistics.

• PGA: partner government agency data in the same ACE window.

• eAdaptor: CargoWise’s integration surface for shipment events.

US logistics costs: $2.3T (8% of GDP) according to CSCMP’s 35th Annual State of Logistics Report (2024). That number is why a missed AES on a $4,200 shipment is not a rounding error when it repeats 86 times a week.

CBP Single Window: ACE is 1 system on CBP’s ACE trade page. Buying a second “customs cloud” that does not transmit is how you get a visibility tower and still miss the 7501.

Common mistakes: treating Magaya as “CargoWise lite” without checking the customs module in your license; treating CargoWise as a track-and-trace buy; letting ops invoice before the ITN is on the file; putting PGA holds in email.

If you cannot name the broker on the hold, you are not ready for either OS or for a workflow hop.

Demo questions that catch a fake customs module

Ask the salesperson to share screen on a real tenant, not a slide. Then:

1. Create a house bill, transmit AES, and show the ITN on that same record within the session.

2. Open a 7501 in progress and show the broker of record, the duty amount, and the ACE status.

3. Trigger a PGA hold and show who is notified besides the customs clerk.

4. Export last month’s AES and 7501s as files you could give to a new OS.

5. Show the eAdaptor or API event for a reject, with the actual payload, not a marketing diagram.

If they cannot do (1) and (2) in one hour, you are buying an operations OS with a customs brochure. CargoWise will usually survive that test in an enterprise tenant that already files. Magaya will usually survive it in a mid-market tenant that already files. A brand-new empty demo tenant may not; insist on a reference tenant or a recorded production-like test.

Staffing still matters more than the logo. A licensed broker who will not log in at 6 p.m. Friday will miss PGA holds in either system. A junior ops person who invoices before the ITN is on the file will create the same refund fight in either system. The OS choice is real. It is not a substitute for a named filer.

Price conversations should convert contact-vendor quotes into a 12-month cash number: licenses, implementation, training weeks, and the cost of a parallel-run month. Do not compare CargoWise enterprise to Magaya mid-market on a per-user rumor. Convert to “what we will pay before the first production AES.” If that number is unclear, the RFP is not done.

Reference calls should include a brokerage that files your entry types, not a 3PL that only tracks containers. Ask how long their first production AES took after go-live, how many 7501s they still file in a sidecar, and whether PGA holds page anyone besides customs. If the reference cannot name a hold from last month, the OS is a brochure in their shop too.

Training is a cash line. CargoWise’s learning curve shows up in qualitative G2 comments as a cost even when the customs module is deep. Magaya’s gentler UI is not free if the customs license is an add-on you discover after signature. Put training weeks and module SKUs in the quote. Then decide. If both quotes are still fog, you are not buying this quarter; you are collecting decks.

Key Takeaways

• ACE, AES, and 7501 are three filing jobs inside one forwarder OS.

• CargoWise fits multi-branch enterprise; Magaya fits mid-market forwarder books.

• $2.3T US logistics cost is context, not a reason to over-buy.

• OSRA detention recipes are a different page.

• Orchestrate rejects and holds; do not build a second filer.

FAQs

Is CargoWise or Magaya better for AES 7501 automated export?

AES is export EEI; 7501 is an import entry summary. Ask each vendor to show both in your license, not on a slide. CargoWise is the more common enterprise answer; Magaya is the more common mid-market answer. Confirm ACE connectivity against CBP’s current ACE documentation.

Can a small forwarder skip both and use AESDirect?

Census still documents AESDirect, according to the U.S. Census Bureau (2026). A tiny filer volume can live there. The moment house bills, warehousing, and 7501 have to share a shipment_id, you are in OS territory.

Does Magaya replace a licensed customs broker?

No. Neither Magaya nor CargoWise is a license. Software transmits; a broker or qualified filer remains responsible.

How is this different from a visibility tower?

A visibility tower tracks milestones. A forwarder OS owns the shipment, the file, and the customs message. Buying a tower to file 7501 is the wrong SKU.

When does a workflow hop beat another OS module?

When the OS already filed and the next failure is human: AES reject not seen, 7501 hold not billed, PGA flag not in ops. US Tech Automations would configure trigger → match → hold. It would not apply for a filer bond.

If the OS is chosen and the remaining work is status hops, compare a scoped flow on the public pricing page. Bring one AES reject sample, one 7501 hold, and the broker who will sit on the hold.