Skip to main content

Delivery Company Guide

Version: v1.1
Last Updated: June 14, 2026

Everything you need to operate a delivery company on BookMaMe: dispatch, rider assignment, active deliveries, failed-delivery handling, depot flows, collections, and reporting.

Start Here​

How to access the delivery company module​

Delivery-company users can access this operational surface from the Partner Portal on supported mobile devices, and through the web experience where deployed.

From the delivery-company module you can:

  • monitor dispatch
  • assign riders
  • track active deliveries
  • manage depot outcomes
  • review collections
  • inspect finance and operational reports

The module now works across mixed delivery sources, not just one order type.

Important distinction:

  • delivery company is included in the Partner Portal
  • rider remains a separate standalone app

What kinds of tasks you may see​

Your active deliveries can include work from different marketplace sources, such as:

  • restaurant deliveries
  • shop deliveries
  • rental outbound or return tasks
  • second-hand deliveries and returns
  • parcel delivery requests

Each task may have different handoff semantics, but they all move through the same core operational lifecycle:

  • unassigned
  • assigned
  • picked up / in progress
  • completed
  • failed / returned to depot

Dashboard overview​

The dashboard typically summarises:

  • Active deliveries
  • Items at depot
  • Riders
  • Collections / finance visibility

For active tasks, the operational view can now include richer package context such as:

  • resolved delivery class
  • computed total weight
  • computed total volume

These help dispatchers understand what kind of delivery is being handled.

Dispatch and rider assignment​

When a supported source creates a delivery task for your company, it appears in the dispatch surface once ready for assignment.

Typical dispatch flow:

  1. Open the active or unassigned task view
  2. Review the pickup, drop-off, source, and package details
  3. Assign a rider
  4. Monitor the task as it moves through pickup and delivery

📸 Screenshot: Delivery-company app — active deliveries list

Choosing the right rider​

Dispatch decisions may take into account:

  • rider proximity / ETA
  • rider availability
  • current workload
  • task compatibility with the delivery requirements

For some deliveries, the task details are important operational context:

  • parcel class
  • weight / volume
  • source type
  • pickup and drop-off instructions

Monitoring active deliveries​

From the active deliveries area you can track:

  • the task status
  • rider assignment state
  • the route / map context where available
  • fulfillment progress
  • source-specific detail such as parcel information or mixed-source references

Parcel delivery tasks, for example, may show:

  • parcel request number
  • sender/recipient context
  • parcel class
  • computed package weight and volume

Failed delivery and depot handling​

If a rider cannot complete a delivery, the item or parcel may be returned to the delivery company for a decision.

Typical flow:

  1. The rider marks the delivery as failed
  2. The rider returns the item to the depot or company handoff point
  3. Depot staff confirm receipt
  4. The company chooses the next action

Common next actions:

  • Retry delivery
  • Return to partner / source
  • Return to sender for parcel and some peer-to-peer flows
  • Close only where the flow/policy permits it

📸 Screenshot: Delivery-company app — items at depot

Important source differences​

Not every task type supports the same depot outcome.

Examples:

  • parcel delivery may require return to sender
  • second-hand may require return toward the seller side
  • rental tasks may use outbound/return-specific handling

So the correct depot action depends on the task source and stage.

Collections and finance visibility​

Some delivery tasks involve money collected from the customer, such as:

  • cash on delivery
  • card on delivery
  • other rider-collected handoff payments where supported

Other tasks, such as parcel delivery or online-paid second-hand, may not produce rider collections in the same way.

Use the collections and finance screens to track:

  • what riders collected
  • what has been remitted
  • what remains outstanding
  • what belongs to the delivery-company earnings side vs. partner remittance side

See Collections Management.

Rider management​

From the rider section you can:

  • add or onboard riders
  • approve riders before they can receive jobs
  • suspend or reactivate riders
  • monitor rider workload and operational performance

The rider app itself is covered in Rider Guide.

Reports and exports​

Delivery-company reporting now reflects a broader mixed-source operation.

You may review:

  • delivery volume
  • success / failure rates
  • SLA performance
  • rider performance
  • mixed-source delivery history
  • finance and settlement reporting
  • CSV exports for reconciliation and operations review

See the shared Reports guide for the reporting overview.