1

1 CEP - Order Creation Workflow

Order
created
via API or
Client
Portal
2
Relevant API documentation is provided

IMPORTANT NOTE:
Some international
partners AND some
services do not allow for
Multi Piece Orders (MPS).
These can be identified
in the Masterdata for the
services and partners. If
the client tries to create
an MPS order where it is
not allowed the system
should reject it and
display a notification as
to why.

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

During order creation any

duties/taxes and other
customs fees are
calculated and itemised in
the record and a
'CUSTOMS FEES’
FLAG is set
4
This is how taxes and duties are calculated in the system

NOTE:
If no delivery attributes
are sent in the order
data the default
attributes according to
the client profile in the
Masterdata are applied
5
Geocoding

The order record is

Yes held in the ‘pending
Deliveries’ folder with
a status of ‘order Data
Received’ In API request
Yes
`
consignee_address.address_code.type
that equals google_plus can be specified
Important
Process
Using and
Are the Street, the Google Reverse
The address
fields contain
Area and city Geocoding API consignee_address.address_code.value
fields populated? No the missing inputs are
input fields `
added to the address may then contain Google Plus code.
for long & lat
data
co-ordinates Coordinates are supplied in
and Google
plus code
Customer has
supplied co-
Using the Google consignee_address.geo.latitude
Geocoding API
ordinates or `
the co-ordinates and
Google Plus Code? or Google Plus
No Code is added to consignee_address.geo.longitude.
the input fields If the coordinates are not set, they are
The order record is obtained through geocoding of the
held in the ‘pending
Deliveries’ folder with address.
a status of ‘order Data
Received’ If the Google Plus code is provided, the
coordinates are obtained through Google
The order record is Plus.
held in the
‘International
Deliveries / Pending
<< order type >>
folder
6
Invoice Generation and Management

During the order creation the

system uses the order data
to create a commercial
invoice and stores it as part
of the order record. Either a
customer specific or a default
template is used acording to
the Masterdata. The invoice
can be printed from the order
record in International/
Pending Deliveries folder or
when a Linehaul bag is
created
7
Invoices are created:
This is implemented through a
cron job that adds an event and
changes the order’s status.

IMPORTANT PROCESS
Any order that has not
received a first scan event
after 90 days from creation
(or as duration set in
masterdata) should be
automatically given an
EVENT of 'NO ORDER
RECEIVED'and is moved from
its current pending location
to the 'PURGED ORDERS
folder.
8
2 Pickups Workflow

All individual orders marked If an incompleted pickup

for a pickup from a single record exists for a client
client are grouped into one the new orders are
pickup record added to it.

From the_‘Pending Pickups’

folder the operator can click
‘EDIT’ and change the
pickup address manually
which will re-route to the
Domestic
required hub if the postal
code is changed
Client Pickups

Pickup is assigned to a
A pickup record is created in local driver. Order
a ‘Pending Pickups’ folder record and pickup
and is assigned to a hub record are given an
based on the pickup city EVENT of 'Assigned To
Driver’.

Yes
9
Collections

A collection
is created
and a driver
is assigned.
10
Assign Collections

How a
collection is
assigned to
driver.
 marked as ‘Finish Pickup’
‘COLLECTED’ in Mobile
11 App

Do you want to
add to pickup?
Y/N
No If there are parcels that are
After all parcels expected to be scanned that
` ` `
are scanned have not been, the driver is
driver selects shown a warming 'You have
‘Finish Pickup’ <x> parcels that have not
1. The pickup record is moved from the been. collected' (click to show
Is Package Driver is shown parcel IDs)
Selecting YES, the 'Pending Pickups' folder and sent toAre
a you sure you want to
ID valid / message ‘Invalid parcel ID is added Completed Pickups folder but ONLY finish
if all this pickup?
available? Parcel’ and is marked as expected parcels are picked up. If there
Parcel ID is
present ‘COLLECTED’ in are parcels not picked up the pickup
Driver is returned to
Mobile App remains active in the Pickups folder but
scanning function and
` with only the remaining parcels, and
continues before re-
If there are parcels that are any new parcels associated to it and it
selecting ‘Finish Pickup’
expected to be scanned that can be assigned to a driver again. If the
Parcel is marked have not been, the driver is expected parcels are cancelled by the
as ‘COLLECTED’ shown a warming 'You have <x> client the pickup can be cancelled
Driver start parcels that have not been. where it should move to the 'Completed
to scan all in Mobile App
` collected' (click to show parcel Pickups' folder and marked as cancelled.
the IDs) 2. Each valid record in the "Pending
packages Are you sure you want to finish Deliveries folder is updated with a
this pickup? Pickup Completed EVENT
Parcel is marked as 3. For any parcel ID picked up but not
‘COLLECTED’ in Mobile showing in the "Pending Deliveries"
App folder a new record is created in this After all pickups & deliveries
are completed the driver
folder but with minimal available data: selects ‘FINISH TRIP’ to end
Parcel ID, Customer & Pickup their day’s work
Driver is returned
Start Completed" EVENT. Additional data can
` to scanning
Pick Up `
be added from the client or from the
function and
continues before If there are any pickups
re-selecting ‘Finish actioned the driver is
Pickup’ presented with a warnin
message to action them
before ‘FINISH TRIP’ can
selected
12
Scan Parcels

The driver can

scan parcels.
13
Partial Shipment

Partially present
shipments are
flagged
14
Missing Shipment

If a shipment is
missing - a
corresponding
notification is
shown
15
Shipment that are picked up

After the pickup,

all shipment
events can be
seen in the
admin area.
16
17
Failed Collection

A collection can
be failed by the
driver.
18
Customer Pickups

Labels can be printed in bulk.

Integrating this with customer
pickup should be a low-effort task.
19

3. The rest of Customer Pickup functionality is the same

as Domestic Client Pickup.

International Customer Pickups

This workflow is covered through our 3PL integrations and

the entire lifecycle of the package is being monitored
through tracking events.

This is covered by the existing system’s features.

20

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.

TBD
21

3 Inbound and Sortation

Workflow
Inbound

TBD.

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

Domestic Inbound and Sortation

Currently we are supporting multiple volumizer sorting solutions and more can
be added.
22
Mobile inbound functionality

The mobile
application also
has inbound
functionality.
23
This is covered by existing sorting settings, with possible
minor changes.
24

This is covered
by existing
sorting settings,
with possible
minor changes.
25
INTL Inbound and Sortation

Apart from the Failed Customs case all is present in

current functionality.
26

Same as above. Fully covered.

============================================
============================
MIS-Route
27
Covered in existing functionality for address corrections.
28
4. Driver Route Prep Workflow

1 2
A route (runsheet) is created with the courier
already assigned.
Route Preparation

Covered by sorting functionality

29
4. Driver Route Prep Workflow

All the other steps are covered in Runsheets

functionality inside the web version of the application.

Courier Loading
The process of courier loading
in the current system is carried
out by the warehouse
administrator within the
functionality described above.
30
5 Delivery Workflow

1 Pre-Delivery

Summary is
viewed from the
driver’s app in
the Runsheet
section.
31
5 Delivery Workflow

2 The trip is initiated by the supervisor

Driver clicks
‘Start Trip’
32
5 Delivery Workflow

The label printing functionality is in

place, however additional warnings
will have to be added.
33
5 Delivery Workflow

Summary is also
visible from the
Tasks list
34
5 Delivery Workflow

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

WhatsApp:

call or message
through
WhatsApp
35
5 Delivery Workflow

6 Tasks are easily delivered consequently, without the need of

explicit grouping.
36
5 Delivery Workflow

7 Parcel check:
37
5 Delivery Workflow

8 All expected Parcels Scan?

38
5 Delivery Workflow

9 The driver specifies the reason for failing a delivery.

39
5 Delivery Workflow

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.
40
5 Delivery Workflow

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.
41
5 Delivery Workflow

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.
42
6 Undelivered Workflow

1 Status to “Delivery Attempted”

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.
43
6 Undelivered Workflow

Status to
“Delivery
Attempted”
44
6 Undelivered Workflow

2 Currently full shipment delivery is being enforced. With

minor reconfiguration, partial delivery can be allowed.
45
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.
46
7 Damaged Parcels Workflow

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).
47
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.
48
9 Change of Address Workflow

A bad address
can be reported
by a hub
operator
49
9 Change of Address Workflow

Customer Support can change the address from the

web interface
50
9 Change of Address Workflow

An API for external integrations (e.g. chatbots) for

address change is available as well
51
9 Change of Address Workflow

The courier can

change the delivery
point without
changing the
delivery address in
the shipment.
52
10 Reschedule Workflow

Rescheduling can be
picked as a delivery fail
reason from the
courier’s app.

Rescheduling
53
10 Reschedule Workflow

The attempt
with the
corresponding
reason will be
seen from the
web interface.
54
11 Debrief Workflow

Runsheet debrief is done from the

admin area.

Collection debrief is done using Origin

inbound scans.
55
11 Debrief Workflow

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.
56
11 Debrief Workflow

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.
57
11 Debrief Workflow

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.
58
12 Linehaul Workflow
Containers (e.g. pallets, bags) are used to group parcels for
linehaul purposes.
Containers can be created from web interface:
59
12 Linehaul Workflow
Containers (e.g. pallets, bags) are used to group parcels for
linehaul purposes.
Containers can be created from web interface:
60
12 Linehaul Workflow
Containers can be created from hub worker’s app:
61
12 Linehaul Workflow

Once a container is created, labels and manifests are

available to be printed and downloaded.
62
12 Linehaul Workflow

Outbound Linehaul
MAWBs can be created to represent a complete haul that consists of multiple containers and separate parcels.
63
12 Linehaul Workflow

Outbound Linehaul
MAWBs can be created to represent a complete haul that consists of multiple containers and separate parcels.
64
12 Linehaul Workflow

Outbound Linehaul

During MAWB creation containers and shipments are added: Truck seal is recorded to ensure the security of the freight.
65
12 Linehaul Workflow

Outbound Linehaul
Created MAWBs can be departed, cancelled or edited. Manifest can be downloaded for each MAWB.
66
12 Linehaul Workflow

Outbound Linehaul

Example of a
MAWB manifest
67
12 Linehaul Workflow

Inbound Linehaul
Linehaul is handled through MAWB’s. MAWB is accepted as arrived by the hub staff after checking the seal on the
vehicle.
68
12 Linehaul Workflow

Inbound Linehaul
After unloading and container unpacking, multiple hub workers can scan
the parcels in parallel, each creating a scan batch.
69
12 Linehaul Workflow

Inbound Linehaul
After unloading and container unpacking, multiple hub workers can scan
the parcels in parallel, each creating a scan batch.
70
12 Linehaul Workflow

Inbound Linehaul

The scan batches from

the previous step are
then added to the
inbound MAWB.
71
12 Linehaul Workflow

Inbound Linehaul

After the batches were

added, separate parcels
can be marked as
damaged.
72
12 Linehaul Workflow

Inbound Linehaul

After the batches were

added, separate parcels
can be marked as
damaged.
73
12 Linehaul Workflow

Inbound Linehaul

If there are missing

shipments in the MAWB,
hub staff receives a
warning and have to
confirm that those
missing parcels are
actually missing.
74
12 Linehaul Workflow

Inbound Linehaul

After the MAWB receiving

process is complete - the
results are generated and
shown in the MAWB’s info.
75
12 Linehaul Workflow

Inbound Linehaul

MAWB’s info screen:

76
12 Linehaul Workflow

Inbound Linehaul
Using existing status functionality additional exception handling can be
added.

Linehaul Transit Mis-Sort

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

A shipment can be put

on hold by a hub
worker.
78
13 On-Hold Workflow
A shipment can be put on hold by a hub worker.
79
13 On-Hold Workflow

Similar process is in
place to remove a
parcel from ‘Hold’
status
80
13 On-Hold Workflow

Holding and revoking

the ‘Hold’ status
events can be viewed
from the shipment’s
details
81
13 On-Hold Workflow
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.
82
13 On-Hold Workflow

A parcel can be put on

a shelf or taken from it
by the hub worker
from the mobile app.
83
13 On-Hold Workflow

These events are also

visible in the
shipment’s details.

Additional statuses
and logic can be
added.
84
14 International Outbound Workflow
This can be implemented based on existing MAWB
functionality.

and finaly
Then selects the
From the Mobile selects selects the
Then 'Create Country code
App the operator ’International Delivery Partner
Route’ from a drop
Outbound’ from a drop
down list
down list

Note:
During order creation if a client
prefers to use a specific delivery
partner, the order is 'TAGGED'
with the Partner's ID and the
delivery data is pushed to them
via API - if no preference is set
the default partner is
automatically selected
85
15 Domestic and ITNL RTO Workflow

From the Mobile App

From the operator’s

app multiple
the operator selects shipments can be
‘RTO’ then assigned to RTO:

‘Create RTO – single

or bulk’
86
15 Domestic and ITNL RTO Workflow

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