A discovery brief from Enmovil for
HOYA × Life Care US

Three realities.

One orchestration surface.

Asia origins under shifting reciprocal-tariff regimes[3]. A US footprint that spans Lewisville, Ramsey, Montvale, Irvine, Milpitas, plus a 20-lab Rx finishing network[4]. Three customer-flow shapes: eye care practitioners, hospitals and clinics, ambulatory surgical centers. The orchestration surface itself is the strategic challenge.

Anchor: HOYA Life Care operating-margin commitment, restored to the 20% benchmark[1]. The execution loop across the surface is where the math gets made.

The shape, named

What we've read.

One inbound. Three strands. Twenty US nodes in between.

ASIA ORIGINS Ayutthaya, TH 15% reciprocal · optical Hanoi, VN 20% baseline · medical Cebu, PH 19% reciprocal · medical Seoul, KR high-index lens manufacture + Jakarta, Shenzhen US FOOTPRINT Lewisville, TX Vision Care HQ + lab Ramsey, MN Vision Ease ATC · 70K sqft Montvale, NJ PENTAX Medical Americas Irvine, CA HOYA Surgical Optics Milpitas, CA Holdings America HQ + 18 labs STRAND 01 · OPTICAL Lab → ~50K independent eye care practices parcel-dominant · UPS-led · HOYA Hub real-time STRAND 02 · MEDICAL DC → hospital, GI clinic, ENT practice capital equipment + consumables + service · serial-traceable STRAND 03 · SURGICAL Hub → ambulatory surgical + ophthalmologist channel sterile preloaded · FDA serial-traceable
Inbound landed cost Thailand 15% · Vietnam 20% · Philippines 19% · China ~35% on general optical components[3][10]. Stepped up vs pre-2024 baseline.
Footprint Lewisville, Ramsey, Montvale, Irvine, Milpitas plus 18 finishing labs.
Outbound Three customer-flow shapes. Eye care practitioner parcel, hospital capital, surgical sterile.
State Spread across HOYA Hub, lab tools, carrier portals, system-of-record.
Commitment vs reality

The gap.

Not a planning gap. Not a stack-modernization gap. An execution-loop visibility gap.

Hypothesis: across an envelope where three customer-flow shapes share one inbound and one freight-and-procurement governance, there is no execution-loop view that survives a disruption, audits a carrier invoice, and surfaces SLA compliance per endpoint in real time.
17.3%[1] post-disruption reality
+2.7 pts to recover
20%[1] Life Care benchmark
Three levers Caddie touches in the procurement and transportation function
01

Freight audit

Per-invoice cost band. Recover variance across the carrier mix.

02

Lane orchestration

Per-mode spend variance across parcel, less-than-truckload, courier.

03

SLA telemetry

Per-endpoint exception cost. Catch the slip before the chargeback.

20%[1]
Life Care operating-margin benchmark. The level the team is measured back to.
20[4]
US prescription finishing labs across the network. One unified governance, for the first time.
3
Customer-flow shapes: practitioner parcel, hospital capital, surgical sterile.
~50K
Independent eye care practices on the optical strand. Parcel-dominant outbound.

This is a hypothesis, not a characterization. We'd love to test it against your measured state.

Three forcing functions

Why now.

Three factors that make this an FY26 problem, not an FY28 one.

01

Cost basis · stepped up

Thailand 15%, Vietnam 20%, Philippines 19%, Korea reciprocal, China ~35% on general optical components. Every freight dollar matters more than it did a year ago.

USTR US-Vietnam framework agreement, Oct 2025 · Lexology Thailand-US tariff update, Feb 2026 · Goldman Sachs HOYA upgrade on tariff clarity.

02

Audit layer · regulatory floor turning competitive surface

FDA-grade serial traceability is now a customer expectation in the medical and surgical channels. Real-time order state is now a customer expectation in the optical channel. The audit layer is being demanded outward, not just enforced inward.

FDA Unique Device Identification rule · HOYA Hub real-time tracking exposure to eye care practices.

03

Tech · the missing layer

The stack runs. Sage X3, HOYA Hub, the 20 lab tools, the carrier portals. Each one runs cleanly, none of them see across each other. Caddie operates the orchestration layer above them.

HOYA Hub launches customer-facing tracking · NA leadership realignment confirms governance · the cross-stack visibility layer is what's not yet on the surface.

If this is half-right, it's worth a working session.

Where fit could live

The leverage.

Start small. Roll out by demonstrated success.

Outside-in read

The math of complexity is the strategic challenge. The audit layer is where it compounds.

What "scaled" would look like

  • Every lane, every mode, every invoice on one orchestration view.
  • Per-endpoint SLA telemetry across the strands, audit-trail intact.
  • Exception response in hours, on the strand the customer feels first.

The replication surface

Start with the optical strand. Medical and surgical follow by demonstrated success.

One Asian origin. One US lab. Sixty-day measurable window.

01 · OPTICAL · START
Ayutthaya, TH[13] Lewisville, TX[4] ~50K eye care practices
parcel-dominant · UPS-led · HOYA Hub real-time[6]
02 · MEDICAL
Hanoi · Cebu Montvale, NJ Hospital · gastroenterology · ENT
03 · SURGICAL
Hanoi · Asia Irvine, CA Ambulatory surgical · ophthalmologist
If this works on the optical strand, the audit-layer playbook ports to medical and surgical without a re-platform.
One platform, every decision layer

What Enmovil is.

The intelligence layer that sits above your stack, not in place of it.

PREDICT

Available for expansion

  • Forecast & Demand Intelligence
  • Inventory Planning & Optimisation
  • Scenario Modelling · S&OP
  • Warehouse & Node Operations

PLAN

Available for expansion

  • Dispatch & Route Optimisation
  • 3D Load Building
  • Network & Capacity Planning
  • Carrier Allocation

EXECUTE

Best-fit wedge for this conversation

  • Multimodal Orchestration (Parcel · LTL · OTR · Ocean · Air)
  • Control Tower & Resilience
  • Freight Audit & Settlement
  • ePOD · Audit-grade Lane Telemetry
CADDIE AI: the cross-suite intelligence layer spanning Predict, Plan, and Execute. Conversational. Agentic. Sits above Sage, SAP, Oracle, MS Dynamics.
25+ Fortune 100 customers · 150+ team · 10+ years · ISO 27001 · SOC 2 Type II · SAP / Sage / Oracle-ready · AI-native
The stack view

CADDIE AI above your stack, not in place of it.

The cross-suite intelligence layer your transportation and procurement leads actually talk to.

CADDIE AI · conversational · agentic · cross-suite
Predict
Plan
Execute
Your system of record · Sage X3 · SAP · Oracle · HOYA Hub · lab-level tools
Plant · Lab · Carrier · Endpoint signals, real-time
The personalized brain for your supply chain orchestration.
Self-sensing. Self-deciding. Self-optimizing. Sense → decide → act, inside governed boundaries. One command, end-to-end coordination across your existing stack.
caddie.enmovil.ai · Logistics Copilot
online
You · Procurement, Monday morning

Caddie, recap the weekend's Rx outbound from the lab network.

Caddie

Here's the read.

  • 312 Rx orders shipped from 20 labs over the weekend.
  • 96.4% on-SLA · 11 lanes flagged for variance.
  • Concentration: Lewisville → Pacific Northwest, UPS hub miss, average 6-hour delay.
  • 4 doctor accounts crossed the 2-miss threshold this month. Proactive-outreach list drafted.
  • Routing alternative ready: shift Lewisville → PNW lanes to FedEx for 30 days.
  • Audit packet logged · awaiting your approval.
No rip and replace. Sage stays. SAP stays. HOYA Hub stays. Caddie queries across them in your language.
For a longer conversation

Questions we'd love to explore together.

What we'd want to understand if we had a longer conversation.

Current state · the optical strand

  • From a Lewisville or Ramsey lab to a small eye care practice in California, how many of those milestones does your team see in real time, and how many are reconstructed from a UPS invoice the next morning?
  • When a parcel misses an SLA window today, how long before the planner who can reroute it knows, and what does that response actually look like?

Network & lanes · inbound discipline

  • Across the Asian origins, where is per-lane cost variance highest in the current quarter, and how is it being absorbed at the new tariff cost basis?
  • If you could compare per-mode, per-carrier invoice variance across the 20-lab network for sixty days, which lane would you pick first?

Governance & stack

  • Where does the cross-strand order, freight, and settlement state currently live as a single view, if anywhere, today?
  • Inside the unified transportation-and-procurement function, what's the first SLA or cost number you'd want a control tower to surface in week one?

Forward · expansion

  • If the optical strand deployment proves the pattern, which strand expands first, the medical hospital channel or the surgical ambulatory channel, and what's the threshold proof?
  • What would a sixty-day visibility experiment have to demonstrate for it to be worth a deeper conversation across all three strands?
Who's building this

Enmovil · the technology thought partner for autonomous supply chains.

One AI-native platform. Demand sensing, inventory, dispatch, execution, freight settlement, sustainability reporting. All on one intelligence layer that sits above the systems you already own.

Under orchestration
~100K
Trucks per day across the customer base
Daily ETA accuracy
99%
Road, rail, ocean, air
Forecast accuracy
97%
Demand sensing on deployed customers
Logistics cost savings
8 to 15%
Measured across deployments
Integration
3 to 4wks
On existing SAP, Oracle, TMS, WMS. No migration.
Deployed at
Dispatch Planning
Multimodal Logistics
Multimodal Orchestration
Dispatch Planning
Fleet Management
Logistics Orchestration
Logistics Resilience
Inventory Management
Freight Settlement
Dispatch Planning
Transport Management
Export Planning
Runs under GDPR and SOC 2. Data ingestion via API, EDI, or bulk upload. Enterprise SSO. Deploys over existing SAP ECC 6.0 and above.
For our session

One orchestration surface, three strands. Sixty to ninety minutes together, used well.

Three things we'd want to land in our session.

01

A lane read

Walk one Asian origin to one US lab to the eye care practitioner outbound, sixty days, audit-grade. What lane variance lives there today, what the unified governance can see in week one.

02

A stack read

Where Caddie sits relative to Sage, SAP, HOYA Hub, lab tools. No rip and replace. Where the audit layer plugs in across the optical, medical, and surgical strands.

03

A co-drafted hypothesis

One page, your team and ours. Where the start-small deployment lands, what success on the optical strand earns the medical and surgical expansions, and what "no fit" looks like.

Three questions we'd love to discuss

Of the three strands, which one would you want to test the execution-loop hypothesis on first?

Where does the stepped-up landed cost worry your team most today?

For our session on the execution gap to reach a real verdict, who else should join?

Reference · the full surface in one view

For your IT and procurement counterparts. The capability, integration, and governance surface in one panel.

Capability surface

Predict

  • Forecast & demand intelligence
  • Customer demand signal ingestion
  • Inventory planning & optimization
  • Scenario modelling · S&OP
  • Warehouse & node operations

Plan

  • Dispatch & route planning
  • 3D vanning & load building
  • Network & capacity planning
  • Automated carrier tendering
  • Port & global traffic signals

Execute

  • Multimodal orchestration · parcel, less-than-truckload, OTR, ocean, air
  • Control tower & resilience
  • Real-time fleet telemetry & driver alerts
  • Dynamic route optimization · risk-based rescheduling
  • Freight audit & settlement · ePOD telemetry
  • Autonomous exception handling

Connectors & integration

  • ERP Sage X3 · SAP S/4HANA · SAP ECC · Oracle · MS Dynamics · JD Edwards
  • Operational WMS · TMS · telematics adapters · HOYA Hub-class portals
  • Interfaces REST · GraphQL · webhooks · pluggable optimizers / language models
  • Data exchange EDI 856 · 810 · 214 · API · bulk upload
  • Identity Enterprise SSO · SAML · SCIM
  • Tooling Protocol-based tool calls for safe agent extensibility

Governance & data

  • Compliance ISO 27001 · SOC 2 Type II · GDPR
  • Residency regional data residency · tenancy isolation
  • PII discovery · minimization · masking / tokenization · DLP
  • Audit immutable action logs · approval lineage · audit-grade exports
  • Retention configurable retention rules per data class