Skip to main content
GullySystem
Logistics

Business solutions for Last-mile delivery companies

Explore software for work such as “Merchant parcel intake and custody reconciliation”. Review each business function below, including when it fits and what to check before implementation.

Last-mile delivery companies

How the business operates.

A last-mile delivery company takes custody of a merchant’s parcels at a hub or pickup point and coordinates their delivery attempts and authorised returns. The goods are entrusted for delivery under the accepted merchant instructions and remain outside operator-owned stock; the delivery operator manages the service and custody records. This proposed software scope connects merchant instructions, actual parcels, rider assignments, attempt evidence and commercial reconciliation. Where cash on delivery is contracted, money collected for the merchant must remain separate from the operator’s delivery-service revenue. A completed rider task can represent a failed attempt, so delivery, return and cash outcomes need their own evidence.

Merchant instructions and hub intake

Accept delivery requests within the actual service agreement. Match parcel identifiers and counts at receipt, preserving shortages, visible concerns and information still needed from the merchant.

Dispatch and rider coordination

Assign the actual work and record parcel handover. Keep delivery instructions, accepted changes and parcel custody visible when work is reassigned.

Attempt and return review

Review successful and unsuccessful attempt evidence. Obtain the merchant’s required decision for reattempt or return and record the actual return acknowledgement.

Collection and service accounts

Reconcile contracted customer collections through rider handover and merchant remittance. Bill delivery services from accepted terms and supported outcomes through a separate account.

The records that hold the operation together.

  • Merchant order and accepted delivery-service reference
  • Parcel identifier, expected and actual piece counts and custody acknowledgements
  • Recipient instructions and authorised changes with access restrictions
  • Rider assignment, attempt outcome and supporting evidence
  • Approved reattempt or return instruction and merchant receipt
  • Contracted collection amount, verified payment and current custodian
  • Merchant remittance reconciliation and separate service invoice

Operational bottlenecks to check

Assignment changes but parcels stay with the first rider

A reassigned task is not a custody transfer. Both workers’ acknowledgements and unresolved parcels need to remain visible.

A closed attempt appears as a delivery

Failure, refusal and incomplete evidence need explicit outcomes. A closed work item must not inflate the delivered-parcel count.

Returned status precedes actual receipt

The merchant’s return instruction and the parcel reaching its recipient are different events. Retain the physical return acknowledgement and any discrepancy.

Collected cash becomes assumed revenue

Cash received for merchandise belongs to the merchant’s settlement record. Internal handover and service-fee deductions must not create a second receipt or an unsupported reduction.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Accept the merchant request

    Confirm the actual delivery service, parcel references and collection instruction if contracted. Keep specialised goods or handling outside acceptance until separately reviewed.

  2. 2. Receive and allocate custody

    Match physical parcels to the request and record exceptions. Assign the work and acknowledge the actual handover to the rider.

  3. 3. Record each attempt

    Capture the attempt outcome and required evidence without turning an address visit into delivery. Refer refused, inaccessible or disputed handovers for the agreed decision.

  4. 4. Resolve undelivered parcels

    Retain prior attempts while recording an authorised reattempt or return. Confirm physical custody and merchant receipt rather than closing a return from its instruction alone.

  5. 5. Reconcile money and fees

    Review any customer collection, rider-to-office handover and actual merchant remittance. Separately bill the accepted delivery services and approved additional work.

Roles and responsibility boundaries.

Merchant account coordinator

Maintains the service agreement, accepted delivery instructions and authority for changes or returns.

Hub custodian

Records actual parcels received, issued and returned, including mismatches and the person acknowledging each handover.

Dispatcher

Assigns work to available riders and keeps reassignment, blockers and unresolved custody visible.

Rider or delivery worker

Records actual attempts, agreed evidence and collection details. Does not change payment instructions or substitute delivery outcomes without authority.

Reconciliation reviewer

Checks delivery-service billing separately from merchant-owned cash, internal handovers and actual remittance evidence.

Reports your managers need.

  • Parcels by merchant, custodian and unresolved mismatch
  • Unassigned work and attempts awaiting review or instructions
  • Delivered, failed, reattempted and physically returned parcels
  • Collection differences by rider, payment evidence and merchant
  • Remittances pending or evidenced separately from service receivables

Connections to scope

  • Assess authorised merchant-order imports, delivery-evidence exports and accounting references using agreed parcel and account identifiers.
  • Rider apps, geolocation, notifications and payment connections require separately agreed supported scope. Evidence access and retention need review before collecting recipient photographs or signatures.

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Define the actual delivery contract

Compare prepaid work and any contracted collection work. Agree accepted goods, instructions, return authority, evidence requirements and the boundary between merchant money and service fees.

Trace custody through exceptions

Follow actual parcels from hub receipt through rider handover. Test reassignment, a failed attempt and return receipt with the responsible people.

Reconcile a completed work set

Compare merchant instructions, attempts, parcel custody and charges. Where collection applies, trace payer evidence through office handover to actual remittance without netting unexplained differences.

Limitations to settle before implementation

  • This example covers ordinary parcel delivery. Medicines, temperature-controlled goods, hazardous items and specialised bulky-item handling require separately confirmed capability and obligations.
  • A task status, photograph or signature is evidence to review, not independent proof of parcel contents, rightful receipt or payment settlement.
  • Live tracking, route optimisation, emergency response, insurance decisions and delivery-time commitments are not supplied by these proposed records.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Merchant parcel intake and custody reconciliation
  • Rider assignment and delivery-attempt recording
  • Authorised reattempt and physical return handover
  • Contracted collection reconciliation and separate delivery-service billing
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements