---
content_id: package-problem-parcel-locker-or-pickup-code-not-working
canonical_url: https://11tracking.com/package-problems/parcel-locker-or-pickup-code-not-working/
title: Parcel Locker or Pickup Code Missing, Expired, or Not Working
meta_description: Find the right pickup method when a locker code, PIN, QR, app
  key, or collection notice is missing, expired, invalid, or not working.
language: en
published_at: 2026-08-04
last_reviewed: 2026-08-04
carrier_scope:
  - Multi-carrier locker, pickup-point, staffed-collection, app, and credential
    examples
jurisdiction_scope:
  - Multiple scoped carrier, operator, service, account, device, location, and
    country examples
---


# Parcel Locker or Pickup Code Missing, Expired, or Not Working

A parcel can be genuinely ready for pickup while its release method is missing or unusable. First confirm the official `Ready`, `Available for Pickup`, or equivalent event, the current pickup location, the responsible carrier or locker operator, and the collection deadline. Then identify whether this parcel uses a PIN, QR or barcode, app action, Bluetooth key, paper notice, staffed identity check, shipper-provided release code, partner PIN, or no separate credential.

Do not assume that every pickup uses a numeric code, that the tracking number opens the locker, or that the carrier can resend whatever is missing. Some systems resend a code, some generate a new code inside an activated app, some use an authenticated button or Bluetooth key, and some staffed locations release parcels with identification or a pickup barcode instead. Use only the official recovery method for the exact operator, service, country, and location type.

Do not post or forward a live code, QR image, barcode, release link, tracking number, phone number, email address, account screenshot, or pickup-location detail. Do not guess codes, try another person's credential, force a compartment, or tamper with a scanner. A support request also does not automatically pause the holding period.

## Start with four facts

Before troubleshooting the phone, app, code, or locker, write down four facts from the carrier or operator's official tracking page, app, account, email, SMS, or paper notice:

1. **The exact pickup state.** Does it say the parcel is ready, or only that it was routed, redirected, assigned, or is moving toward the location?
2. **The current location.** Use the newest official location, not an older message or the place you expected.
3. **The operator.** The carrier shown in tracking, the locker operator, the parcel shop, and the merchant may be different organizations.
4. **The deadline.** Use the date or time stated for this parcel. Do not replace it with a general period remembered from another carrier.

If the parcel is not yet officially ready, code troubleshooting is premature. A location assignment or arrival scan does not necessarily mean the parcel has been processed for customer access. Start with [Available for Pickup](/tracking-status/available-for-pickup/) or [Tracking Not Updating](/package-problems/tracking-not-updating/) instead.

If the parcel was sent to an unexpected pickup point, redirected without permission, or appears to have been collected by someone else, treat that as a shipment-control or security problem before trying to use the credential. Use [Package Rerouted, Held, or Picked Up Without Permission](/package-problems/package-rerouted-held-or-picked-up-without-permission/).

## Identify the release method before looking for a code

“Pickup credential” is a broad category. It can be a message, an account object, an activated-device key, a physical notice, an identity check, or a code supplied by someone other than the carrier.

| Release method | Where it may appear | What must be true before it works | Important limitation |
|---|---|---|---|
| Numeric PIN or collection code | SMS, email, app, account, or partner message | Correct parcel, location, operator, and current credential | Not every pickup uses a PIN |
| QR code or barcode | App, email, account, or paper notice | Correct screen or notice and a supported scanner | A QR may have a manual-entry alternative, but only where documented |
| Dynamic app code | Authenticated carrier app | Correct account, activated device, current code, and sometimes correct device time | An older displayed code may refresh while the parcel remains collectible |
| App button or Remote Opening | Carrier or locker app | Parcel associated with the account and supported locker | No PIN or QR may be needed |
| Bluetooth digital key | App near the locker | Correct account, app, proximity, Bluetooth, and operator-required permissions | An app or entitlement failure can look like a locker failure |
| Paper notice or notification card | Delivered by the carrier or driver | The exact redirected or notified-shipment workflow | A digital pickup code may not exist |
| Staffed ID, barcode, or tracking route | Post office, carrier counter, retail partner, or Access Point | The exact identification and authorization requirements | “Bring ID” is not a universal locker fallback |
| Shipper-provided release code | Merchant, sender, or shipper channel | The shipper created and communicated the correct code | The carrier may not be able to invent or recover it |
| Pickup-partner PIN | Partner or carrier message | The partner's release process | Rules can differ inside one carrier network |
| No separate credential | Staffed identity route or authenticated app action | The official alternative requirements are satisfied | Searching for a nonexistent code wastes the holding window |

The release method can change even inside one carrier's network. A parcel addressed directly to a locker may use an app code, while a parcel redirected after a failed home delivery may use a paper notice or staffed counter. A parcel shop may ask for a code supplied by the merchant or pickup partner rather than the transport carrier.

## Separate readiness, notification, credential, and access

These states are related, but they are not interchangeable:

```text
routed to a pickup location
→ physically received by that location
→ processed and marked Ready
→ release method selected
→ notification or credential generated
→ credential delivered or shown in an account
→ credential validated
→ door or staff release succeeds
→ correct parcel is present
→ collection is recorded
```

A visible event supports only its own stage.

| Visible event | What it can support | What it does not establish |
|---|---|---|
| Assigned or redirected to a location | A pickup route or location was selected | The location physically has the parcel |
| Received at location | The operator recorded local receipt | The parcel is processed and ready |
| Ready or Available | The operator recorded collection availability subject to release rules | A code was generated, delivered, or remains usable |
| Notification sent | The system recorded an outbound notice | The correct phone, email, account, or device received it |
| Credential shown | The current account or message displays a release object | The terminal will accept it or the correct location was selected |
| Credential accepted | The release system accepted the credential | The compartment opened or contained the correct parcel |
| Door opened or staff released | Physical access was granted | The correct parcel was inside |
| Collected | The operator recorded collection | The named recipient personally possesses the parcel |

If the door opens but the compartment is empty, contains the wrong parcel, or the system says `Collected` when you did not receive it, stop code troubleshooting. Use Parcel Locker Empty or Marked Collected when that guide is published.

## Find who issues the missing access method

The actor transporting the parcel may not control the credential.

| Possible issuer | What it may control | What to check |
|---|---|---|
| Carrier | Tracking state, some notifications, carrier app, or pickup rules | Official tracking and carrier account |
| Locker operator | Terminal, operator app, digital key, access event, or locker support | Operator name on the locker and official app/domain |
| Merchant or shipper | Contact data, service selection, shipper release code, or marketplace instructions | Order account and merchant message history |
| Marketplace | Order-linked pickup credential or integrated notification | Official marketplace account, not an unsolicited link |
| Pickup partner | Partner PIN, local release process, staffed procedure | Exact location notice and partner instructions |
| Postal or carrier account provider | Login, parcel association, device activation, or identity verification | Correct account, phone/email, and device |
| Staffed location | Release under carrier or partner policy | Required ID, notice, barcode, tracking record, or authorization |

This matters when support sends you in circles. Ask each actor about the layer it controls:

- **carrier or operator:** Is the parcel Ready, which release method applies, and was an access object generated?
- **merchant or shipper:** Which phone/email was transmitted, and does this service use a shipper-provided release code?
- **app/account support:** Is the parcel associated with the correct account and activated device?
- **pickup partner or staffed point:** Which release evidence is accepted at this exact location?

Use [Who Should I Contact About a Package?](/delivery-actions/who-to-contact-about-a-package/) when the carrier, operator, merchant, and pickup point dispute ownership of the problem.

## If no code, QR, or pickup notice arrived

Use this order:

### 1. Confirm that the parcel is actually Ready

Do not rely on an order page or tracking aggregator when the carrier or locker operator has a more specific status. Some operators generate or reveal the collection credential only after the final readiness scan.

### 2. Confirm that this parcel requires a digital credential

Check the exact location type and service. A staffed FedEx, Canada Post, Australia Post, UPS Access Point, post-office, or retail-partner pickup may use ID, a barcode, tracking details, a door tag, or a shipper release code. An app-based locker may use Remote Opening or a Bluetooth key rather than a PIN.

### 3. Check the authoritative channel

Look in the place named by the official instructions:

- the carrier or operator app's pickup or locker section;
- the authenticated account;
- the official readiness email or SMS;
- the paper notice;
- the merchant or marketplace account when it owns the release code.

Do not assume that the ordinary tracking screen contains the credential. DHL Packstation, for example, places its pickup code in a dedicated Packstation area of the Post & DHL app rather than the standard shipment-tracking view.

### 4. Check which contact data was used

The phone number or email can come from a carrier account, merchant checkout, shipping label, shipper integration, or marketplace. A missing message may therefore require the merchant or shipper to confirm what it transmitted. Do not promise that any actor can change shipment-specific contact data after dispatch.

### 5. Use only the documented recovery

Official systems use different recovery models:

- **resend:** La Poste France and DPD Netherlands document missing-code recovery;
- **automatic regeneration:** DHL Packstation generates a current app code rather than resending a fixed one;
- **account retrieval:** some credentials are already present in the official app or account;
- **no-code alternative:** InPost Remote Opening or a staffed identity/barcode process may replace a PIN;
- **shipper route:** UPS describes shipper-provided parcel release codes for some Access Point collections.

The correct action is not simply “ask the carrier to resend the code.” First identify whether there is a resendable code and who owns it.

## If the code says invalid, expired, or already used

These messages describe different problems.

### Invalid

Possible explanations include:

- wrong pickup location or terminal;
- code for another parcel;
- older or refreshed app code;
- wrong account or device;
- incorrectly entered code;
- parcel no longer in the same pickup state;
- credential issued by another actor;
- terminal or operator-service failure.

Do not keep trying random variations. Confirm the exact parcel, newest location, current credential, and official release method. Repeated guesses do not prove legitimacy and can complicate the official recovery process.

### Expired

First separate two clocks:

```text
credential instance
≠
parcel holding period
```

A dynamic credential can refresh every short interval while the parcel remains available. Conversely, a fixed credential can stop working because the actual collection period ended and the parcel moved to another location or entered return processing.

Check the current official status:

- still Ready at the same location;
- moved to a staffed point;
- deadline passed but no return event yet;
- returning;
- already collected.

If the holding period has ended or return has started, the primary problem is no longer credential recovery. Follow the official expired-pickup or return route rather than trying to reactivate an old code.

### Already used

Do not treat `already used` as automatic proof of theft, account compromise, or successful collection. Check the official parcel status and access outcome:

- Did your own earlier attempt open a compartment?
- Does tracking say `Collected`?
- Is the code linked to another parcel?
- Did the app generate a replacement credential?
- Does the operator have an official incident route?

If the status indicates unauthorized collection or the parcel is absent after an opening event, use the unauthorized-pickup or empty-locker guidance rather than continuing to test credentials.

## If a QR code or barcode will not scan

Use the newest official code on the correct terminal. A scanner failure does not by itself prove that the credential is invalid.

Safe checks include:

- confirm the QR or barcode belongs to this parcel and current location;
- open it from the official app, account, email, or notice;
- use normal screen brightness and an undamaged display or notice;
- remove obvious glare or obstruction;
- follow the operator's stated scanning distance and orientation;
- use manual entry only when the official terminal or instructions support it;
- use an official app-opening alternative where available.

InPost UK and DHL Packstation document operator-specific alternatives when scanning fails. That does not create a universal rule that every tracking number, barcode number, or manual code can be entered at every locker.

Never upload the QR or barcode to a public support forum. It may function as a live release credential.

## If the app does not show the parcel or will not open the locker

Treat the app as one layer in the access system, not as proof that the locker is broken.

Check only the prerequisites documented by the operator:

1. **Correct app and account.** Confirm that you are using the official app for the actual locker operator and are logged into the account associated with the parcel.
2. **Matching contact data.** Some systems associate the parcel through the same phone number or email used when ordering.
3. **Device activation.** DHL Packstation requires the pickup code to be displayed on an activated device.
4. **Identity verification.** PostNord Sweden's digital-key model includes identity verification.
5. **Correct app section.** The pickup credential may be outside ordinary tracking.
6. **Current app and session.** Check the operator's current compatibility and login guidance.
7. **Required permissions.** PostNord, Packeta, and DPD Poland document Bluetooth-based opening; Packeta also describes mobile internet and location services.
8. **Proximity and correct locker.** Bluetooth or local digital-key access may require you to be beside the exact locker named in the notice.
9. **Device time.** A dynamic code can depend on accurate device time.
10. **Network preparation.** Some systems can display a prepared credential offline, but this is operator-specific and should not be assumed.

Do not make reinstalling the app the first step. Reinstallation, logout, number changes, or device replacement can create or worsen an activation problem. Follow the operator's device-change or account-recovery instructions instead.

If the required digital method is not usable because of a sensory, mobility, dexterity, cognitive, communication, or other functional barrier, the central problem is accessibility rather than ordinary app troubleshooting. Use [Package Delivery and Pickup Accessibility Needs](/delivery-actions/package-delivery-and-pickup-accessibility-needs/) and ask the operator for an available non-digital or assisted route. The pickup deadline may continue.

## If Bluetooth opening fails

A Bluetooth failure can occur before the locker receives a valid release command. It can involve:

- wrong locker or parcel selected;
- app not associated with the parcel;
- missing identity or device activation;
- Bluetooth disabled;
- required location permission disabled;
- no mobile data or failed app session where the operator requires connectivity;
- user not close enough to the terminal;
- operator backend or locker fault.

Use only the settings and permissions named by the operator. Do not attempt to pair with, probe, or manipulate the locker outside the official app. Do not assume that a hardware fault exists until account, entitlement, location, and app state have been separated.

When an official keypad code is also offered, use that documented branch. Do not invent or derive a keypad code from the tracking number.

## If the code was sent to the wrong phone number or email

Identify who supplied the contact data:

- carrier account;
- merchant checkout;
- shipper label;
- marketplace;
- recipient's saved profile;
- pickup-network account.

Then contact the actor that can verify or correct that source. A carrier may control its account but not a phone number embedded in a merchant-created label. A merchant may confirm the checkout data but not the locker operator's app state.

Ask for a shipment-specific official fallback:

- retrieve the credential from an authenticated account;
- verify the recipient through the documented staffed process;
- regenerate or resend through the existing official channel;
- have the shipper provide its release code;
- move or redirect the parcel only if the service permits it;
- use another documented release method.

Do not ask support to send the credential to an unverified new number or email. Do not post the old or new contact details publicly.

## If a staffed pickup point asks for a code you do not have

First identify what kind of location it is:

- carrier counter;
- post office;
- UPS Access Point;
- FedEx Hold at Location;
- parcel shop;
- retail partner;
- marketplace pickup point;
- locker with nearby staff but no staff override.

Ask the location which official release evidence applies to this parcel:

- pickup code or partner PIN;
- shipper-provided release code;
- app barcode or QR;
- tracking number plus ID;
- door tag or paper notice;
- government-issued photo ID;
- address or authorization evidence.

Do not assume that staff can override an automated locker, reveal a credential, change the addressee, or accept ID in place of a code. If the core problem becomes a name mismatch, age requirement, missing ID, or alternate-collector authorization, use the dedicated identity and authorized-collector guidance when available.

## Protect the holding deadline while access is unresolved

Different operators use different holding periods. Some lockers return the parcel after a short window; some transfer it to a staffed post office; some staffed points hold it longer. The exact message or account page for the parcel should control.

Credential failure does not automatically pause the clock. A support case, reminder, app error, wrong contact channel, or promised callback does not establish an extension unless the operator confirms one.

Record privately:

- the official Ready timestamp;
- current pickup location;
- stated collection deadline;
- exact error wording without the credential itself;
- date and time of each official access attempt;
- official support case or reference;
- any confirmation of resend, regeneration, transfer, or extension;
- the newest tracking state.

Also identify deadlines outside the pickup system. A merchant, marketplace, return, refund, travel-document, event, payment, or dispute deadline can continue while the carrier or operator investigates access.

If the deadline is close, ask the responsible operator a precise question:

> The parcel is shown as Ready at **[location]** until **[deadline]**, but the official release method is unavailable or rejected. Please confirm the required release method for this parcel, its issuer and current status, any documented alternate collection method, whether the holding period has been extended, and what will happen if access is not restored before the deadline.

Do not include the live code, QR, barcode, or full tracking number in a public post.

## Use the operator's official fallback, not a universal fix

The public decision sequence is:

```text
verify Ready state and current location
→ classify the release method
→ identify the issuer and authoritative channel
→ verify documented account, contact, device, or identity prerequisites
→ use the documented resend, regeneration, app, manual-entry, staffed, shipper, or partner route
→ open the official support case
→ protect the collection deadline
→ route the physical outcome
```

A few current systems illustrate why classification matters:

| System example | Release model that changes the action |
|---|---|
| InPost UK | App details, email/SMS, QR or code, and Remote Opening without PIN or QR |
| DHL Packstation Germany | Dynamic app code on an activated device; some redirected shipments use a notification card instead |
| PostNord Sweden | Verified app identity, Bluetooth, and digital key |
| Packeta Z-BOX | App/Bluetooth plus keypad branch |
| Australia Post | Locker access code, followed by a staffed Post Office branch after the locker period in the cited service |
| UPS Access Point | ID, shipper release code, or pickup-partner PIN depending on the shipment and location |
| FedEx Hold at Location | Staffed pickup with ID, tracking or door-tag details, and an optional Delivery Manager QR |
| Canada Post post-office pickup | Staffed ID, mobile barcode, or delivery notice rather than a universal locker PIN |
| La Poste Pickup Station | Official customer-service resend for a missing locker code |
| PostNL locker | Collection code generated when the parcel is ready; PostNL-ID is a different account object |
| Omniva parcel machine | The tracking number is not the locker-door code |

These are scoped examples, not instructions for every country or service. Open the official support page for the exact carrier division and location shown on your shipment.

## Know when this is no longer a credential problem

Leave this guide when another fact becomes central:

| What you now know | Use instead |
|---|---|
| The parcel is not officially Ready | Available for Pickup or Tracking Not Updating |
| The pickup location or control action was unexpected | Package Rerouted, Held, or Picked Up Without Permission |
| The compartment opened but was empty or contained the wrong parcel | Parcel Locker Empty or Marked Collected |
| Tracking says Collected but the legitimate recipient did not collect | Unauthorized-pickup or empty-locker guidance |
| The location is closed, full, moved, unsafe, or physically inaccessible | Pickup-location problem guidance when published |
| The holding period ended or return started | Missed-pickup-deadline or return guidance when published |
| Name, ID, age, or alternate-collector authorization is the main barrier | Pickup-ID or authorized-collector guidance when published |
| A functional accessibility barrier is central | Package Delivery and Pickup Accessibility Needs |
| You want to move or reroute the parcel | Change Delivery Address, Reroute, Hold, or Intercept |
| A message or release link looks suspicious | Fake Delivery Text, Email, Fee, or Tracking Link |

A credential failure does not prove that the parcel is missing, that someone collected it, that the locker was compromised, or that the deadline was extended.

## Keep the credential private

A pickup credential can authorize physical release. Treat it more like an access key than an ordinary tracking update.

Do not:

- publish or send it to an unknown support account;
- upload a QR or barcode screenshot;
- forward an unsolicited “retrieve your code” link;
- try codes from another parcel;
- guess missing digits;
- reuse an old credential;
- share account screenshots containing personal details;
- force, pry, reopen, or hold a compartment;
- tamper with the scanner or keypad;
- enter staff-only areas;
- impersonate the named recipient;
- bypass ID, age, signature, or authorization controls.

Some operators provide a formal in-app delegation or authorized-collector method. Use that exact process when available. A carrier-specific delegation feature does not make informal code forwarding safe or valid everywhere.

Open the official carrier or operator app or website independently rather than relying on an unexpected message link. If a message asks for payment, identity data, or account credentials to “restore” locker access, verify it through the official channel and use [Fake Delivery Text, Email, Fee, or Tracking Link](/package-problems/fake-delivery-message/).

## What 11Tracking can and cannot establish

11Tracking can help you organize public tracking events and distinguish:

- routed versus physically received at the location;
- received versus Ready;
- Ready versus credential generated;
- notification versus credential delivered;
- credential displayed versus accepted;
- access accepted versus correct parcel present;
- collection record versus named-recipient possession.

11Tracking and USTracking cannot:

- generate, retrieve, resend, validate, or apply a pickup code, PIN, QR, barcode, or digital key;
- authenticate the recipient, account, phone, email, device, ID, or collector;
- open or remotely control a locker;
- access private operator, merchant, account, terminal, or collection logs;
- change the pickup location or contact data;
- extend the holding period;
- contact the carrier, locker operator, merchant, marketplace, or pickup point;
- recover the parcel;
- determine theft, compromise, or legal responsibility from a failed credential.

The safest next step is the least invasive official action that matches the exact failed layer—readiness, release model, issuer, account, credential, terminal, location, identity, accessibility, or physical parcel outcome.

## Use the companion app when it helps

USTracking is the companion mobile app for 11Tracking and can keep active shipment history available on your phone.

USTracking can organize supported public shipment events and monitor later recorded updates. It cannot generate, retrieve, resend, validate, or apply a pickup credential; authenticate a recipient; open a locker; change contact data; extend a holding period; contact a carrier, locker operator, merchant, or pickup point; or recover a parcel.

- [Google Play](https://play.google.com/store/apps/details?id=com.smartaistudio.ustracking)
- [App Store](https://apps.apple.com/us/app/ustracking-package-helper-ai/id6749468345)

## Official sources and actions

- [InPost UK: I Didn't Receive My Collection Code](https://inpost.co.uk/help/i-didnt-receive-my-collection-code)
- [InPost UK: My QR Code or Label Won't Scan at a Locker](https://inpost.co.uk/help/my-qr-code-or-label-wont-scan-at-a-locker)
- [InPost UK: How Long Do I Have to Pick Up My Parcel?](https://inpost.co.uk/help/how-long-do-i-have-to-pick-up-my-parcel)
- [DHL Paket Germany: Assistance With the Pick-Up Code](https://www.dhl.de/en/privatkunden/hilfe-kundenservice/packstation/abholcode.html)
- [PostNord Sweden: Collect Parcels From Parcel Lockers](https://www.postnord.se/en/private/paketboxar/collect-parcels-from-parcel-lockers/)
- [Packeta: Z-BOX](https://www.packeta.com/zbox)
- [Packeta: How to Use the Packeta Mobile App](https://blog.packeta.com/how-does-packeta-mobile-app-work/)
- [Australia Post: Parcel Lockers](https://auspost.com.au/personal/receiving/parcel-deliveries/parcel-lockers)
- [UPS: ID Requirements for Collecting a Parcel From a UPS Access Point](https://www.ups.com/es/en/support/shipping-support/id-requirements-for-tendering-shipment)
- [UPS Netherlands: UPS InfoNotice](https://www.ups.com/nl/en/support/tracking-support/where-is-my-package/how-to-use-infonotice)
- [FedEx: Hold at Location](https://www.fedex.com/en-us/shipping/hold-at-location.html)
- [Canada Post: Manage Your Mail and Packages](https://www.canadapost-postescanada.ca/cpc/en/personal/manage-mail.page)
- [Canada Post: Flexible Delivery Options](https://www.canadapost-postescanada.ca/cpc/en/support/articles/parcel-services-shipping-in-canada/flexible-delivery-options.page)
- [Canada Post: Implement Deliver to Post Office on Your Site](https://www.canadapost-postescanada.ca/cpc/en/support/kb/business/deliver-to-post-office/deliver-to-post-office-implementing-on-your-site.page)
- [La Poste: I Don't Have the Pickup Code for a Parcel in a Locker—What Should I Do?](https://aide.laposte.fr/contenu/je-n-ai-pas-le-code-de-retrait-pour-recuperer-mon-colis-dans-une-consigne-que-faire)
- [DPD Poland: DPD Pickup Parcel Lockers](https://www.dpd.com/pl/en/dpd-polska-parcel-lockers/)
- [DPD Netherlands: I Have Not Received a Collection Code](https://www.dpd.com/nl/en/faq/i-have-not-received-a-collection-code-to-collect-the-parcel-what-should-i-do/)
- [PostNL: Pakket- en Briefautomaat](https://www.postnl.nl/ontvangen/pakket-ontvangen/pakket-en-briefautomaat/)
- [Omniva Estonia: The Parcel Machine Locker Door Code Doesn't Work](https://www.omniva.ee/help/the-parcel-machine-door-code-doesnt-work)

## Related 11Tracking guides

- [What Does “Available for Pickup” Mean?](https://11tracking.com/tracking-status/available-for-pickup/) — Confirm pickup readiness, location rules, ID requirements, and hold deadlines before collecting.
- [Package Rerouted, Held, Redirected, or Picked Up Without Permission](https://11tracking.com/package-problems/package-rerouted-held-or-picked-up-without-permission/) — Verify an unexpected delivery change, protect accounts, and route the right carrier or purchase case.
- [Package Delivery and Pickup Accessibility Needs](https://11tracking.com/delivery-actions/package-delivery-and-pickup-accessibility-needs/) — Match a delivery or pickup access barrier to the controlling actor, compatible official alternative, evidence, and complaint route.
- [Can I Change a Package Delivery Address, Reroute It, Hold It, or Intercept It?](https://11tracking.com/delivery-actions/change-delivery-address-reroute-or-hold/) — Check whether a change, hold, reroute, or intercept option may be available and how to confirm later events.
- [Who Should I Contact About a Package?](https://11tracking.com/delivery-actions/who-to-contact-about-a-package/) — Identify whether the seller, shipper, or carrier controls the next package action.
- [Official Carrier Support Directory](https://11tracking.com/carrier-support/) — Find the correct official carrier support channel for your shipment without guessing links.
- [Is This Delivery Text, Email, Fee, or Tracking Link a Scam?](https://11tracking.com/package-problems/fake-delivery-message/) — Verify a suspicious delivery text, fee request, or tracking link without using the message.

### More related guides

- [Full, Closed, Changed, or Unusable Locker or Pickup Point](https://11tracking.com/package-problems/locker-or-pickup-location-inaccessible-or-changed/) — Verify which point physically holds the parcel, whether Ready and usable, who controls redirection, and the active deadline.

[Browse all Package Help guides](https://11tracking.com/package-help/)