Bring tracking statuses follow a parcel through the Norwegian postal group's network, from the moment your store transmits the order data to delivery at a door or a pickup point. Bring (Posten Bring) is the backbone carrier for Norway and a major player across the Nordics, so if you sell into the region, your customers read these statuses daily.
Most of them mean the parcel is moving as planned. A few mean your store should act. Here is the sequence in plain language, grouped by meaning since exact wording varies by service and country.
The normal Bring sequence
Parcel information received / EDI received. Bring has the electronic shipment data but has not scanned the parcel. Nothing is physically moving yet. This is Bring's version of the "parcel data submitted to carrier" status that generates so many confused support tickets. If it lasts more than a day, the delay is in your warehouse handover, not at Bring.
Collected / handed in. First physical scan. The parcel is genuinely in the network and the delivery clock starts.
In transit / arrived at terminal. Moving between Bring terminals. Norway's geography means long lanes are normal: an Oslo-to-Tromsø parcel passes several terminals, and repeats of this status are not a problem.
Out for delivery / on its way. On the final vehicle. Most parcels complete the same day.
Delivered. Handed over at the door or left as agreed.
Ready for pickup / delivered to pickup point. The Nordic classic. A large share of Bring deliveries end at a Post i Butikk counter or parcel locker rather than a doorstep. The customer usually has around two weeks to collect before the parcel returns. This status deserves prominent, positive treatment on your tracking page: "waiting for you at your pickup point" reads very differently from a bare "delivered".
The statuses that need action
Delivery attempt failed / recipient not present. For home deliveries. The follow-up line says what happens next: reattempt, redirect to a pickup point, or held at terminal. Messaging the customer at this scan, before the slip in the mailbox, is the difference between a smooth redirect and a WISMO ticket.
Customs clearance / held by customs. Cross-border parcels into Norway meet customs because Norway sits outside the EU customs union. Shipments missing data or with unpaid VAT stall here. If your parcels stick on this status repeatedly, the fix is upstream paperwork, covered in our guides to packages stuck in customs and DDP vs DDU shipping.
Not collected / return to sender. The pickup window expired or the parcel was refused. This should trigger your returns flow automatically while the parcel is still traveling back, so the refund-or-reship decision is made before it hits your dock.
The Norway wrinkle every EU brand hits
Norway is Nordic but not EU. Selling from an EU warehouse into Norway means VAT registration questions (the VOEC scheme for low-value goods), customs data on every label, and duties handling that Sweden-bound parcels never see. Bring handles the border smoothly when the data is right and stalls when it is not. That data problem is exactly what carrier integration quality decides.
Pango connects Bring through prebuilt connectors alongside PostNord, Instabee and 100+ other carriers, normalizes every Bring status into one clean milestone set, and can act on the scans: a failed attempt fires a pickup-point message, a customs stall flags the paperwork, an uncollected parcel opens the return. One record, across every Nordic carrier you use.
The bottom line
Bring's happy path runs from EDI to a doorstep or pickup point without your attention. The action statuses are failed attempts, customs holds, and uncollected pickups, and each one is worth an automatic response rather than a support ticket. Pango normalizes Bring with every other Nordic carrier and acts on the scans. See the post-purchase operations platform and book a demo.
