1 CEP - Order Creation Workflow

--------------------------------------------------------------------------------------------------------------------------
1.

Shipment is created through API or through user interface

Relevant API documentation is provided

--------------------------------------------------------------------------------------------------------------------------
2.

By default we accept all orders, however if an order is not matched by routing rules - we can
easily modify the system to reject orders that do not match any routing rule.
--------------------------------------------------------------------------------------------------------------------------
3.
This is how taxes and duties are calculated in the system

--------------------------------------------------------------------------------------------------------------------------
4.
This can be easily added.
-------------------------------------------------------------------------------------------------------------------------
5.

In API request consignee_address.address_code.type that equals google_plus can be

specified and consignee_address.address_code.value may then contain Google Plus code.
Coordinates are supplied in consignee_address.geo.latitude and
consignee_address.geo.longitude.
If the coordinates are not set, they are obtained through geocoding of the address.
If the Google Plus code is provided, the coordinates are obtained through Google Plus.
--------------------------------------------------------------------------------------------------------------------------
6.
Invoices are created:

--------------------------------------------------------------------------------------------------------------------------
7.

This is implemented through a cron job that adds an event and changes the order’s status.
========================================================================
2 Pickups Workflow
Domestic Client Pickups

1.
A collection is created and a driver is assigned.

--------------------------------------------------------------------------------------------------------------------------
2.
The driver can scan parcels.
Partially present shipments are flagged
If a shipment is missing - a corresponding notification is shown
After the pickup, all shipment events can be seen in the admin area.

--------------------------------------------------------------------------------------------------------------------------
3.
A collection can be failed by the driver.

========================================================================
Customer Pickups

1.

Labels can be printed in bulk. Integrating this with customer pickup should be a low-effort task.
--------------------------------------------------------------------------------------------------------------------------

3.
The rest of Customer Pickup functionality is the same as Domestic Client Pickup.
========================================================================

International Customer Pickups

1.

This workflow is covered through our 3PL integrations and the entire lifecycle of the package is
being monitored through tracking events.
--------------------------------------------------------------------------------------------------------------------------
2.

This is covered by the existing system’s features.

--------------------------------------------------------------------------------------------------------------------------

3.
TBD

========================================================================

Multi-Pickup Delivery

To cover this workflow, the current system can be adapted through creating separate pickups
for individual parcels instead of shipments.

========================================================================

Pickups Folder and Pickups Completed Folder

Collections are grouped into logical folders depending on their status.

========================================================================.
3 Inbound and Sortation Workflow
Inbound

TBD.

========================================================================
Domestic Inbound and Sortation

1.

Currently we are supporting multiple volumizer sorting solutions and more can be added.

The mobile application also has inbound functionality.

--------------------------------------------------------------------------------------------------------------------------
2.
This is covered by existing sorting settings, with possible minor changes.
========================================================================
INTL Inbound and Sortation
1.

Apart from the Failed Customs case all is present in current functionality.
--------------------------------------------------------------------------------------------------------------------------
2.
Same as above. Fully covered.
========================================================================
MIS-Route
Covered in existing functionality for address corrections.
========================================================================

4 Driver Route Prep Workflow

Route Preparation

1.

Covered by sorting functionality

--------------------------------------------------------------------------------------------------------------------------
2.
All the other steps are covered in Runsheets functionality inside the web version of the
application.
A route (runsheet) is created with the courier already assigned.
========================================================================
Courier Loading

The process of courier loading in the current system is carried out by the warehouse
administrator within the functionality described above.
========================================================================

5 Delivery Workflow
Pre-Delivery

1.

Summary is viewed from the driver’s app in the Runsheet section.

--------------------------------------------------------------------------------------------------------------------------
2.
The trip is initiated by the supervisor

--------------------------------------------------------------------------------------------------------------------------
3.

The label printing functionality is in place, however additional warnings will have to be added.
--------------------------------------------------------------------------------------------------------------------------
4.

Summary is also visible from the Tasks list

--------------------------------------------------------------------------------------------------------------------------
5.

Driver is able to call the consignee or send a message through WhatsApp:

--------------------------------------------------------------------------------------------------------------------------
6.

Tasks are easily delivered consequently, without the need of explicit grouping.
--------------------------------------------------------------------------------------------------------------------------
6.

Parcel check:
--------------------------------------------------------------------------------------------------------------------------
7.
--------------------------------------------------------------------------------------------------------------------------
8.
The driver specifies the reason for failing a delivery.

========================================================================
COD Delivery
COD can be validated through various means. Money can be collected by cash or through a
POS terminal. POS-less card payments and mixed card-cash payments will have to be
implemented.
========================================================================
Prepaid Delivery

Our functionality fully covers this workflow, with the only difference from the COD delivery being
the driver needing to add a photo confirmation of the delivery at the end. To cover all the
possible delivery fail reasons we may want to add several additional ones.
========================================================================
Pickup on Delivery

Currently delivery and pickup are handled separately since it allows to also handle returns
without deliveries.
========================================================================
Same Day Delivery
Currently, the driver’s app has the functionality to add a newly picked up parcel to a runsheet
allowing its delivery without going through a hub. With additional effort, this can be streamlined
and enforced for the Same Day delivery service.

========================================================================
6 Undelivered Workflow
1.
When shipment’s delivery has failed, it changes status to “Delivery Attempted” and can be
added to a new Runsheet for the next delivery attempt to be made.
--------------------------------------------------------------------------------------------------------------------------
2.

Currently full shipment delivery is being enforced. With minor reconfiguration, partial delivery
can be allowed.
========================================================================
7 Damaged Parcels Workflow

Currently, damaged status is applied to the whole shipment. Minor adjustments will be needed
to allow separate parcels to be marked as damaged.

This can also be done from the web UI.

In our current terminology, Damaged status means ‘Damaged beyond repair’ by default.
More statuses can be added to reflect various degrees of damage. Or the stage at which
damage occurred (e.g. Inbound damage).
========================================================================

8 Lost Parcels Workflow

In the current system, the transition between Lost and Found is done through scanning a parcel
as Lost and if the parcel is found, by revoking the Lost scan.
========================================================================
9 Change of Address Workflow
A bad address can be reported by a hub operator:

Customer Support can change the address from the web interface
An API for external integrations (e.g. chatbots) for address change is available as well
The courier can change the delivery point without changing the delivery address in the
shipment.

========================================================================
10 Reschedule Workflow

Rescheduling can be picked as a delivery fail reason from the courier’s app.
The attempt with the corresponding reason will be seen from the web interface.

========================================================================

11 Debrief Workflow
Runsheet debrief is done from the admin area.
Collection debrief is done using Origin inbound scans.
1.
These steps are combined on one screen.
If a financial discrepancy occurrs - the system shows a warning and doesn’t allow the debrief to
be completed.

========================================================================
12 Linehaul Workflow
Containers:

Containers (e.g. pallets, bags) are used to group parcels for linehaul purposes.

Containers can be created from web interface:

Containers can be created from hub worker’s app:

Once a container is created, labels and manifests are available to be printed and downloaded.
========================================================================
Outbound Linehaul

MAWBs can be created to represent a complete haul that consists of multiple containers and
separate parcels.

During MAWB creation containers and shipments are added:

Truck seal is recorded to ensure the security of the freight.

Created MAWBs can be departed, cancelled or edited. Manifest can be downloaded for each
MAWB.
Example of a MAWB manifest
========================================================================
Inbound Linehaul
Linehaul is handled through MAWB’s. MAWB is accepted as arrived by the hub staff after
checking the seal on the vehicle.
After unloading and container unpacking, multiple hub workers can scan the parcels in parallel,
each creating a scan batch.
The scan batches from the previous step are then added to the inbound MAWB.

After the batches were added, separate parcels can be marked as damaged.
Comment and a photo for a damaged parcel can be added.
If there are missing shipments in the MAWB, hub staff receives a warning and have to confirm
that those missing parcels are actually missing.

After the MAWB receiving process is complete - the results are generated and shown in the
MAWB’s info.
MAWB’s info screen:
Using existing status functionality additional exception handling can be added.
========================================================================
Linehaul Transit

This is essentially the previous two workflows with the exception of the ability to receive and
dispatch containers without unpacking on transit hubs that will have to be added.
========================================================================
Mis-Sort
Mis-sorting is present in the current system with the exception of a need to unpack containers,
mentioned above.
========================================================================

13 On-Hold Workflow
A shipment can be put on hold by a hub worker.
Similar process is in place to remove a parcel from ‘Hold’ status
Holding and revoking the ‘Hold’ status events can be viewed from the shipment’s details.
For additional sorting of parcels that are on hold, shelves are used. These are created from the
web interface. For each shelf, a corresponding warehouse and a code is assigned.
A parcel can be put on a shelf or taken from it by the hub worker from the mobile app.
These events are also visible in the shipment’s details.
Additional statuses and logic can be added.
========================================================================

14 International Outbound Workflow

1.
2.

This can be implemented based on existing MAWB functionality.

TBD - Add routing rules here.

========================================================================

15 Domestic and ITNL RTO Workflow

Domestic RTO
1.

From the operator’s app multiple shipments can be assigned to RTO:

The result can be seen in the shipment’s details:

RTO Address, different from sender address, is easily added to current logic.

2.

Consolidation can be covered by extending existing hold mechanics to support scheduled holds.
3.

This can be covered through the implementation of additional statuses.

========================================================================
INTL Transit & Direct RTO

The current system has 3PL integrations with tracking mapping functionality.
========================================================================
EMS RTO

TBD.
========================================================================

16 Customs Workflow

The current system delegates customs clearance responsibility to external customs brokers and
more customs brokers can be added.
========================================================================

17 International Pre-Alert Workflow

This can be added by using already existing MAWB creation and processing functionality as a
basis.
=======================================================================

18 PUDO Workflow
1.

PUDO list API endpoint is available:

--------------------------------------------------------------------------------------------------------------------------
2.

During shipment creation, PUDO can be set as the sender's or delivery address.
PUDO point operator receives and stores parcels:
Parcels present at the PUDO point:
When consignee picks up a parcel from the PUDO point

he operator can validate the delivery through SMS to the consignee’s phone or by their ID.
A step where COD payment is confirmed:
Corresponding event can be seen in the shipment’s details:
PUDO point operator can also create a shipment:
After the shipment is created, a label for it can be printed:
========================================================================
19 Customer Services Workflow

Customer services workflow is virtually the same as address fix workflow shown below. It can
be extended to cover additional request types including more complex request processing
involving multiple roles.
For example the workflow below involves a person that reports a bad address; customer
services that fix the address; and hub staff that reprints the label and relabelles the parcel.

Address fix is created:

New address is specified:
After the address has been fixed and label reprinted - the shipment’s status is updated to reflect
the changes:

========================================================================

20 Customer Self-Collection Workflow

This is better handled as a PUDO-point collocated with a hub, as described in PUDO workflow.
========================================================================
21 Postal Workflows

Tracked Mail-Order Creation

1.

This is covered through API integrations.

--------------------------------------------------------------------------------------------------------------------------
2.
Covered through ‘Bad address’ functionality described earlier.
========================================================================
Redirection

Covered by ‘Bad address’ functionality, described earlier.

========================================================================
Tracked Mail-Sort & Bagging + Ordinary Mail-Sort & Bagging

This is covered by existing ‘Containers’ functionality, with some additional tweaks.

========================================================================
Mail Linehaul Outbound

Same as in Linehaul Workflow - covered by existing container functionality.

========================================================================
Mail Linehaul Inbound

By introducing an overarching ‘Trip’ entity we can effectively implement multi-point livehaul logic
while using point-to-point linehauls as a more robust way to group shipments without any
apparent drawbacks. As before, this workflow is almost entirely covered by container
functionality, with possible addition of exceptions handling through shipment/container statutes.
========================================================================
Mail-Mis-Sort

Mis-sorting is present in the current system with the exception of a need to unpack containers.
========================================================================
Customs-Ministry Check

1.

This is currently covered by broker integration, additional scan options on hub worker’s app may
be added, along with customer notification through WhatsApp.
--------------------------------------------------------------------------------------------------------------------------
2.
In the current system, customs fees are calculated automatically, yet manual input can be
added for cases when customs recategorizes imported items.
========================================================================
Tracked Mail-Inbound & Shelving
1.

This part is covered by existing ‘MAWB receiving’ functionality, described above.

--------------------------------------------------------------------------------------------------------------------------
2.

Shelving is covered:
--------------------------------------------------------------------------------------------------------------------------
3.
This feature can be implemented without extensive development.
========================================================================
Tracked Mail-Customer Collect

With minor tweaks, this is covered by PUDO functionality.

========================================================================
Tracked Mail-Ex Branch Outbound

Covered by PUDO and International Outbound workflows.

========================================================================
Tracked Mail - Uncollected

Can be implemented through a cron job.

========================================================================
Tracked Mail - RTS

It is covered in Linehaul workflows with addition of Disposal procedure, which can be

implemented with low to medium development effort.
========================================================================

22 Driver DB
1.

Drivers are currently handled in the web interface, along with vehicles and garages:
--------------------------------------------------------------------------------------------------------------------------
2.
More info for the driver can be easily added in accordance to reflect Driver Profile requirements.

Vehicles are assigned to drivers and added to a garage.

Various events can be tracked from Driver incidents:
An example of ‘Accident’ report:
========================================================================

22 Driver Payment Reports

Since it doesn’t involve any logic-heavy operations, this can be implemented without extensive
development efforts.
========================================================================