ACE Ocean Manifest Release 3: October 2026 Guide

ACE Manifest Modernization reaches another important milestone on October 24, 2026, when Release 3-Ocean, identified as INT-062, is scheduled for production deployment. Although no direct changes to the ACE user experience or Electronic Data Interchange behavior are expected, ocean carriers, NVOCCs, brokers, and software developers should still prepare carefully.

What ACE Manifest Modernization Release 3 Changes

A Back-End Migration for Ocean Transportation

CBP is modernizing the ocean, rail, and air manifest components of the Automated Commercial Environment over multiple releases. INT-062 addresses the ocean mode through a technical migration of back-end functionality.

This distinction is important. The release is not positioned as a new ocean manifest workflow, a redesigned user interface, or a change to the way trade participants structure their EDI transmissions. Its primary purpose is to move underlying ocean manifest functionality within the modernized ACE environment.

For operational teams, that generally means existing procedures should remain in place unless CBP communicates additional requirements. Ocean carriers and NVOCCs should not need to redesign filing processes solely because of INT-062. Brokers should likewise avoid treating the deployment as a new data requirement or cargo release policy.

No Direct User Experience or EDI Behavior Change

INT-062 is not expected to directly affect the ACE user experience or EDI behavior. Users should generally see the same workflows, while systems should continue sending transmissions and receiving responses through established interfaces.

However, the absence of an intended behavior change does not eliminate implementation risk. Back-end migrations can expose assumptions in integrations, response handling, monitoring, or error-management processes. A technically valid transmission may continue to behave as expected, but developers should confirm that acknowledgments and other responses remain compatible with their applications.

The correct compliance posture is therefore measured rather than disruptive. Organizations do not need to invent new procedures, but they should validate existing ones. Testing, stakeholder communication, and production monitoring can provide that assurance without creating unnecessary operational change.

How to Use ACE CERT Before October 24

Validate Representative Ocean Manifest Transmissions

The ocean portion of Release 3 is available in the ACE certification environment, commonly called ACE CERT. Trade software developers may send transmissions through CERT and confirm that the resulting responses match expected behavior before the scheduled production deployment.

Testing should focus on representative workflows rather than an unnecessarily broad system redesign. Developers should select transactions that reflect normal ocean manifest activity, including common message paths and any scenarios that are particularly important to their customers. The objective is to verify continuity across the migrated back-end functionality.

A practical CERT test cycle should generally include:

• Sending representative ocean manifest transmissions through established interfaces.
• Confirming that expected acknowledgments and responses are received.
• Comparing CERT results with existing application expectations.
• Reviewing parser, mapping, logging, and exception-handling behavior.
• Recording test dates, inputs, outcomes, and unresolved questions.
• Retesting any scenario that produces an unexpected response.

Testing results should be evaluated in context. Not every difference necessarily indicates an INT-062 problem, particularly if test data, CERT availability, or environmental configuration differs from production. Developers should isolate variables before escalating an issue.

Coordinate Questions Through the Appropriate Channel

Technical questions should generally be directed to the organization’s assigned Client Representative. This is particularly appropriate when a developer encounters unexpected transmission behavior, response handling questions, or an issue that appears connected to the certification environment.

Other Cargo Control and Release questions may be sent to CREM@cbp.dhs.gov. Separating technical integration questions from broader cargo control questions can help organizations obtain more relevant guidance and avoid delays.

CERT testing is available before October 24, so teams should avoid concentrating all validation in the final days before deployment. Early testing leaves time to reproduce results, coordinate with customers, and determine whether an issue belongs to the filer’s software, the test environment, or the modernized back-end service.

Production Readiness for Ocean Trade Stakeholders

Recent Developments at a Glance

The key operational facts are straightforward:

• INT-062 covers a back-end technical migration for ocean manifest functionality.
• The release is currently available for developer testing in ACE CERT.
• No direct change to ACE user experience or EDI behavior is expected.
• Production deployment is scheduled for October 24, 2026.
• The October date remains a scheduled deployment until production implementation is confirmed.

These points support a readiness plan centered on verification and monitoring, not wholesale process change.

Assign Responsibilities Across the Filing Chain

Software vendors should lead transmission testing, response validation, and technical issue triage. They should also communicate clearly with customers about what has been tested and whether any action is required before the production date.

Ocean carriers and NVOCCs should confirm that their technology providers are aware of INT-062 and have evaluated the CERT opportunity. Internal teams should identify critical manifest workflows and verify that escalation contacts are current. Organizations using multiple platforms or service providers may need to confirm readiness separately for each connection.

Customs brokers may not control the carrier’s manifest transmission, but they remain affected by cargo data quality, release visibility, and downstream exceptions. Brokerage operations should know the deployment date, monitor ocean shipments after implementation, and distinguish manifest-related issues from entry filing problems.

Prepare a Focused Cutover Plan

A proportionate cutover plan should identify technical owners, operational contacts, affected customers, and escalation routes. Teams should preserve relevant transmission logs and monitor response patterns closely following deployment.

Organizations should not assume that every production issue occurring on or after October 24 is caused by INT-062. A disciplined triage process should compare affected and unaffected transactions, identify common characteristics, and determine whether the issue is reproducible. That approach helps technical teams escalate credible findings without creating unnecessary disruption for cargo operations or brokerage personnel.

Frequently Asked Questions

What Is ACE Manifest Modernization Release 3-Ocean?

Release 3-Ocean, or INT-062, is a technical migration of back-end ACE manifest functionality for the ocean mode of transportation. It is part of a broader, multi-release modernization of ACE ocean, rail, and air manifest systems.

When Is INT-062 Scheduled for Production?

INT-062 is scheduled to deploy to ACE production on October 24, 2026. Trade participants should treat that date as the current production target and monitor normal operational communications for confirmation or scheduling changes.

Will INT-062 Change Ocean Manifest EDI Requirements?

No direct effect on EDI behavior is expected from this portion of Release 3. Organizations should generally continue using their established transmission processes while validating that expected responses remain consistent.

Do Ocean Carriers and NVOCCs Need to Test?

Testing is not described as a new filing obligation, but it is a prudent readiness measure. Carriers and NVOCCs should coordinate with their software developers or service providers to determine whether representative ocean transmissions have been validated in CERT.

What Should Developers Test in ACE CERT?

Developers should send representative transmissions and confirm expected responses. Testing should generally cover important customer workflows, application parsing, message handling, logging, and exception processes without assuming that INT-062 introduces new transaction requirements.

Who Should Receive Technical Questions?

Technical questions should be directed to the organization’s assigned Client Representative. Other Cargo Control and Release questions may be sent to CREM@cbp.dhs.gov. Teams should document the relevant test scenario before requesting assistance.

How Stable Software Can Help

Technology Built for Customs Brokers

ACE modernization reinforces the importance of controlled testing, clear ownership, and dependable software across customs operations. Stable Software develops technology for customs brokers, including DrawbackAI, duty drawback software that brokers can white-label for importer clients and use to file under their own filer codes.

DrawbackAI is offered through a flat software license, and Stable Software never takes a percentage of the importer’s refund. Brokers evaluating how specialized software can support their broader technology strategy can learn more about Stable Software’s approach on the customs broker solutions page.

Resources