Seven Senders will retrieve carrier message for you shipments and based on those messages, we will create some events to better represent what is currently happening for the orders and shipments.
You will find below all the possible events that can occur for your orders and shipments.
Order Events
| Event | Description | Trigger | Meaning | Max occurrence |
| Order cancelled | The order has been cancelled by the customer | Custom logic | REALLY BAD | 1 |
| Order completed | The order has been completed, all shipments have been delivered to the customer | Custom logic | GOOD | 1 |
| Order created | The order has been created | Custom logic | NEUTRAL | 1 |
| Order delayed | Based on the historical data and the shipment events, we know that the shipment will arrive after the Promised Delivery Date | Custom logic | BAD | 1 |
| Order is being prepared | The warehouse is currently preparing the order | Custom logic | GOOD | 1 |
| Order Paid | The order has been paid by the customer | Custom logic | GOOD | 1 |
| Order shipped | All the shipments for the order are ready or have been left the warehouse | Custom logic | GOOD | 1 |
| Ordered items are being produced | The ordered items are being produced at the factory | Custom logic | GOOD | 1 |
Shipment Events
| Event | Description | Trigger | Meaning | Max occurrence |
| 7S hub scan | The shipment has been scanned at one of our warehouses | Custom logic | NEUTRAL | No limit |
| Carded | Customer received a notification card inside his/her inbox | Carrier message | GOOD | No limit |
| Carrier changed | The carrier in charge pf the shipment was changed to improve the delivery performance | Custom logic | NEUTRAL | No limit |
| Contact carrier | Get in touch with the Last Mile Carrier (LMC) for clarification of further steps | Carrier message | BAD | No limit |
| Delayed | The shipment's delivery is delayed | Carrier message or custom logic | BAD | 1 |
| Delivered | The shipment has been delivered to the customer | Carrier message | GOOD | 1 |
| Delivered to a drop-off point | The returned shipment has been dropped off at a parcel station | Carrier message | BAD | 1 |
| Delivered to a pick_up point | The shipment was delivered to a pick-up point. The customer has to pick up the shipment | Carrier message | GOOD | 1 |
| Delivered to a third party | The shipment was delivered to a third party (e.g. neighbour, relative, etc.) | Carrier message | GOOD | 1 |
| Delivery address changed | The customer requested to be delivered to another address | Carrier message | NEUTRAL | No limit |
| Delivery appointment | An appointment for the delivery has been defined between the LMC and the customer | Carrier message | NEUTRAL | No limit |
| Delivery attempt failed | The carrier attempted to deliver the parcel but failed | Carrier message | BAD | No limit |
| Delivery date changed | The customer requested the carrier to change the delivery date | Carrier message | NEUTRAL | No limit |
| Delivery impossible | The carrier said that it is impossible to deliver the shipment | Carrier message | REALLY BAD | No limit |
| Delivery requested to the carrier | The delivery request has been transmitted to the carrier | Carrier message | NEUTRAL | No limit |
| Dropped off at Carrier Hub | This event is triggered when your shipments have been dropped off at the carrier hub. This event occurs before the "First Hub Scan" event | Custom logic | GOOD | 1 |
| FDA timeout | First Delivery Attempt timeout is created based on value set in Service Level Agreement (SLA) Settings | Custom logic | BAD | 1 |
| Fifth delivery attempt failed | The carrier attempted to deliver the parcel a fifth time to the customer but failed | Custom logic based on the "delivery attempt failed" event | REALLY BAD | 1 |
| Fifth delivery attempt succeeded | The carrier attempted to deliver the parcel a fifth time to the customer and succeeded | Custom logic based on the "delivered" event | GOOD | 1 |
| First delivery attempt failed | The carrier attempted to deliver the parcel to the customer but failed | Custom logic based on the "delivery attempt failed" event | REALLY BAD | 1 |
| First delivery attempt succeeded | The carrier attempted to deliver the parcel to the customer and succeeded | Custom logic based on the "delivered" event | GOOD | 1 |
| Fourth delivery attempt failed | The carrier attempted to deliver the parcel to the customer but failed | Custom logic based on the "delivery attempt failed" event | REALLY BAD | 1 |
Fourth delivery attempt succeeded | The carrier attempted to deliver the parcel a fourth time to the customer and succeeded | Custom logic based on the "delivered" event | REALLY BAD | 1 |
| General | There is an issue with the shipment which needs further investigation | Carrier message | BAD | No limit |
| Good address | This event is triggered after the event "Wrong address" when we receive a new delivery address in Seven Senders | Custom logic | GOOD | No limit |
| Heavy damage | Shipment was damaged heavily and is not on the way to customer anymore | Carrier message | REALLY BAD | No limit |
| Hub scan | The shipment has been scanned by the carrier | Carrier message | NEUTRAL | No limit |
| International | The shipment has been scanned by the carrier | Carrier message | NEUTRAL | No limit |
| Invalid tracking number | Seven Senders can be not retrieve tracking information with this tracking number | Custom logic | REALLY BAD | No limit |
| Light damage | Shipment was damaged but is till on its way to customer | Carrier message | BAD | No limit |
| Notify recipient | The shipment can not be delivered, an email was sent to the recipient | Carrier message | BAD | No limit |
| Out for delivery | The delivery vehicle is loaded with the shipment | Carrier message | GOOD | No limit |
| Postal return | The shipment has been returned to sender without having reached the customer | Carrier message or custom logic based on the SLA setting | BAD | 1 |
| Refused | The consignee refused the delivery | Carrier message | REALLY BAD | 1 |
| Received from pick-up point | The customer has received the shipment at the pick-up point | Carrier message | GOOD | 1 |
| Return shipment created | A return shipment for the given order has been created | Custom logic | BAD | 1 |
| Routing problem | The carrier has announced a problem in the delivery of the shipment | Carrier message | BAD | No limit |
| Second delivery attempt failed | The carrier attempted to deliver the parcel a second time to the customer but failed | Custom logic based on the "delivery attempt failed" event | REALLY BAD | 1 |
| Second delivery attempt succeeded | The carrier attempted to deliver the parcel a second time to the customer and succeeded | Custom logic based on the "delivered" event | GOOD | 1 |
| Shipment created | A shipment for the given order has been created | Custom logic | NEUTRAL | 1 |
| Shipment lost | The shipment has been lost during its way to the customer | Carrier message | REALLY BAD | 1 |
| Third delivery attempt failed | The carrier attempted to deliver the parcel a third time to the customer but failed | Custom logic based on the "delivery attempt failed" event | REALLY BAD | 1 |
| Third delivery attempt succeeded | The carrier attempted to deliver the parcel a third time to the customer | Custom logic based on the "delivered" even | GOOD | 1 |
| Tracking update | A new update are been provided by the carrier | Carrier message | NEUTRAL | No limit |
| Valid tracking number | This event is triggered after the event "Invalid tracking" number when we receive tracking information from the carrier | Custom logic | GOOD | No limit |
| Warehouse pick-up | The carrier has pick-up the shipment at the warehouse | Carrier message or custom logic | GOOD | 1 |
| Wrong address | Consignee address is not correct. Please contact customer | Carrier message | REALLY BAD | Not limit |