At a glance
Share of Norway-to-EU outbound shipments that cleared export customs within three days of leaving the despatch terminal. Norway is outside the EU customs union, so every parcel crossing the border needs an export customs declaration (a tolldokument). Bring auto-generates the export documentation as part of the cross-border booking, but the declaration can still fail or stall: missing or mismatched commodity codes, an absent EORI number, an unstated value, or a goods description Norwegian or destination customs rejects. When the declaration stalls, the parcel sits at the border and the customer’s clock keeps running. This dial is the early-warning that your export-paperwork pipeline has broken.
Calculation
Calculated automatically from your Bring data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A Norwegian home-electronics accessories brand based in Sandefjord, around 1,900 outbound parcels per week, with a growing EU export book: roughly 35 percent of volume now ships Norway-to-EU (Germany, Netherlands, Poland) via Bring Cross-Border, the rest domestic. Reading taken at 09:00 CET on 14 Apr 26 for the trailing 30 days (15 Mar 26 to 13 Apr 26), compared with the previous 30 days. NO-to-EU leg only:
The dial reads 88.6 percent, down 7.3 points period-over-period. The
<85% alert is not tripped at the aggregate, but Poland alone has collapsed to 72.2 percent. Five things to notice:
- The period-over-period drop is the real signal. 88.6 percent in isolation looks acceptable; an overnight 7-point fall does not. Something changed: a product feed update, a commodity-code remap, an EORI lapse, or a Tolletaten process change. The trend, not the level, tells you a fault was introduced.
- Poland is the broken lane. 72.2 percent against a 95.1 percent baseline says the failure is destination-specific. The usual culprit is a commodity code (HS code) that Norwegian export or Polish import customs newly rejects for a SKU range, or a value threshold that tripped a manual review. Open three held Polish consignments in Mybring and read the customs reason text.
- The tolldokument is generated from your booking payload. Bring auto-builds the export document, but only from the data you send. A blank
commodityCode, a missingsenderEori, or acontentValueof 0 produces a document customs will not accept. Check whether a recent catalogue sync stripped HS codes from the affected SKUs. - 316 stalled parcels is the customer-facing cost. Each one is a frozen tracking page and a likely WISMO ticket, plus the risk the parcel times out and returns. Pair with Exception Rate, customs holds surface there as exceptions, and with Nordic Export OTD (NO to SE/DK/FI) for the wider cross-border picture.
- Three days is generous on purpose. Clean declarations clear same-day to next-day. The three-day window deliberately ignores normal border latency so the dial only moves when something is genuinely stuck. A parcel still pending on day 2 is not yet a miss.
Sibling cards merchants should reference together
Customs clearance is an upstream gate: if the paperwork stalls, every downstream delivery metric on the cross-border lane degrades. Pair it with these:Reconciling against the vendor’s own dashboard
Where to look in Bring’s own portal: Mybring is the merchant-facing portal. Navigate to Tracking to read the customs lifecycle on an individual held consignment (theexport_customs_started, customs_held and export_customs_cleared events carry reason text), and to Statistics → Cross-Border Performance for the aggregate clearance view. For the document itself, the Customs / Tolldokument section of the booking shows the generated declaration and any validation errors Bring flagged before lodging it.
The closest like-for-like view is Cross-Border Outbound, Origin Norway, Destination EU, Last 30 Days, Customs Outcome.
Why our number may legitimately differ from Mybring:
Cross-connector reconciliation: