LBC Express Tracking

Start with the right LBC object

LBC uses several numbers and references across parcel, ecommerce, disposition, and money services. They are not interchangeable.

This distinction matters because even LBC's current regional pages do not describe one global number format. A Canada-path FAQ describes 12–17 digits for Philippine domestic cargo and normally 5 digits for international cargo, while the same page also tells web users to enter a valid 12-digit number. A U.S. shipping FAQ describes 12 digits for domestic and international packages, while a UAE FAQ describes 5 digits. These examples prove variation; they are not a format-validation rule for every LBC shipment.

If the official lookup says the number is invalid or cannot be found, first verify that you copied the shipment number—not a booking, remittance, disposition, order, or payment reference. Then use How to Find and Verify a Tracking Number or Tracking Number Not Found rather than guessing from length alone.

Does LBC physically have the parcel?

Treat possession as an evidence question, not as a consequence of a booking or number existing.

The current inbound-to-Philippines contract also uses the concept of LBC having a record of tender when discussing loss. It does not define one universal public status label that means “physical acceptance” for every LBC product. Do not invent one.

If all you have is an electronic or pre-handover record, compare the boundary with Label Created, Carrier Received Package, and Dropped Off but Not Scanned. If strong LBC possession evidence already exists and the record then stops changing, move to Tracking Not Updating.

Failed delivery, disposition, and branch pickup are separate states

The current Philippines Domestic Disposition Form can expose these requests for eligible shipments:

• Return to Shipper;
• re-deliver to the same address;
• transfer for branch pickup;
• retain at the pickup location.

The form also places conditions around those actions. It says re-delivery or transfer to the nearest branch is limited to the same area/city unless the relevant fee is settled at the origin branch, and it distinguishes Return to Shipper fees by product. These are current Philippines disposition rules, not a promise that every LBC shipment can use every option.

Most importantly:

disposition request submitted
≠ parcel physically rerouted
≠ redelivery completed
≠ parcel returned
≠ branch pickup ready

A successful form submission establishes a request record. The next decisive evidence is the corresponding physical routing, branch-readiness, delivery, or return outcome.

The same evidence rule applies to branches. An LBC branch can exist without a specific parcel being assigned there, physically present there, ready for release, or collected. For a generic collection state after the carrier has actually established readiness, use Available for Pickup.

The reviewed LBC first-party material does not establish one portable LBC-wide delivery-attempt count. If the latest carrier event is an unsuccessful attempt, interpret the event actually shown and then look for the next attempt, pickup, disposition, or return evidence. For the generic status meaning, use Delivery Attempted.

Cash on Pick Up is a special ecommerce lane

Cash on Pick Up (COP) should not be used as the model for every LBC branch pickup.

In the current LBC COP flow, the seller specifies branch pickup details and LBC notifies the customer by SMS when the item is ready for pickup. LBC separately notifies the seller after the item has been paid for. Buyer payment and seller settlement remain separate evidence states.

Keep the evidence chain separate:

COP branch selected
≠ item ready for pickup

ready-for-pickup SMS
→ readiness evidence

buyer collection / payment
≠ seller settlement completed

seller payment reference or settlement state
≠ merchant refund or product-dispute outcome

LBC's ecommerce material also uses a separate Branch Collect tracking/reference number for the payment side. Do not use that reference as if it were the parcel tracking number.

COD/COP carrier evidence does not decide whether the seller is legitimate or whether a buyer is entitled to a refund, replacement, or marketplace remedy. LBC's own COD safety guidance tells buyers to verify sellers separately and warns against suspicious messages asking for personal or bank information. A valid-looking LBC shipment record is therefore not seller authentication.

What Delivered and POD can prove

Do not apply one recipient rule to every LBC contract.

The current root-looking LBC terms are actually scoped to goods transported to the Philippines. In that contract, LBC requires the consignee to present a valid government-issued ID at delivery and sign a Proof of Delivery (POD), and the POD may be provided to the shipper on request.

A separate live LBC cargo-terms surface uses a different recipient model: it says the shipment may be released at the address to another person of sufficient age and discretion when the consignee is absent.

That means the safe public conclusion is:

Delivered / POD
≠ universal proof that the named consignee personally received every LBC shipment

POD / signature
≠ proof that the contents were correct
≠ proof that concealed damage did not exist
≠ merchant refund decision

If the carrier record says Delivered but the parcel is missing, use Delivered but Not Received. If you need to understand an official photo, signer, signature, or POD object, use Proof of Delivery, Photo, or Signature. If the proof itself conflicts with the delivery facts, use Challenge an Incorrect Proof of Delivery.

LBC's Privacy Policy treats proof-of-delivery photos and shipment/contact information as personal-information objects. Do not post POD photos, signatures, IDs, addresses, or other private proof publicly just to ask what a tracking state means.

There is no single LBC claim deadline

LBC first-party contracts publish different clocks for different markets, events, claimant roles, and process objects. The applicable contract and trigger matter more than the brand name alone.

A useful example is the current U.S. LBC terms, which place the written-notice duty on the shipper:

Those numbers are not Philippines claim deadlines and are not universal LBC rules.

There is another 90-day figure in the current inbound-to-Philippines terms, but it concerns the treatment of a refused or unclaimed shipment after notice when no further shipper instructions are received. That is a different process object, not a universal 90-day claim clock.

Once the question becomes claim eligibility, required evidence, or formal case status rather than LBC-specific status interpretation, move to How to File a Package Claim or Carrier Investigation Open, Pending, Closed, or No Resolution.

International LBC timing and customs need their own clock and actor

Do not assume every international LBC delivery estimate starts when the parcel is first picked up.

The current LBC contract for goods transported to the Philippines says its sea-delivery commitment is based on the expected vessel departure date, not the pickup time. That is a scoped international cargo rule, not a global ETA formula for every LBC air, sea, courier, or country lane.

For cross-border shipments under that same contract, LBC says the shipment must clear destination customs before delivery. It also allows LBC, where necessary and permitted, to act as a customs-clearance agent, nominal consignee, and coordinator of a customs broker.

That does not make LBC the government customs decision-maker. For Philippine Balikbayan-box processing, the Bureau of Customs describes the documents moving through the consolidator/freight forwarder to BOC, with BOC examination and applicable duties/taxes preceding release for delivery.

Keep the actors separate:

LBC transport / clearance assistance
≠ government Customs decision

customs processing
≠ customs release

customs release
≠ later carrier movement or final delivery

If the unresolved job is now a generic customs hold rather than an LBC-specific carrier question, use Customs Processing or Package Stuck in Customs.

Use the next decisive evidence instead of guessing

When an LBC state is ambiguous, ask what observable record would actually change the conclusion.

A return scan and a refund are different systems. If the parcel has already been returned but the commercial remedy is missing, use Returned Package Received but Refund Has Not Arrived.

Protect shipment and payment data

Use the minimum private data required inside the relevant official LBC, merchant, marketplace, payment, or customs workflow. Do not post or send to 11Tracking a real:

• tracking number;
• disposition reference code;
• remittance transaction/tracking number;
• Branch Collect or payment reference;
• PIN or other release credential;
• government ID;
• address or phone number;
• POD signature or photo;
• invoice, customs document, or identity document;
• bank or payment details.

11Tracking can help interpret supported public tracking events and evidence boundaries. It cannot create or backfill LBC scans, contact LBC, a branch, courier, seller, marketplace, broker, or Customs on your behalf, submit a disposition request, reroute or release a shipment, retrieve private POD, file a claim, clear customs, issue a refund, or guarantee delivery or compensation.