***

## title: Workflow Summary

Rendr orchestrates the full lifecycle of a delivery — from creation through fulfilment, monitoring, and resolution.

<CardGroup cols={2}>
  <Card title="API Reference" icon="duotone code" href="/api-reference">
    For endpoint definitions and field-level details.
  </Card>

  <Card title="Status Lifecycle" icon="duotone arrows-spin" href="/documentation/key-concepts/status-lifecycle">
    For detailed state transitions.
  </Card>
</CardGroup>

***

## System Overview

Every delivery in Rendr is a state-driven object that moves through a well-defined lifecycle.

<CardGroup cols={3}>
  <Card title="State-Driven" icon="duotone arrows-spin">
    Progresses through a deterministic state machine from creation to completion.
  </Card>

  <Card title="Orchestrated" icon="duotone diagram-project">
    Evaluated by Rendr's orchestration engine at every key decision point.
  </Card>

  <Card title="Carrier-Executed" icon="duotone truck">
    Fulfilled via one or more carrier or fleet models.
  </Card>

  <Card title="Continuously Monitored" icon="duotone eye">
    Evaluated in real time for exceptions and SLA health.
  </Card>

  <Card title="Event-Driven" icon="duotone bolt">
    Updated via webhook events as state transitions occur.
  </Card>
</CardGroup>

<Note>
  **Your system creates the delivery. Rendr manages orchestration, carrier execution, and lifecycle progression.**
</Note>

***

## High-Level Flow

```mermaid
flowchart LR
    A[Create Delivery] --> B[Validate & Apply Store Rules]
    B --> C[Orchestration Engine]
    C --> D[Carrier / Fulfilment Selection]
    D --> E[Booking]
    E --> F[Dispatch & Assignment]
    F --> G[Pickup]
    G --> H[In Transit Monitoring]
    H --> I[Delivered]

    H --> J[Exception Detected]
    J --> K[Automation / Reassignment / SOP]
    K --> H
```

***

## Delivery Lifecycle

Deliveries progress through a consistent set of states regardless of the fulfilment model used — from creation through to a final resolved state. For a full breakdown of each status and its transitions, see [Status Lifecycle](/documentation/key-concepts/status-lifecycle).

***

## Fulfilment Models

The orchestration model is consistent across all fulfilment types. Only booking and dispatch behaviour differ.

<CardGroup cols={3}>
  <Card title="Rendr Carrier Network" icon="duotone truck" href="/documentation/key-concepts/fulfilment-models/rendr-carrier-network">
    Rendr selects and manages carriers on your behalf.
  </Card>

  <Card title="Bring Your Own Carrier" icon="duotone box" href="/documentation/key-concepts/fulfilment-models/bring-your-own-carrier">
    Use your own carrier accounts with Rendr's orchestration layer on top.
  </Card>

  <Card title="Own Network" icon="duotone car" href="/documentation/key-concepts/fulfilment-models/own-network">
    Fulfil deliveries using your own staff or internal fleet.
  </Card>
</CardGroup>

***

## Automation Layer

Rendr supports rule-based operational automation layered on top of the delivery lifecycle.

<CardGroup cols={2}>
  <Card title="Reassignment" icon="duotone shuffle">
    Automatically reassign deliveries on failure or SLA breach risk.
  </Card>

  <Card title="Notifications" icon="duotone bell">
    Trigger customer or store communications on key lifecycle events.
  </Card>

  <Card title="Compliance Workflows" icon="duotone shield-check">
    Enforce compliance rules and escalate operational issues.
  </Card>

  <Card title="Oversight" icon="duotone list-check">
    Monitor delivery performance and operational health across your network.
  </Card>
</CardGroup>