A PARS release is supposed to be boring. The broker files the release request, your driver drives, ACI eManifest talks to the release request behind the scenes, and the officer at the booth scans a barcode and waves the truck through. That's the version dispatch teams plan around. It's also the version that falls apart the moment a single character on the eManifest doesn't match the number the broker used — and when it falls apart, it doesn't fail quietly. It fails at the booth, in front of the driver, with the truck already stopped.
This post is not a general "what is PARS" primer. It's about the specific ways a PARS release gets rejected or scanned late at the CBSA primary booth, why those failures happen more often than carriers expect, and what a dispatch team can do — procedurally and with the right physical barcode labels — to keep a two-minute release from turning into a re-labeling exercise, a call to the broker, or a redirect to secondary.
1) PARS in one paragraph — and the match that has to hold
PARS stands for Pre-Arrival Review System. It's the CBSA program that lets a customs broker submit a release request for a commercial highway shipment before the truck physically arrives at the border, so the paperwork review can happen in advance instead of holding the driver at the booth while someone digs through a filing queue. The broker files the release request under a specific reference number, and separately, the carrier (or its service provider) transmits an ACI eManifest for the same trip. Those two filings are supposed to be linked by one thing: a shared number.
That shared number is a Cargo Control Number, or CCN — carrier code plus a unique sequence the carrier assigns. The CCN is what CBSA's systems use to connect "the broker says this shipment is cleared for release" with "the carrier says this truck is carrying that shipment." When both filings reference the identical CCN, CBSA's system links them automatically and the officer at primary sees a clean match. When they don't, the system has nothing to link — and a barcode that scans clean but points to a release CBSA can't find is functionally the same as no release at all.
2) Why PARS numbers get rejected: the exact-match problem
If you ask a CBSA-facing broker what causes the most PARS rejections, the answer is rarely "missing documents." It's a mismatch between the CCN on the ACI eManifest and the CCN the broker used on the release request. CBSA's systems look for an exact string match — not a "close enough" match — so small inconsistencies that a human would read past instantly break the automated link.
The small stuff that breaks the match
- A missing or extra character in the carrier-code prefix
- A stray space, dash, or hyphen that one filing has and the other doesn't
- A transposed digit in the sequence portion of the CCN
- Inconsistent inclusion (or omission) of the literal word "PARS" in the reference — one system expects it, the other doesn't have it
- Copy-paste artifacts: a trailing space, a line break, or an autocorrect change from a phone or tablet keyboard
None of these look serious on paper. Read side-by-side, a human catches "PARS123456789" versus "PARS 123456789" in about a second. CBSA's matching logic doesn't get that benefit of context — it's comparing strings, and a string comparison either matches or it doesn't. That's the entire mechanism behind the single most common PARS rejection, and it's also the one that's most preventable with a disciplined process.
3) Barcode print and scan quality: the failure mode nobody plans for
Even when the CCN is a perfect match on both filings, a PARS release can still stall at the booth if the barcode itself won't scan. Officers use handheld or fixed scanners to read the barcode and pull the matching record instantly — that's the entire point of a barcode instead of an officer keying in a long alphanumeric string by hand. When the barcode is smudged, faded, printed at low contrast, curled from humidity, or torn where it crosses a fold in the paperwork, the scanner can't resolve it cleanly.
The practical result isn't "the release is rejected." It's slower and more frustrating than that: the officer either re-scans several times, tries a different angle or lighting, or gives up and manually keys the number from what's printed underneath the barcode. Manual keying reintroduces exactly the kind of human transcription risk the barcode was supposed to eliminate — and if there's already a typo in the underlying number, manual entry makes it more likely to surface at the worst possible moment.
What actually degrades scan quality
- Direct-thermal labels that have faded from heat, sunlight, or age in the cab
- Low print density settings on a desktop thermal printer, producing a barcode with weak contrast
- Labels printed on plain paper and left loose in a folder, where they crease or tear
- Ink-jet printouts on ordinary paper that smear if they get damp
- Barcodes shrunk too small to preserve bar width, especially on multi-shipment paperwork
This is where the physical label stock actually matters operationally, not just cosmetically. Direct-thermal barcode labels designed for Code 128 barcodes hold contrast and edge sharpness far better than a home-printed sheet, and they're built to survive a folder, a clipboard, and a few days riding in a cab door pocket. It's a small, unglamorous detail — but it's the difference between a barcode that scans on the first pass and one that turns into a manual keying exercise at the worst possible moment.
4) Building exact-match discipline into your workflow
Because the rejection mechanism is a string match, the fix is procedural as much as it is technical. A few habits eliminate most of the risk before the truck ever leaves the yard.
Single source of truth for the CCN
Pick one place the CCN lives first — usually the broker's release confirmation — and copy it from there into every downstream system: your TMS, your driver paperwork, your label print job. Every re-typing of the number is another chance for a transposed digit or a dropped character.
Confirm word usage, not just numbers
If your broker's system expects the literal word "PARS" prepended to the CCN and your carrier's eManifest software strips it (or vice versa), that inconsistency alone can break the match even if every digit is correct. Confirm with your broker exactly how the reference should be formatted, including whether "PARS" is part of the string.
Proofread before printing, not after
A visual side-by-side check of the release confirmation against the label about to be printed catches the small stuff — extra spaces, dash placement, carrier-code length — before it becomes a barcode a driver is carrying toward the border.
5) Timing, ACI, and AMPS penalties
A correct, cleanly matched, cleanly scanning PARS number can still cause problems if the timing is wrong. CBSA's highway rules require that ACI cargo and conveyance data be received and validated at least one hour before the truck arrives at the first port of arrival. That window exists so CBSA has time to actually process the advance information — it's not a courtesy buffer, it's the mechanism that makes "pre-arrival" review possible at all.
Arriving before that window has closed, or arriving without a transaction number for a shipment that was supposed to move under PARS, isn't just an inconvenience. It can draw an Administrative Monetary Penalty (AMPS) against the carrier. That's a real cost sitting on top of whatever delay the truck experiences at the booth — and it's entirely avoidable with a dispatch buffer that assumes filings sometimes need a correction cycle.
6) The status you must see before you send the driver
Most PARS status tools walk a shipment through a sequence of stages, and the two that matter most to dispatch are easy to conflate. A shipment can show as "on file with a match notice" — meaning CBSA's system found a corresponding filing — well before it shows as fully accepted with a transaction number. Sending a driver toward the border based on the match notice alone is a common, avoidable mistake.
The status you actually want to see before you tell a driver to head for the booth is confirmation that PARS has a transaction number and a declaration accept — not just that a match was found. A match notice tells you the two filings found each other; it doesn't tell you CBSA has finished reviewing and released the shipment. Treat "matched" as "in progress," not "done."
7) What a rejection actually costs: rework and secondary
It's easy to underestimate a PARS rejection as "a few extra minutes." In practice, a mismatch that surfaces at the booth sets off a chain reaction: the officer can't retrieve the release, the driver has to pull aside, someone calls the broker, the broker checks what was filed against what the carrier transmitted, someone identifies the mismatched character, the broker or carrier corrects and re-transmits, and everyone waits for the new filing to process and clear. A release that should have taken two minutes at primary can turn into an hour or more — and that clock is running with a loaded truck sitting at the border, not moving freight.
If the mismatch can't be resolved quickly enough, or if the officer decides the discrepancy warrants a closer look, the shipment can be referred to secondary inspection, which adds its own queue and its own delay on top of the original problem. In some cases, a failed or rejected PARS release at the border redirects the shipment to an inland sufferance warehouse for clearance — which means the truck isn't just delayed, it's diverted, with additional handling, additional coordination, and additional cost layered onto a trip that was supposed to be a straight-through delivery.
There's also a validity window to watch on the other end. A PARS approval is generally valid for 30 days under CBSA's own guidance (D17-1-10). If a shipment's physical arrival slips past that window — because of a delay, a rescheduled pickup, or a hold at origin — the release expires and has to be refiled from scratch, even though nothing about the underlying paperwork was wrong the first time.
8) A rejection-prevention workflow for dispatch
Most of this comes down to a short list dispatch can run through before a driver is told to head for the border. It's not complicated — it just has to happen every time, not just when something already looks off.
Before dispatch releases the driver
- Confirm the broker has actually filed the release request (not just "queued" it)
- Confirm the broker used the exact same PARS number/CCN the carrier is using on the eManifest — character for character
- Check specifically for typos, stray spaces, dashes, and missing or extra carrier-code characters
- Check whether the word "PARS" is included consistently (or consistently omitted) across both filings
- Confirm the ACI eManifest was actually transmitted and accepted — not just submitted
- Allow real time for the status to update before assuming a rejection; some delay between filing and match notice is normal
If PARS still isn't showing as ready
- Go back to the broker's confirmation as the single source of truth for the CCN
- Re-check the eManifest transmission for the exact same string, not a remembered or retyped version
- Confirm the shipment hasn't drifted past its 30-day approval window if there's been a delay since filing
- Have the driver hold rather than approach the booth on an unresolved status
9) Rolls, sheets, or a PARS/PAPS combo — picking the right format
CBSA requires advance data for PARS shipments, and barcode labels help you meet that by giving the officer a fast, accurate way to retrieve the release CBSA already has on file. Once the process discipline is in place, the physical format you print on is mostly a question of your fleet's volume and workflow.
Direct thermal rolls printing Code 128 barcodes built to hold contrast and edge sharpness through the trip — the print quality that keeps a booth scan a first-try scan.
- Roll format for desktop thermal printers running high daily volume
- Direct thermal stock designed to resist fading and smearing in a cab environment
Also available: PARS labels in sheet format for lower-volume printing, or a PARS/PAPS combo roll and matching PARS/PAPS combo sheets for fleets running both northbound and southbound lanes.
Rolls suit a dispatch desk printing labels continuously through the day — feed, print, cut, done, with no sheet alignment to manage. Sheets suit lower-volume operations or back-office printing where a standard printer tray is more convenient than a dedicated thermal roll printer. If your fleet runs freight in both directions — releasing PARS shipments northbound into Canada and PAPS shipments southbound into the U.S. — a combo format keeps one consistent label style in the printer instead of swapping stock depending on the lane. You can browse the full range of PARS label formats in the PARS labels collection.
10) How PARS relates to PAPS and ACI eManifest
PARS and PAPS are mirror-image programs on opposite sides of the same border: PARS is CBSA's pre-arrival release program for goods entering Canada, while PAPS is the equivalent pre-arrival release mechanism U.S. CBP uses for goods entering the United States by highway. If your fleet runs freight in both directions, your dispatch team is effectively managing two parallel release systems with the same underlying discipline — a reference number that has to match exactly between the broker's filing and the carrier's manifest, and a barcode that has to scan cleanly at the booth.
On the Canada-bound side specifically, the PARS release request and the ACI eManifest are two separate filings that have to reference the same CCN to link automatically. During CBSA system outages, carriers fall back to the System Outage Contingency Plan using paper cargo control documents — which is exactly the scenario where a pre-printed, legible barcode label (rather than something improvised at the last minute) keeps a manual process moving instead of stalling completely.
None of this changes the core lesson of this piece: the release mechanism CBSA built is fast and reliable when the data lines up, and it's the first thing to break when it doesn't. Treat the CCN as the single most important string of characters in the trip packet, and treat the barcode label as infrastructure — not an afterthought printed five minutes before the driver leaves the yard.
Related reading:
11) FAQ
Why did my PARS get rejected at the border?
The most common reason is a mismatch between the CCN on the ACI eManifest and the number the broker used on the release request — often a small difference like a stray space, a dash, a missing carrier-code character, or inconsistent use of the word "PARS." A damaged, low-contrast, or poorly printed barcode that won't scan cleanly is the second major cause, since it can force manual keying and slow the booth interaction even when the underlying number is correct.
How far in advance must PARS/ACI be filed?
CBSA's highway rules require that cargo and conveyance data be received and validated at least one hour before the truck arrives at the first port of arrival. That's a minimum for a clean, first-try filing — build extra time into your dispatch schedule in case a mismatch needs to be corrected and refiled before arrival.
Can I reuse a PARS number?
No. A Cargo Control Number can't be reused for three years, and reusing one causes an immediate rejection because the system has already linked that number to a previous shipment. Always generate a new, unique CCN for each shipment rather than recycling one from an old label or template.
Authority references: CBSA — Pre-Arrival Review System / eManifest. Informational only; always confirm filing details and timing with your customs broker.