← All supplier integrations
Wholesale connectivity

Entanet
order orchestration.

Bring Entanet-labelled wholesale orders, service references and migration workflows into one connected operational view.

Connector familyWholesale access & broadband
Interface routePartner interface or portal
Primary scopeLegacy catalogue mapping
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.

  • Qualify an address or service identifier against the products your agreement exposes.
  • Map a sellable OrderMesh offer to the supplier product, speed, term and installation options.
  • Submit provide, modify, cancel and cease commands through the connected supplier interface.
  • Capture appointment choices and keep committed dates visible to operations and customers.
  • Normalise supplier milestones, delays and action-required messages into one order timeline.
  • Reconcile open orders so missed callbacks or portal-only changes do not become invisible.
Integration coverage
  1. 01

    Legacy catalogue mapping

  2. 02

    Partner portal orchestration

  3. 03

    Migration and reconciliation

  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

    Qualify

    Validate the address and return only products permitted by the operator’s agreement.

  2. 02

    Configure

    Map the selected offer, access attributes, contract term and installation choices.

  3. 03

    Validate

    Check required customer, address, migration and appointment data before submission.

  4. 04

    Submit

    Send one idempotent provide request and preserve the supplier reference and payload hash.

  5. 05

    Track

    Translate callbacks or polled updates into a consistent OrderMesh milestone timeline.

  6. 06

    Complete

    Confirm activation, trigger downstream billing and retain a full evidence trail.

Worked scenarioEntanet

Example: migrate an existing wholesale order book

An operator has open and active services stored under historic Entanet product and order references.

Operational outcome

OrderMesh imports the references, reconciles them against the current partner route and keeps new commands blocked until each product mapping is approved.

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
  • Customer and service address
  • UPRN, line or service identifier
  • Chosen product, speed and term
  • Installation and appointment preference
  • Migration, number or access details where relevant
  • Internal order and customer references
OrderMesh receives
  • Qualification and availability result
  • Supplier order and circuit references
  • Appointment confirmation or amendment
  • Committed date and milestone changes
  • Delay, rejection or action-required reason
  • Activation, cancellation or cease outcome
Typical scope for this route
  • Legacy catalogue mapping
  • Partner portal orchestration
  • Migration and reconciliation
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 product disappears between qualification and commit.

  • An appointment slot is no longer available when the order is submitted.

  • The supplier times out after accepting a request, leaving the outcome unknown.

  • A callback is duplicated, delayed or arrives out of sequence.

  • A cancellation or cease is rejected and needs an operational decision.

Connect the route

Bring Entanet into one complete order journey.

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

Plan this integration →
Entanet questions

What teams usually need to know.

What does the Entanet integration cover?

The core scope includes Legacy catalogue mapping, Partner portal orchestration, Migration and reconciliation, with supplier events connected to the wider OrderMesh order journey.

Which interface does OrderMesh use?

The integration route is “Partner interface 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