Propose deliveries at the most
competitive cost rate with
delivery options that better
meet customer requirements.
Contain Net Landed Cost
for every order with lower
delivery costs.
Increase the relevance
of the delivery SLA with more
appropriate transportation
services.
Become a more reliable
business partner as a result
of improved delivery experience.
Seamlessly adopt new carrier services in a shorter time frame.
Reliably implement innovative
services without compromising
operations.
Automate carrier service
selection process to optimise
cost to service ratio.
Enable close monitoring
of shipping operations and meet
any peak capacity demands
at any time.
Detect and process invoicing
errors based on a three-way
process – manifest, PoD and
invoice line.
Allocate all shipment costs
to the relevant order, cost
centre or line of business.
Provide a comprehensive
list of historical shipments
per origin service category.
Report on any relevant
performance indicators
to facilitate supplier
management.
Use real-time information
to enhance customer service
interactions. Identify failures
and proactively notify service
issues.
Monitor tracking patterns
to identify deviations from
planned sequences. Identify
the impact of external events
on delivery schedules.
Provide uniform delivery
information online with tracking
status consolidated to the order
level. Reduce the impact of
delays by reordering, diverting
or rerouting shipments already
in process.
Automated carrier selection
rules updates based on predicted failures.
For those who might be wondering what is the difference between MCSS and SRM, we have explained the main distinctive elements in the table below. Here you can see how Shipping Resource Management covers the functions of the Multi Carrier Shipping System and so much more.
| Features |
Traditional Shipping Systems |
Shipping Resource Management |
|---|---|---|
| Generate a list of valid shipping methods for an origin/destination/service | ||
| Dynamically identify the most appropriates shipping services for a line of business | ||
| Shipment tracking is based on carrier provided information | ||
| Customer order is tracked by merging all carrier provided events, predictive information and internally generated events | ||
| Customer is informed of any tracking issues and is provided with planned, actual and predicted events | ||
| Intelligent metrics dynamically drive carrier selections | ||
| Customer is provided with shipment related tracking information | ||
| Customer wants to know what is going on with the order as a whole, regardless of the shipment structure | ||
| Customer is proactively informed of any issues | ||
| Delivery occurs and proof of delivery is recorded | ||
| Data Model learns from new shipment information to drive future selection |
Now you have an overview of t2cloud.app™
and how it can benefit you. To learn more about
exactly what problems it can solve for you, fill out
this simple form
