At a glance
A real-time work queue of Bring Mypack (Pakke i postkasse / pickup point) parcels that are approaching the end of their pickup-holding window, plus orders that have blown their dispatch deadline. Mypack parcels delivered to a Posten parcel locker or a post-in-shop (Post i Butikk) are held for a fixed number of days, then returned to sender if the recipient never collects them. This card surfaces those parcels before they expire so the despatch and customer-service teams can prompt the customer, and flags orders sitting past their promised hand-over time so they can be pushed out of the warehouse.
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 DTC outdoor-apparel brand based in Oslo, around 1,900 outbound parcels per week, splits volume roughly 55 percent Bring Pickup Parcel (Mypack to a Posten locker or Post i Butikk), 35 percent Bring Home Delivery Parcel and 10 percent cross-border to Sweden. The carrier agreement holds pickup-point parcels for 7 calendar days; the warning window is the final 48 hours. Reading taken at 08:00 CEST on 14 Apr 26. The card shows two lists:
The Mypack limb reads 7, which trips the
>5 threshold, so the card is in alert. Five things to notice:
- Each expiring parcel is a recoverable sale, not a lost one (yet). A parcel that expires and goes back on its return leg costs the merchant the outbound carriage, the return carriage, and almost always a refund. Prompting the customer in the final 48 hours typically recovers 40 to 60 percent of otherwise-expiring Mypack parcels. The action is a targeted “your parcel is waiting, collect by 16 Apr 26” SMS or email, not a generic reminder.
- Locker parcels and Post i Butikk parcels behave differently. A Posten parcel locker (Pakkeboks) frees space on a fixed cadence and the carrier may shorten the hold during peak; a Post i Butikk hold is more forgiving. If your expiring list skews to lockers during December peak, expect the effective hold to be shorter than the nominal 7 days.
- The dispatch-SLA limb is a warehouse problem, not a carrier problem. Those 2 unbooked orders never reached Bring. The fix is upstream: check that the label-booking step ran (see Label Generation Success) and that the Mybring Booking API was reachable (see Bring Tracking API Unavailable / 5xx).
- Holding deadlines are in carrier-local time. The
READY_FOR_PICKUPscan timestamp and the holding deadline are recorded in the pickup point’s local time (CET / CEST for Norway). If you read the card in UTC the deadline can appear an hour or two earlier than the customer experiences it; always show the customer the local collect-by date. - Expiry is seasonal. Collection discipline drops over public holidays and the Christmas window. Expect the expiring count to rise across Påske (Easter) and the 23 Dec to 2 Jan window even at flat volume, because recipients are travelling and lockers fill faster.
Sibling cards merchants should reference together
This card is a real-time work queue. Pair it with these to diagnose cause and measure the leakage it prevents:Reconciling against the source
Where to look in Bring’s own tooling: Mybring is the merchant portal. The pickup status of a consignment lives under Tracking (search the shipment number) and the holding deadline shows as the pickup-point event with its collect-by date. Bulk despatch and booking status live under Booking → Shipments. For the customer-facing view, Bring’s public tracking at tracking.bring.com shows the sameREADY_FOR_PICKUP event and the collect-by date the recipient sees.
The closest like-for-like view is Tracking, status Available for pickup, sorted by holding-deadline ascending. The dispatch-SLA limb has no direct equivalent in Mybring; it is computed from your own order’s promised hand-over time against the absence of a Bring booking confirmation.
Why our number may legitimately differ from Mybring:
Cross-connector reconciliation:
Known limitations / merchant FAQs
Why does a parcel I know was collected still show in the expiring list? Ingestion lag. Bring surfaces theCOLLECTED_BY_RECIPIENT scan in a batch, not instantly. For up to one ingestion cycle (15 to 60 minutes) a just-collected parcel can linger in the queue. The card deliberately keeps a parcel in the list until the collected scan is confirmed rather than dropping it on an assumption; a collected parcel that never clears after several cycles points to a tracking-event gap (see Shipments with Tracking-Event Gap).
What is the difference between this card’s two lists?
The Mypack limb is a carrier-side problem the customer must solve (collect the parcel). The dispatch limb is a warehouse-side problem you must solve (book the label and hand the parcel over). They share a card because both are time-critical work queues that, left alone, end in a refund, but the owners and the fixes are different.
Can I change the 48-hour warning window?
Yes. The warning window and the >5 count threshold are both configurable per profile in the Alert Rules tab. A high-Mypack-volume merchant may want a 72-hour window to give more reminder runway; a low-volume merchant may want a tighter window to keep the queue small.
Why does the expiring count spike over holidays even though my volume is flat?
Collection behaviour, not despatch behaviour. Recipients travel over Påske and Christmas, lockers fill and the carrier may shorten the effective hold, and reminder emails get buried. Expect the queue to grow across public-holiday windows; pre-empt it by front-loading reminder messaging before the holiday rather than during it.
Does this count Bring Home Delivery Parcels?
Not in the Mypack limb. Home Delivery has no pickup-holding window, so a missed home delivery is not an “expiring pickup”; it shows on Failed Deliveries. Home Delivery orders can appear in the dispatch-SLA limb if they were never booked.
A parcel expired and went back to me. Where do I see that?
On Returned to Sender. Once the holding window lapses, Bring books the parcel on its return leg; it leaves this card’s expiring list and enters the return-to-sender flow. Track the two together to size the true cost of uncollected pickups.
What is the playbook when the Mypack limb crosses the threshold?
In order: (1) trigger the collect-by reminder to every customer in the warning window with the local collect-by date and the pickup-point name, (2) for high-value orders, follow up with a second channel (SMS if the first was email), (3) check whether the spike is concentrated at specific pickup points (a single full locker can generate a cluster), (4) if the dispatch limb is also firing, fix the booking pipeline first since unbooked orders never even reach a pickup point.