← All supplier integrations
Global enterprise connectivity

Level 3 / Lumen
order orchestration.

Support legacy Level 3 references and current Lumen delivery workflows through the commercial route available to your organisation.

Connector familyEthernet & enterprise connectivity
Interface routeAPI, EDI or portal
Primary scopeGlobal enterprise services
What can be orchestrated

A consistent workflow around supplier-specific rules.

OrderMesh connects the repeatable work across qualification, ordering, fulfilment, exception handling and downstream handoff.

  • Capture site, bandwidth, resilience, access-tail and service-class requirements.
  • Coordinate qualification, budget pricing and formal quote or survey stages.
  • Map customer-facing offers to supplier product codes, terms and technical attributes.
  • Submit orders through API or EDI, or coordinate a guided portal task inside the same workflow.
  • Track survey, wayleave, delivery, testing and ready-for-service milestones.
  • Reconcile supplier status with CRM, project, billing and customer-facing timelines.
Integration coverage
  1. 01

    Global enterprise services

  2. 02

    Legacy reference migration

  3. 03

    Quote-to-handover orchestration

  4. 04

    Connected milestones, exceptions and downstream billing handoff

Example implementation

From validated demand to a billing-ready service.

This workflow shows how OrderMesh connects the supplier journey from initial qualification through delivery, activation and downstream handoff.

  1. 01

    Scope

    Capture both sites, bandwidth, resilience, handoff and required service dates.

  2. 02

    Qualify

    Request availability or create a governed survey and quotation task.

  3. 03

    Approve

    Record the selected design, term, charges and any wayleave or construction decision.

  4. 04

    Order

    Submit through the connected route and preserve supplier and internal references.

  5. 05

    Deliver

    Track survey, build, access-tail, testing and ready-for-service milestones.

  6. 06

    Handover

    Store service details, complete operational acceptance and trigger billing readiness.

Worked scenarioLevel 3 / Lumen

Example: add a new site to a legacy estate

An enterprise has existing Level 3-labelled circuits and needs a new Lumen-routed site added to the same customer solution.

Operational outcome

OrderMesh preserves legacy service references, applies the current product mapping to the new order and presents both on one customer delivery view.

Connected data flow

Know what goes in—and what comes back.

OrderMesh keeps the customer order, supplier references and operational events aligned throughout fulfilment.

OrderMesh sends
  • A-end and B-end site details
  • Bandwidth, bearer and service class
  • Resilience and diversity requirements
  • Term, target date and commercial references
  • Site contacts and access restrictions
  • Technical handoff and demarcation details
OrderMesh receives
  • Availability and quote reference
  • Survey or wayleave requirement
  • Excess construction charge decision
  • Committed delivery date
  • Build, test and handover milestones
  • Service identifier and completion evidence
Typical scope for this route
  • Global enterprise services
  • Legacy reference migration
  • Quote-to-handover orchestration
Designed for the awkward cases

Failures become owned work, not silent drift.

OrderMesh classifies whether an action is safe to retry, needs a supplier lookup or needs a person. It never assumes a timeout means the supplier did nothing.

  • A survey changes the available design or delivery estimate.

  • Excess construction charges require customer approval.

  • A wayleave or landlord dependency blocks the committed plan.

  • One access tail is delayed on a multi-site or resilient service.

  • Testing fails or the handoff details do not match the approved design.

Connect the route

Bring Level 3 / Lumen into one complete order journey.

Connect products, orders, supplier milestones, exceptions and downstream systems through one operational workflow.

Plan this integration →
Level 3 / Lumen questions

What teams usually need to know.

What does the Level 3 / Lumen integration cover?

The core scope includes Global enterprise services, Legacy reference migration, Quote-to-handover orchestration, with supplier events connected to the wider OrderMesh order journey.

Which interface does OrderMesh use?

The integration route is “API, EDI or portal”, connecting the supplier workflow to a consistent OrderMesh order record.

Can it update our CRM, billing and customer communications?

Yes. Qualification results, order references, milestones, activation and exceptions can be mapped into the systems and communication flows used by your operation.

What happens when the supplier status is uncertain?

OrderMesh preserves the unknown outcome, performs a safe status lookup or reconciliation, and prevents a blind duplicate submission. A person is assigned when the state cannot be resolved automatically.

Book a demo