At a glance
On-time delivery rate for Norway-to-Norway shipments only. This is Bring’s home turf: Posten Bring runs the Norwegian network end-to-end, with its own terminals, drivers and last-mile, and no customs or partner-handover friction. A miss on this dial therefore points at a Bring-side operational issue (terminal disruption, weather on a northern route, a sortation incident) or at your own upstream data, not at cross-border friction. It is the cleanest read you have on Bring’s actual delivery performance, stripped of every cross-border variable, which is why it carries the tightest threshold of the OTD family.
| What it counts | COUNT(no_domestic_shipments WHERE delivered_at <= promised_delivery_date) / COUNT(no_domestic_shipments WHERE delivered_at IS NOT NULL) over the rolling 30-day window, period-over-period. Scope is Norwegian origin and Norwegian destination only; any cross-border consignment is excluded and sits on the export dials. |
| API endpoint | Bring Booking API POST /booking/v3/bookings returns consignmentNumber, service.id (Home Delivery / Pickup Parcel / Business Parcel) and expectedDelivery.estimatedDate. Bring Tracking API GET /tracking/v3/tracks/{consignmentNumber} returns the event stream including delivered. The dial joins booking + tracking on consignmentNumber. |
| Promise day | The card uses Bring’s domestic expectedDelivery.estimatedDate: next working day for Home Delivery in the major-city catchments, one to two working days for Pickup Parcel, two to four working days for northern Norway (Nordland, Troms, Finnmark). Delivery on or before midnight Oslo time on that date counts as on-time. |
| Delivery success criterion | A delivered scan with the recipient, neighbour, mailbox or collected-from-pickup-point status. A parcel dropped at a pickup point but not yet collected is not counted as delivered until the recipient picks it up. |
| Service-tier scope | All tracked domestic services (Home Delivery, Pickup Parcel, Business Parcel, domestic Cargo with a tracked code). Posten letter products (Bring Mail) are excluded because letters do not generate a delivered scan. |
| Why it is the cleanest dial | No customs step, no partner-carrier handover, no border. Everything that affects this number is inside Bring’s own network or inside your own despatch process. When this dial moves and the export dials do not, the cause is domestic and on Bring’s side or yours. |
| Winter handling | Norwegian winter (Nov to Mar) genuinely affects northern lanes. The card does not auto-adjust; manage seasonality per route via OTD by Route rather than re-baselining the global dial. |
| Time window | 30D vsP (rolling 30 days, period-over-period). Daily readings are noisy below 150 consignments per day. |
| Alert trigger | <95%. This is the tightest threshold in the OTD family because the domestic network has no structural excuse: Norwegian-domestic Bring Home Delivery typically runs 95 to 97 percent. Below 95 percent is a real operational signal. |
| Roles | owner, operations |
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 homeware brand with the warehouse in Lillestrøm (just outside Oslo), around 4,400 outbound parcels per week, predominantly domestic: 88 percent Norway-to-Norway, 12 percent Nordic export. 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. Domestic leg only:| Region | Consignments | Delivered on or before promise | OTD Rate | Previous period |
|---|---|---|---|---|
| Oslo / Viken / major cities | 9,820 | 9,576 | 97.5% | 97.3% |
| Western Norway (Bergen / Stavanger) | 3,140 | 3,015 | 96.0% | 96.4% |
| Mid Norway (Trondheim) | 1,610 | 1,535 | 95.3% | 95.8% |
| Northern Norway (90xx to 99xx) | 2,180 | 1,962 | 90.0% | 93.7% |
| All domestic (this card) | 16,750 | 16,088 | 96.1% | 96.5% |
<95% alert line. Five things to notice:
- The headline is healthy, but the north is dragging. 96.1 percent sits comfortably above threshold, yet northern Norway fell from 93.7 to 90.0 percent. The major-city catchments held; the drag is geographic. Confirm in OTD by Route before deciding the network is fine.
- A domestic miss is Bring-side or yours. There is no customs step and no partner handover to blame. If this dial drops, the cause is a Bring terminal or last-mile issue, a weather event on a northern route, or your own despatch process (late terminal collection, bad address data). That makes it the most actionable OTD dial you have.
- Northern winter is a known pattern. The 90.0 percent northern reading in mid-April is the tail of the winter window; Nordland, Troms and Finnmark routes run 88 to 92 percent from December through March and recover to 95+ by summer. Manage it per route, not by moving the global threshold.
- Pickup Parcel quietly outperforms Home Delivery domestically. Within these numbers, Pickup Parcel typically reads one to two points higher than Home Delivery because there is no “no one home” failure mode; the recipient collects from a fixed point. For northern postcodes, defaulting Pickup Parcel is the single best OTD lever.
- 662 late domestic parcels is the workload. 96.1 percent on 16,750 parcels is 662 late deliveries, each a likely WISMO touchpoint. Pair with Late Shipments for the absolute count and staff the queue accordingly.
Sibling cards merchants should reference together
Domestic OTD is the cleanest read on Bring’s own network. Pair it with these to localise and act:| Card | Why pair it with Norway-Domestic OTD | What the combination tells you |
|---|---|---|
| On-Time Delivery Rate | The all-lane aggregate. | If the aggregate drops but domestic holds, the cause is cross-border; if domestic drops too, the cause is the home network or your despatch. |
| Nordic Export OTD (NO → SE/DK/FI) | The cross-border counterpart. | Domestic-stable, cross-border-down isolates the cause to the border; both-down points at a network-wide event. |
| OTD by Route | Where the domestic drag is concentrated. | Northern Norway, Arctic-circle postcodes and weather-hit routes usually drag the domestic average. |
| Late Shipments | The absolute count behind the percentage. | Turns 96 percent into the real ticket workload. |
| Exception Rate | Tracking exceptions (held at terminal, address invalid, no answer). | A rising domestic exception rate predicts a falling domestic OTD at 24 to 72 hours. |
| First-Attempt Delivery Rate | Whether the parcel landed first time. | A gap between OTD and first-attempt is the redelivery / collection friction tax. |
Cross-connector: shopify.unfulfilled_orders | Upstream cause: orders waiting for a label cannot meet OTD. | Climbing unfulfilled count predicts a domestic OTD dip 2 to 4 days later. |
Reconciling against the vendor’s own dashboard
Where to look in Bring’s own portal: Mybring is the merchant-facing portal. Navigate to Reports → Delivery Performance for the headline domestic OTD, Statistics → Service Performance for the per-service-code breakdown, and Tracking to read an individual domestic consignment’s event stream. Filter to Norway origin and Norway destination to match this card. The monthly Quality Report PDF for Customer Service Account holders is the authoritative version for service conversations. The closest like-for-like view is All Tracked Services, Origin Norway, Destination Norway, Last 30 Days, Outbound Only. Toggle Home Delivery / Pickup Parcel / Business Parcel to drill per tier, and filter postcode ranges to isolate the north. Why our number may legitimately differ from Mybring:| Reason | Direction | Why |
|---|---|---|
| Timezone (CET / CEST vs UTC) | Boundary days off | Domestic scan timestamps are recorded in Oslo local time; Mybring presents Oslo local, the card stores UTC. Across 30 days the effect is below 0.1 points; a single-day boundary can shift by one during summer time. |
| Tracking-event ingestion lag | Ours lower for “today” | Bring’s tracking stream is normally 5 to 30 minutes behind the truck scan, longer at peak. A just-delivered parcel may not show in our index for a few minutes; Mybring shares the source but does not always lag in step. |
| Pickup-point collection timing | Either | A Pickup Parcel “delivered to point” is not counted as delivered until the recipient collects. If Mybring counts the drop-to-point scan as delivered, its OTD reads higher than ours for the Pickup Parcel slice. |
| Service-tier reclassification mid-period | Either | Moving SKUs from Home Delivery to Pickup Parcel mid-month splits the population in the portal’s per-service view; the card uses the service code at label generation. Aggregate agrees, per-service can diverge. |
| Returns inclusion | Ours lower if RTO-heavy | Mybring’s default sometimes includes the return leg; the card is outbound-only. |
| Card | Expected relationship | Causes of legitimate divergence |
|---|---|---|
shopify.unfulfilled_orders | Upstream input: orders waiting for a Bring label cannot meet OTD. | Webhook failures, manual fulfilment delays, B2B / pre-order flows. |
postnord.pos_otd_rate | Alternative carrier on Norwegian domestic lanes. | Different shipments, different network; useful for carrier choice, not a like-for-like reconciliation. |