Workflow Summary
Rendr orchestrates the full lifecycle of a delivery — from creation through fulfilment, monitoring, and resolution.
For endpoint definitions and field-level details.
For detailed state transitions.
System Overview
Every delivery in Rendr is a state-driven object that moves through a well-defined lifecycle.
Progresses through a deterministic state machine from creation to completion.
Evaluated by Rendr’s orchestration engine at every key decision point.
Fulfilled via one or more carrier or fleet models.
Evaluated in real time for exceptions and SLA health.
Updated via webhook events as state transitions occur.
Your system creates the delivery. Rendr manages orchestration, carrier execution, and lifecycle progression.
High-Level Flow
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.
Fulfilment Models
The orchestration model is consistent across all fulfilment types. Only booking and dispatch behaviour differ.
Rendr selects and manages carriers on your behalf.
Use your own carrier accounts with Rendr’s orchestration layer on top.
Fulfil deliveries using your own staff or internal fleet.
Automation Layer
Rendr supports rule-based operational automation layered on top of the delivery lifecycle.
Automatically reassign deliveries on failure or SLA breach risk.
Trigger customer or store communications on key lifecycle events.
Enforce compliance rules and escalate operational issues.
Monitor delivery performance and operational health across your network.
