← Use cases
Margin and profit

A carrier was just paid more than the lane supports. Who saw it?

Bicycle watches margin on every order and flags high carrier pay, negative margin and repeated order edits before the transaction closes.

Book a demo Start for free

No credit card required

Before

In a marketplace, margin leaks one order at a time: a carrier paid above the lane, an order edited too often, a price that never covered the cost. Finance finds it at month end.

With Bicycle

Each margin problem is flagged while the order is still open, with the trigger and the impact, and business users set their own route-level alerts.

What happens when a KPI moves.

  1. 01

    Detect

    An order's carrier pay or margin crosses its threshold.

  2. 02

    Explain

    The exact trigger is named, with the order's context and impact.

  3. 03

    Act

    Bicycle recommends a pay or price correction, and finance operations acts before the transaction closes.

  4. 04

    Learn

    Thresholds by mileage band and margin targets tune over time.

40–60%

fewer ad hoc requests to the data team

Seen at: an automotive logistics provider. Read the case study

Everyone can ask. Data & Analytics controls what gets trusted, published, and acted on.

Runs on
  • Orders
  • Carrier bids
  • Pricing
  • Mileage bands
Used by
  • Finance operations
  • Operations leadership

Common questions

How do you spot overpaying a carrier on an order before the deal closes?
Bicycle checks every order event against a set of margin patterns: a single carrier pay increase above threshold, pay per mile above the mileage-band ceiling, a large negative margin, a zero-day margin violation, several pay edits in one day, and orders executives have not reset. Bicycle classifies each alert and names the trigger and the responsible executive.
What order data does margin alerting need, and can it run during a data migration?
Bicycle runs on your order-lifecycle event stream, with mileage bands, carrier tiers, customer types, lane adjacency and the bidding lifecycle already modeled. If you are moving to a new data system, Bicycle can ingest from both the old and new sources during the transition, so alerts do not wait for the migration to finish.
Who approves a carrier pay correction?
Bicycle sends each alert to the team that owns it: finance operations for margin alerts, and the executive on the order for order resets. Bicycle makes recommendations, not autonomous changes, bounded by pre-approved ranges and sent to the executive with authority, who decides. Business users can also set up their own alerts, such as a rule for one route, without the data team.

More on margin and profit

More on delivery and turnaround

See it on your own KPI.

Bring one revenue-critical KPI. We'll show how Bicycle detects the movement, explains the cause, and recommends the next step.

Book a demo