eManifest Portal Outages: Why CBSA's Paper Fallback Still Decides Your Dwell Time

The CBSA’s eManifest and CERS portals went intermittent again on September 28. If you import regularly, you’ve seen this notice before. The portals come back up, the world moves on, and everyone forgets the System Outage Contingency Plan exists until the next time they can’t file a PARS release electronically at 4pm on a Friday.

The issue isn’t the outage itself. CBSA’s portal stability has improved since the CARM rollout chaos of 2024-2025. The issue is what happens in the gap between “portal is down” and “portal is back up” when your container is sitting at the Montreal sufferance warehouse and the free time clock is running.

What SOCP Actually Means

System Outage Contingency Plan procedures are the paper and fax fallback CBSA published for exactly this scenario. When the eManifest portal is unavailable, carriers and freight forwarders can’t file ACI (Advance Commercial Information) electronically. When CERS is down, exporters can’t submit export declarations. The CBSA’s SOCP documentation lays out the manual procedures: fax the cargo control document, phone the Commercial Client Services Unit, wait for manual processing.

In theory, SOCP keeps cargo moving. In practice, it’s slower, more error-prone, and burns through your free time at the port or warehouse faster than you’d expect. A PARS release that normally takes 15 minutes to file and clear electronically can stretch into hours when you’re faxing forms and waiting for a CBSA officer to manually input the data.

The dwell time spread matters. If your drayage appointment was booked for same-day pickup and the release doesn’t hit until after the driver is already dispatched, you’re paying detention on the container and rebooking the dray for the next available window. Montreal port drayage windows are tight. Miss yours, and you’re looking at next-day pickup at best.

Where Broker Quality Shows Up

Most customs brokers can file a PARS release when the system is working. The ones who’ve been doing this for a decade or more can file it when the system isn’t. SOCP procedures aren’t something you learn from a manual. You learn them by living through the last three portal outages, knowing which CBSA officers pick up the SOCP fax line fastest at which service areas, and having the carrier’s cargo control number and CCN reference ready before you call.

The other part that separates brokers: how fast they pivot. When the eManifest portal goes down mid-morning, do they sit there refreshing the page hoping it comes back, or do they immediately kick to SOCP and start the manual filing process? That two-hour decision window is the difference between same-day release and overnight dwell.

We’ve filed PARS releases on paper before. It’s slower, it requires more phone follow-up, and the error rate is higher because you’re re-keying data that would normally transmit electronically. But it works, and it keeps your container moving instead of sitting in a yard accruing per-diem charges.

The Export Side: CERS Outages

CERS (Canadian Export Reporting System) outages hit exporters the same way. If you’re shipping goods out of Canada and the CERS portal is unavailable, you can’t submit the export declaration electronically. CBSA’s SOCP for exports involves paper submission, but the carrier won’t move the goods until CBSA clears the shipment. Delayed export clearance means delayed loading, delayed departure, and missed sailing or flight cutoffs.

Export compliance is less visible than import compliance until something goes wrong. Miss a sailing because your export declaration couldn’t be filed? You’re rebooking the shipment, paying storage at the port, and explaining to your customer why their delivery date just slipped by a week.

If you’re running a regular export program, your freight forwarder should have SOCP procedures ready to go. Not “we’ll figure it out when it happens” ready. Actually ready: fax templates, CBSA contact lists, contingency timelines built into your shipping windows.

What’s Different This Time

The September 28 outage notice didn’t include an estimated time of resolution. That’s CBSA’s way of saying “we don’t know yet.” Some portal issues resolve in an hour. Some stretch into a full business day. The ones that hit late Friday afternoon and run into the weekend are the expensive ones.

If your shipment is time-sensitive, you plan around the possibility of an outage. Build buffer time into your drayage booking. Don’t schedule a warehouse cross-dock cutoff for the same day as your estimated arrival if the release requires PARS and eManifest filing. Give yourself a day of slack. The cost of an extra day of storage is lower than the cost of missing a delivery window because the CBSA portal was down when you needed to file.

The CARM Layer

CARM (CBSA Assessment and Revenue Management) added another dependency to the stack. The CAD (Commercial Accounting Declaration) filing process ties into CARM Client Portal access, your financial security on file, and the Release Prior to Payment bond math. When eManifest is down, you can fall back to SOCP for the release itself. When CARM Client Portal is down, you can’t adjust your RPP bond, you can’t view your K84 monthly statement, and you can’t file corrections to a CAD that needs amendment.

CBSA has mostly stabilized CARM portal uptime, but “mostly” isn’t the same as “always.” The compliance risk sits in the gap between what the system is supposed to do and what it actually does when you need it at 4:30pm on a short week.

How We Handle It

We keep SOCP procedure templates current for every CBSA service area we file into. When a portal outage notice hits, we don’t wait to see if it resolves. We shift to manual procedures immediately and keep the cargo moving. The fax line is slower than the portal, but it’s faster than sitting idle hoping the system comes back up before the free time window closes.

If your import volume is high enough that a four-hour portal outage translates into detention charges on three or four containers, you need a broker who treats SOCP as a live procedure, not a dusty appendix in the D-memo library. Portal outages will keep happening. CBSA’s infrastructure is better than it was two years ago, but it’s not bulletproof. The importers who come out fine are the ones who planned for it. Get in touch.

Source: CSCB