All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Courier & Parcel Management · Available now

Follow each parcel milestone through to delivery evidence.

Courier & Parcel Management coordinates courier loads from planning through physical pickup, parcel milestones and evidenced delivery. Each load has an operating organization, assigned owner, transport partner, promised delivery time and freight amount.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewLoad planning queue
Courier & Parcel Management · Loads

Load planning queue

Loads in one list

New load
Loads in view
6
Total freight amount USD
2,940
Draft
3
Planned
3
Draft3
Riverside retail morning routeHigh-roof parcel van
600
26 Oct
Westport same-day parcelsElectric cargo van
790
02 Nov
Airport business park pickupLiftgate box truck
230
23 Oct
Add
Planned3
North hill medical suppliesStandard delivery van
610
29 Oct
Market district afternoon loopRefrigerated van
460
27 Oct
South quay returns routeCargo bicycle
250
16 Oct
Add
Riverside retail morning routeLoads · LDS-42142
Draft
Promised delivery at26 Oct
Equipment classHigh-roof parcel van
CounterpartyHarbor Trail Logistics
OwnerNadia Mensah
Freight amount USD600
Review parcel scanLDS-42142 · Riverside retail morning route

Transport Supervisor approves, rejects or returns the submitted parcel scan revision with a reason; the preparer cannot approve their own work.

Waiting for Transport Supervisor
ApproveReturn
Example screen with sample data
Tables, ready to use
15
Saved views
16
Roles with set permissions
5
Reports and dashboards
9
Features

Keep courier work in view

Every feature works on the same records. Pick one to see the screen your team works in.

Load planning

Build a feasible courier load around its partner, promised delivery and ordered stop windows.

  • Load ownership
  • Stop sequence
  • Feasibility
  • Loads
  • Load stops
  • Transport partners
  • Organizations
  • Team members
  • Load assignments
Explore load planning
OverviewLoad exceptions
Courier & Parcel Management · Load planning

Load exceptions

Loads

New
Record numberSubjectStatusPromised delivery atActual pickup atActual delivery at
LDS-19394Riverside retail morning routeException15 Oct23 Oct25 Oct
LDS-35529North hill medical suppliesException29 Oct02 Nov10 Nov
LDS-53576Westport same-day parcelsException23 Oct01 Nov09 Nov
LDS-13273Market district afternoon loopException31 Oct03 Nov12 Nov
LDS-99436Airport business park pickupException23 Oct26 Oct04 Nov
6 of 6 records
Riverside retail morning routeLoads · LDS-19394
Exception
Promised delivery at15 Oct
Actual pickup at23 Oct
Actual delivery at25 Oct
OwnerKira Petrov
CounterpartyWillow Road Couriers
Example screen with sample data
Process

From load plan to delivery proof

Planned load to evidenced delivery ships ready to use. One step needs a named approval before the work moves on: Review parcel scan (Transport Supervisor).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Plan the load

    Check stop windows, eligible assignments and the promised delivery.

    Riverside retail morning routeLDS-42142 · Transport Supervisor
    Plan the loadBy Transport Supervisor
  2. Confirm pickup

    Record physical pickup and its actual time before dispatch.

    Riverside retail morning routeLDS-42142 · Dispatcher
    Confirm pickupBy Dispatcher
  3. Capture parcel milestone

    Tie the physical event to its tracking number and operating load.

    Riverside retail morning routeLDS-42142 · Dispatcher
    Capture parcel milestoneBy Dispatcher
  4. Review parcel scan

    Give the submitted revision an independent evidence decision.

    Riverside retail morning routeLDS-42142 · Transport Supervisor
    Review parcel scanBy Transport Supervisor
    ApprovalTransport Supervisor approves, rejects or returns the submitted parcel scan revision with a reason; the preparer cannot approve their own work.
  5. Record delivery

    Close complete service from recipient proof and actual delivery time.

    Riverside retail morning routeLDS-42142 · Dispatcher
    Record deliveryBy Dispatcher
  6. Reconcile effects

    Compare uncertain actions with the effects that actually persisted.

    Riverside retail morning routeLDS-42142 · Transport Supervisor
    Reconcile effectsBy Transport Supervisor
Inside a record

Connect physical events to the load

Open any load to see its load assignments, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Promised delivery at, Equipment class, Counterparty and Owner.

  2. 2
    Load assignments

    Each line is linked to this load.

  3. 3
    Who works on it

    Dispatcher, Transport Supervisor and Auditor, each with their own permissions.

  4. 4
    Process stages

    Prepare operating scope and Plan the load, with the role that acts.

  5. 5
    Approvals

    Review parcel scan, with who decides.

Load planning queueRiverside retail morning route
Courier & Parcel Management · Loads

Riverside retail morning route

High-roof parcel van · Draft

Log activity
1
Record details
Promised delivery at26 Oct
Equipment classHigh-roof parcel van
CounterpartyHarbor Trail Logistics
OwnerNadia Mensah
2
Load assignments

Riverside retail morning route

LoadDriverVehicle
South quay returns routeLena BrooksVan 18, refrigerated
Cedar valley express runLena BrooksVan 21, standard
Riverside retail morning routeTessa NguyenVan 04, electric
Load assignments
6
3

Who works on it

  • DispatcherManage Loads, parcel scans, record attachments
  • Transport SupervisorView Drivers, load assignments, load stops, Loads, operation…
  • AuditorView Drivers, load assignments, load stops, Loads, operation…
4

Process stages

  • Prepare operating scopeApp Administrator, Dispatcher
  • Plan the loadTransport Supervisor, Dispatcher
5

Approvals

  • Review parcel scanTransport Supervisor
    Approved
Example screen with sample data
Approvals

Review parcel evidence independently

Transport Supervisor decides submitted scan revisions through the authorized review procedure. Keep the preparer separate from the reviewer and check the current revision when recording a decision.

OverviewApprovals
Courier & Parcel Management · Overview

Approvals

Signed in as Transport Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • PS-37760Old town residential deliveries
    Northbank Delivery GroupRequested by Dispatcher
    Pickup2dActions
  • PS-16349Cedar valley express run
    Oakline Urban DeliveryRequested by Dispatcher
    Sortation1dActions
  • PS-12231Westport same-day parcels
    Northbank Delivery GroupRequested by Dispatcher
    Out For Delivery2dActions
  • PS-32339Airport business park pickup
    Silverway Parcel NetworkRequested by Dispatcher
    Delivered6dActions

Who approves what

DecisionApprover
Review parcel scanGive the submitted revision an independent evidence decision.Transport Supervisor
1 approval rule · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Courier & Parcel Management to the work that is theirs. Pick a role to see what it starts with.

Dispatcher

Prepare assigned operational records and execute eligible reviewed actions.

This is the first screen this role sees.

OverviewLoad planning queue

Load planning queue

Loads · Dispatcher

Draft3
Riverside retail morning routeHigh-roof parcel van
600
26 Oct
Westport same-day parcelsElectric cargo van
790
02 Nov
Airport business park pickupLiftgate box truck
230
23 Oct
Add
Planned3
North hill medical suppliesStandard delivery van
610
29 Oct
Market district afternoon loopRefrigerated van
460
27 Oct
South quay returns routeCargo bicycle
250
16 Oct
Add
Example screen with sample data
Reports

Explain parcel and delivery outcomes

Explain parcel movement, delivery performance and unresolved actions from their underlying evidence.

Overview
Courier & Parcel Management · Overview

Courier & Parcel Management dashboard

This quarter

Parcel scans in view
6
Total package weight LB
3,640
Pickup
2
Sortation
1

Loads by status

How far records got this quarter

StageReachedStep
Draft30
Planned1757%
Dispatched953%
In transit667%

Freight amount USD by status

Sample totals per stage

2.0k0
2.0kDraft
2.0kPlanned
2.0kDispatched
2.0kIn transit
2.0kDelivered
Example screen with sample data
  1. 01Load workload by owner

    Group Loads by Organization, Owner and Status with promised delivery at and freight amount USD to distinguish operational work from recorded freight value.

  2. 02Assignment window register

    List load assignments with Load, Driver, Vehicle, starts at, ends at and Status to inspect overlapping commitments.

  3. 03Driver eligibility register

    List Drivers with driver code, Active, eligibility until and external authority for the assignment interval under review.

  4. 04Critical vehicle defect history

    Group vehicle defects by Vehicle and show reported at, Severity, repair evidence and released at without treating every historical Critical entry as currently open.

  5. 05Parcel milestone history

    Group parcel scans by Parent and tracking number with scan type, scanned at, package weight LB, Status and Revision, retaining repeated milestones without summing their weight as separate parcels.

  6. 06Delivery timeliness

    Compare actual delivery at with promised delivery at on Delivered Loads and group by actual delivery week, retaining late deliveries against the original promise.

  7. 07Stop evidence register

    Group load stops by Parent and stop sequence with window start, window end, actual arrival at, actual departure at and proof reference.

  8. 08Independent scan decision history

    Group review decisions by Parent and source revision with Reviewer, Decision, Reason, decided at and operation key.

  9. 09Operation discrepancy register

    List operation receipts with result state Pending, Failed or needs review alongside expected revision, effect references and failure reason.

Controls

Keep decisions tied to their evidence

Each stage of planned load to evidenced delivery names the role that acts and the status it records, so a change is never anonymous.

OverviewPlanned load to evidenced delivery
Courier & Parcel Management · Process

Planned load to evidenced delivery

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
3
Tables touched
12
Plan the load
Transport Supervisor, Dispatcher
StatusDraft → Planned
RecordsVehicle defects, Load stops, Drivers
Reserve assignment
Any role with access
StatusHeld → Confirmed
RecordsLoad assignments, Vehicles, Drivers
Confirm pickup
Dispatcher
StatusPlanned → Dispatched
RecordsOperation receipts, Loads
Planned load to evidenced delivery
  1. Start
    Plan the loadDraft → Planned
    Vehicle defects
  2. Step
    Reserve assignmentHeld → Confirmed
    Load assignments
  3. Step
    Confirm pickupPlanned → Dispatched
    Operation receipts
  4. Step
    Capture parcel milestoneDraft → Submitted
    Parcel scans
  5. Approval
    Review parcel scanSubmitted → Approved
    Review decisions
Example screen with sample data
AI agent

Prepare the dispatch shift with Proto

Ask Proto to prepare load work and explain parcel evidence within the team's operating authority.

It can

  • Dispatcher: Show my planned loads and summarize their promised delivery, stop windows and outstanding scan preparation.
  • Transport Supervisor: Prepare a review of submitted parcel scans, highlighting the tracking number, physical event time and any mismatch with supporting evidence.
  • Admin: Help inspect assignment intervals and identify driver or vehicle commitments that overlap the requested load window.
  • App Administrator: Prepare partner and fleet roster updates while preserving stable codes, authority references and organization membership.

Stays with a person

  • The assistant cannot invent a physical pickup, scan or recipient proof.
  • Transport Supervisor makes the independent review decision, and assisted actions remain subject to the person's authority and current record revision.
  • An uncertain operation requires inspection of actual effects before any further external execution.
  • Prepare the operating identities and evidence connections through Implementation before using assisted actions in daily dispatch.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Courier & Parcel Management
  • Carrier and parcel scan sources
  • Fleet and driver authority sources
  • Recipient proof sources
  • Exchange-rate source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 15 tables
15tables
  • Load planning7
  • Driver and vehicle assignments5
  • Parcel milestones4
  • Independent scan review6
  • Delivery evidence5
  • Exceptions and reconciliation6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the first operating scope

    Choose the organization, partner lane and dispatch shift. Set the time zone and name the people responsible for load preparation, supporting records and independent scan decisions.

  2. Prepare the rosters

    App Administrator loads partners, drivers and vehicles with stable identities. Admin prepares assignment and defect records, and Transport Supervisor checks the evidence supporting eligibility for the pilot interval.

  3. Build the load plan

    Prepare promised delivery, ordered stop windows and the driver-vehicle assignment. Rehearse overlap, equipment suitability and open critical defect checks before planning is accepted.

  4. Connect physical evidence

    Arrange the scan and recipient-proof sources. Check provider identity, timestamps and load mapping, including a repeated notification and an event for another operating organization.

  5. Rehearse independent acceptance

    Submit a supported scan, return a flawed submission and prepare an authorized correction. Test a stale decision and self-review before accepting the valid current revision.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Courier & Parcel Management.

All questions
How do I get started?

Click Get started, then use Proto to configure Courier & Parcel Management for your business. Begin with a familiar partner lane, a bounded dispatch shift and a dispatcher-supervisor pair that can rehearse both a completed delivery and an exception.

What belongs in a load plan?

Record the operating organization, assigned owner, transport partner and promised delivery. Add ordered stop windows and an eligible driver-vehicle assignment so the dispatch team can explain how the plan will be performed.

How do we check driver and vehicle suitability?

Examine driver eligibility across the assignment interval, vehicle equipment and capacity, readiness and critical defect evidence. Check existing commitments before confirming another interval for the same driver or vehicle.

Which parcel milestones can we record?

Use Pickup, Sortation, Out For Delivery, Delivered and Exception. Retain the tracking number, physical scan time and supported package weight with the correct load and organization.

Who decides whether a submitted scan is accepted?

Transport Supervisor independently approves, rejects or returns the submitted revision with a reason. The dispatcher who prepared the scan cannot provide its independent approval.

What happens when a provider sends the same scan again?

The receiving procedure uses provider event identity to return the existing result. A tracking number can have different valid milestones, so distinguish the event identity from the parcel identity during setup.

What evidence completes delivery?

Obtain the recipient proof reference for the correct stop and the actual delivery time. Check the whole load before marking it Delivered; partial or refused service remains an explicit Exception.

How is late delivery reviewed?

Compare actual delivery with the original promised time. Keep that promise intact so the delivery-week and late-delivery review reflects the commitment the team originally made.

How do we correct accepted work?

Read the current revision, stops, decisions and operation receipts before requesting an authorized correction. Preserve executed evidence and use a fresh submission when a returned scan needs another review.

What if an action times out?

Transport Supervisor checks the operation receipt against linked local effects before another attempt. Record completion only when the expected effects match; otherwise retain the discrepancy for review. Follow Correct and reconcile.

Set up Courier & Parcel Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appCourier & Parcel Management

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.