Logistics System

MetroLogix.

First-attempt delivery, even when no one is home.

Connecting carrier authentication with condominium access to structurally reduce re-delivery in dense cities.

01The loop
  1. A single parcel

    This is one parcel.

    Follow it through an ordinary afternoon in a Tokyo auto-lock building.

  2. Attempt 01 · 14:23

    Locked out.

    No access code. The intercom goes unanswered. The building stays sealed.

  3. Attempt 02 · 14:41

    Wrong floor.

    The address is ambiguous. 12F or 12A? The driver is left guessing.

  4. Attempt 03 · 15:02

    Nobody home.

    The recipient is out, and there is no safe place to leave it.

  5. 15:18

    Back to the depot.

    The parcel is carried back. Tomorrow, the cycle repeats.

10–15%

of deliveries in Japan are attempted again.

02The handshake

The right access. Nothing more.

  1. 01 / 04 · Identity

    The carrier vouches for the courier.

    Identity stays with the carrier. MetroLogix receives only a signed result — never a face, a fingerprint or an iris.

  2. 02 / 04 · Token

    The parcel carries its own permission.

    A standard QR holds an encrypted Building ID, the exact floor and a delivery window. No names. No room numbers.

  3. 03 / 04 · Access

    The building opens — for one floor.

    A match unlocks the door and lets the elevator accept only the delivery floor. Any other building: access denied.

  4. 04 / 04 · Expiry

    Permission ends with delivery.

    After delivery, the token expires and an auditable log remains. Access is not left open.

03The result

Zero Re-delivery.
Zero Emissions.

Every figure below is a projection from our business plan — the outcome the protocol is designed to deliver, not a measured result.

−30–50%

Re-delivery

Projected reduction. First-attempt delivery becomes the default, not the exception.

+15–25%

Deliveries per driver

Time lost to locked doors and wrong floors goes back into the route.

0

Biometric records held

The carrier proves identity. MetroLogix only receives a signed result.

CO₂ ↓

Fewer repeat trips

Every avoided second attempt is fuel, noise and kilometres the city no longer carries.

3.1Where others fall short

Closing the gaps access tech leaves open.

01

Intercom access

Buzzing a resident who isn’t home is the default failure mode — every miss becomes a re-delivery.

Meldotia’s approach

A signed carrier credential and a time-boxed QR authorize the building’s own API directly.

02

Biometric databases

Centralizing driver face or fingerprint data creates legal, labor and trust liabilities no operator wants.

Meldotia’s approach

Identity proof stays on the carrier’s device. MetroLogix only receives a signed result.

03

Retrofit cost

Legacy buildings can’t justify tearing out working lock hardware, so access-tech pitches stall.

Meldotia’s approach

We start with new construction and partner with vendors on subsidized systems.

3.2Comparative matrix

Structural superiority.

Re-delivery risk

Traditional delivery
High
Delivery locker
Low
MetroLogix
Near zero

Capacity limit

Traditional delivery
None
Delivery locker
Limited
MetroLogix
Unlimited

Security

Traditional delivery
Visual check
Delivery locker
Key code
MetroLogix
Signed token + IoT

Implementation

Traditional delivery
None
Delivery locker
Per location
MetroLogix
Per building*

* Implementation cost varies: lower for new construction with smart infrastructure, higher for retrofits.

04Market opportunity

The scale of waste.

¥180B

Estimated annual cost of re-delivery in Japan.

ILLUSTRATIVE · NEEDS VALIDATION

NOT TO SCALE

TAM

¥24T

Japan’s domestic logistics market

SAM

¥3.2T

Last-mile delivery segment

SOM

¥480B

High-density urban buildings

4.9B

Parcels delivered annually

Japan, estimated

15%

Re-delivery rate

Industry estimate

735M

Failed first attempts

Estimated annually

2.5M t

CO₂ impact

Illustrative

Even capturing a small fraction of re-delivery costs is a significant annual opportunity.

MARKET SIZING IS ILLUSTRATIVE · REQUIRES VALIDATION

05Integration ecosystem

Built to connect.

Designed to plug into Japan’s logistics and real-estate infrastructure. Conceptual partners — not current relationships.

LOGISTICS CARRIERS

YAMATO

ヤマト運輸

SAGAWA

佐川急便

JAPAN POST

日本郵便

SEINO

西濃運輸

REAL-ESTATE DEVELOPERS

MITSUI FUDOSAN

三井不動産

MITSUBISHI ESTATE

三菱地所

SUMITOMO REALTY

住友不動産

TOKYU LAND

東急不動産

MetroLogix

TECHNOLOGY & ACCESS CONTROL

ASSA ABLOY

Smart locks

HITACHI

Elevators

NEC

Authentication

FUJITSU

Cloud

OMRON

Access control

5.1Adoption strategy

Start as a public-private pilot.

Instead of selling separately to carriers, buildings and hardware vendors, connect to logistics-improvement programs that can convene the ecosystem and subsidize early deployment.

01

Strategic partner

Carrier first

The first carrier supplies authentication, validates usage and gives buildings confidence it will be used.

02

Adoption signal

Lower building risk

With a carrier committed, managers and developers can treat MetroLogix as usable infrastructure.

03

Public forum

Government convening

Tokyo or MLIT-aligned pilots bring carriers, real estate, authentication IT and vendors to one table.

04

Certified infrastructure

Move to standards

After validation: subsidies, certified building specs and smart-lock integration requirements.

5.2Systems thinking

The stakeholder equation.

Building developers

Carrier-ready building amenity

Building managers

Fewer delivery complaints and handoffs

Logistics carriers

Reduced re-delivery costs and driver load

Hardware vendors

Authentication-ready modules

Governments

Convening power and subsidy impact

Residents

Reliable package delivery

Carrier participation lowers the adoption threshold for every building.

06Business model

How it could work.

Early revenue comes from buildings and pilots, while carriers act as strategic partners that unlock adoption.

CONCEPTUAL MODEL · NOT FINALIZED

Building SaaS

Initial revenue

Setup fees and monthly fees for building managers

Pilot funding

Public-private

Government pilots and subsidy-backed deployments

Carrier API

Mid-term

Carrier API fees after building coverage grows

Certification

Standardized

Vendor partnerships and certified integration fees

01 · SHORT TERM

Validate with one carrier, one building manager and a small set of properties through setup fees, SaaS and pilot funding.

02 · MID TERM

Introduce carrier API fees only after building coverage and delivery volume make the integration valuable.

03 · LONG TERM

Expand into certified specifications for smart locks, intercoms, elevators and access-control vendors.

Who brings what.

01

Carriers

  • Authentication issuer
  • Device integration
  • Pilot usage data

02

Buildings

  • Setup fee
  • Monthly SaaS
  • Building-system integration

03

Government

  • Convening forum
  • Pilot subsidy
  • Standardization support

04

MetroLogix

  • Auth protocol
  • Ecosystem coordination
  • Audit logs & compliance
07Honest assessment

What could go wrong.

Real challenges we’re thinking through. Building something new means confronting hard problems.

Critical

Coordination problem

Buildings need carrier usage guarantees; carriers need building coverage before integration is valuable.

MITIGATION

Secure one carrier as a strategic partner first, then connect the pilot to a public-private forum.

High

Privacy & data concerns

External databases of driver face or fingerprint data would create heavy legal, labor and trust barriers.

MITIGATION

Keep identity proof inside the carrier or driver device; MetroLogix receives only signed results.

High

Hardware dependency

Despite the software focus, it needs compatible smart locks and building systems. Retrofit costs can be prohibitive.

MITIGATION

Focus on new construction; partner with hardware vendors for subsidized systems.

Medium

Public-sector pace

Government involvement creates credibility, but forums, pilots and budgeting can move slowly.

MITIGATION

Don’t wait for policy. Generate evidence through a small private PoC first.

Medium

Unproven market

Willingness to pay, re-delivery reduction and management workload savings still need field data.

MITIGATION

Measure re-delivery rate, delivery time and resident inquiries across one carrier, one manager and several buildings.

Acknowledging challenges is the first step to solving them.

08Roadmap

Deployment strategy.

Prove the model in a small private PoC, then connect it to Tokyo and national logistics policy.

01

Private PoC

One carrier, one building manager and several properties — measure the impact.

02

Public pilot

Connect to Tokyo / MLIT-aligned logistics programs for funding and convening power.

03

Joint rollout

Bring in major carriers, developers, authentication IT and access-control vendors.

04

Standardization

Expand into subsidies, certification specs and new-building design standards.

CURRENT STATUSConcept stage
03Contact

Let's build
the future together.

We provide strategic incubation and technical direction for visionary projects.