The shipment is already going there. Your data should ride with it.
Send us the data that your business uses. It can come from a TMS, an ERP, a spreadsheet, or a function that you write. We attach it to the shipment as fields that you define. Then we give it to the company that needs it, in the format that they use.
Four problems that look like labor problems.
These problems do not look like shipping problems. This is why they continue. The data that can solve them is already in your business. But the data cannot get to the person who needs it, at the time when they need it. Therefore, a person does the work by hand.
-
01
One leg of the route exists only because data cannot move.
You ship in bulk to a partner. At that partner, a person does this work:
- Opens the pallet
- Identifies each unit
- Matches each unit to a customer
- Ships each unit again.
The shipment does not need to go to that partner. You use the partner because you cannot give them the data for each unit.
What it costsEach cycle takes more days. Your partner operates a sort facility that neither company wants.
With the data attachedYou ship directly to the customer. The data for each unit goes with the shipment. The extra leg is not necessary.
-
02
Your proof is in a system that no other company can see.
You record the evidence for each shipment. This evidence can include:
- Photographs of the contents
- Inspection records
- Certificates
- Weights and lot numbers.
You keep these records in your own system. The records become visible only after a customer makes a claim. At that time, they cannot prevent the claim.
What it costsEach claim becomes an investigation. The records that you pay to make give you no other value.
With the data attachedYour customer sees the records before the shipment arrives. The records then prevent claims.
-
03
Two systems that will not connect to each other.
Your TMS has the transportation data. Your ERP has the value of the goods. The system of your customer has neither. A direct connection to each customer is a separate project. Your customer does not want that project either.
What it costsA person sends a spreadsheet each week. Another person types data that is already in two systems.
With the data attachedEach company connects one time, to Delivered. The shipment then carries the data between the two companies.
-
04
Revenue waits for a status that no carrier publishes.
You must wait for one specific event at the end of the route. Until that event, you cannot make an invoice, close the ticket, or start the next step. The event occurs on time. But your billing system cannot read it.
What it costsYou invoice later than necessary. Your team must reconcile the shipments at the end of the month.
With the data attachedDelivered gives the event to your systems as a field. Your systems read it immediately.
In each example, the shipment goes to the correct place. The data does not.
A shipment is also a delivery of data. It moves a box at the same time.
One hand-off carries two things.
- serial
- patient id
- photos
- your PO
- lot
The shipment arrives. Now the data arrives at the same time.
A shipment is a hand-off between two companies. It has a schedule, a record of events, and an agreement about the time of delivery. Your company already has this.
The shipment does not carry the data that makes the hand-off useful:
- The serial number or the lot number
- The account or the customer that the unit belongs to
- Photographs of the contents
- The one field that lets the other company close its ticket.
Therefore a person does that work by hand. A person sorts a pallet. A person sends a spreadsheet. These are not labor problems. They show the cost of data that cannot move.
Any data in. One shipment. Any format out.
Send us the data in the format that you use now. Or write a small function, and we run it to get the data. We attach the data to the shipment as fields that you define. Then we give the data to the receiving system in its own format.
- Your TMS
- Your ERP or WMS
- A spreadsheet that a person maintains
- Airtable, S3, a shared drive
- A function that you write
You can push the data to us. Or your own function can pull it. Your credentials stay with you.
- Normalized stateIn transit
- Your order numberSO-44812
- SerialCX-99417-B
- Asset or account idyour field, your name
- Attached documents3 files
You define these fields. We do not give you a schema. The shipment becomes the place where the answer is.
- They pull it from our API
- We push a webhook
- We deliver a file in their format
- A function running on their own tenant
- The tracking page and notifications
There are four methods. The receiving company uses the method that it supports now.
You do not build a connection to each partner. Neither company does work when the other company changes its systems.
Connect to each partner, or connect one time.
The same partners. The same systems. Only one of these projects is realistic.
You define the fields. We do not give you a schema.
Most platforms give you a fixed set of fields. If you need a different field, you must open a support ticket. With Delivered, you make the fields. You give them the names that your business uses. You also control which companies can see each field.
Your data can be in a system that we do not know. If it is, you write a small function. The function runs on your own tenant. It gets the data when a shipment needs it. Your credentials stay on your side.
The data leaves in the same way. The receiving company can use one of these methods:
- Pull the data from our API
- Receive a webhook
- Receive a file in its own format
- Run its own function on its own tenant.
The company selects the method that it supports now.
Tell us about the work that a person does by hand.
Give us one example. It can be the pallet that a partner sorts again. It can be the spreadsheet that a person sends each week. If data is the reason for that work, we will show you the process without it.
Bring one workflow. You do not move your systems to test this.