OrderMesh
Book a demo
← All supplier integrations
Wholesale platform & aggregator

Giacom
order orchestration.

Connect Giacom Cloud Market ordering and lifecycle workflows across connectivity, communications, cloud, mobile, hardware and billing products.

Discuss this route See how it works ↓
Connector familyWholesale platform & aggregator
Interface routeCloud Market, partner portal or approved integration interface
Primary scopeMulti-carrier connectivity
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 and compare the carrier and product options exposed by the operator’s wholesale agreement.
  • Map retail offers to the platform catalogue, supplier product code, term, margin and service options.
  • Coordinate connectivity, IP communications, mobile, cloud, hardware and billing dependencies in one order.
  • Submit orders through the integration interface or coordinate a guided Cloud Market task.
  • Normalise platform and underlying carrier references into one customer-facing milestone timeline.
  • Reconcile open orders, service inventory and downstream billing so partial completion remains visible.
Integration coverage
  1. 01

    Multi-carrier connectivity

  2. 02

    IP comms, mobile and cloud

  3. 03

    Cloud Market order 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

    Qualify need

    Capture the customer address, bandwidth, resilience, voice, mobile, cloud and hardware requirements in scope.

  2. 02

    Compare routes

    Request the carrier and product options exposed to the partner through Giacom Cloud Market.

  3. 03

    Map catalogue

    Link the selected option to the approved retail offer, term, margin, hardware and billing treatment.

  4. 04

    Submit safely

    Use the connected integration route or create a guided Cloud Market task without rekeying order data.

  5. 05

    Track delivery

    Join Giacom, underlying carrier, porting and hardware references into one milestone and exception view.

  6. 06

    Activate & bill

    Reconcile every required component, retain completion evidence and release billing only when ready.

Worked scenarioGiacom

Example: qualify and order the best approved connectivity route

A reseller enters a customer address and requirement. Giacom Cloud Market returns the carrier and product options available to that partner, and OrderMesh maps the selected result to the reseller’s retail offer, term, hardware and billing rules.

Operational outcome

The platform order, underlying carrier reference, delivery milestones and any portal-only actions stay on one OrderMesh timeline. Historic DWS or Daisy Wholesale service references remain searchable and are linked to the current Giacom identity during migration.

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, site and service address
  • Selected carrier, product and term
  • Connectivity, voice or mobile attributes
  • Hardware and delivery requirements
  • Commercial and billing references
  • Requested activation and migration details
OrderMesh receives
  • Qualification and product options
  • Platform, order and carrier references
  • Provisioning and delivery milestones
  • Appointment, port or hardware status
  • Rejection, delay or action-required reason
  • Activation and billing-ready outcome
Typical scope for this route
  • Multi-carrier connectivity
  • IP comms, mobile and cloud
  • Cloud Market order 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.

  • The preferred carrier or product changes between qualification and order commit.

  • One component of a bundled connectivity, voice or hardware order is rejected.

  • A portal action succeeds but its confirmation is not reflected in the integration feed.

  • The platform and underlying carrier report different delivery states.

  • A completed service is not yet ready for billing because another required component is outstanding.

Related routes

Explore similar supplier workflows.

View all integrations →
Colt logo

Colt

API, EDI or portal
Exponential-e logo

Exponential-e

Enterprise API or managed integration
FluidOne logo

FluidOne

Partner platform or portal
Connect the route

Bring Giacom into one complete order journey.

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

Plan this integration →
Giacom questions

What teams usually need to know.

What does the Giacom integration cover?

The core scope includes Multi-carrier connectivity, IP comms, mobile and cloud, Cloud Market order orchestration, with supplier events connected to the wider OrderMesh order journey.

Which interface does OrderMesh use?

The integration route is “Cloud Market, partner portal or approved integration interface”, 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