Top of Page Privacy Policy 'Header' Title a b Privacy Policy

Top of Page Privacy Policy 'Header' Privacy Policy Title a b

Top of Page Requirements Direct-to-Print Labelling The no-hands, web based label solution for fully integrated customers... Are you looking to print parcel labels directly from packing the item? No manual searching or scanning for the HU in Event, just pack and print? The Direct-to-Print application uses the Label Station ID added to the Packing message to trigger the print of the label you have just packed. The application is a windows application It needs to be downloaded onto each Label Station PC Each PC must have a default printer setup Each Label Station must be given a unique name to differentiate it (Workstation01, Workstation02...) You will need to add this unique Label Station ID to the packing Order message you create On receipt of the packing Order message, Event will process the request automatically and output the correct label for exactly the packing Order sent. Expected performance is approx. 10 seconds per label* note : Direct-to-Print works only per packing Order message, it does not allow for consolidation as it creates per HU reference. Ready to activate? Make sure all the requirements have been met... Get Direct-to-Print Implementing Direct-to-Print How to start direct label printing This guide will step through getting started with hands free label generation What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 'How to' guide ...or access it from the activation page in Event itself. Save ...save the status. Direct-to-Print is now LIVE and ready to receive. What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 1/19 Now it's active, how do i use it? Once downloaded, the application will need to be opened each time the PC is switched on by the user. PIN the application fro the Start menu to the Task Bar to make it easier to access. Click on it to start it and minimise it again Start packing and labels will print on the PC default printer There is no need to open Event as the application works without it physically open. Application Open and minimise each shift. ROUTE configuration In ROUTE configuration, you can see if Print-to-Label is active. Application Open and minimise each shift. 1/2 Requirements Requirements to use Direct-to-Print A valid Event account with ROUTE, integrated parcel carriers with valid accounts. A valid interface from your ERP to Event [including the Label Station tag] Ability to download the windows application to each PC on each Label Station .net framework on each PC (https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer ) A default label print for each Label Station PC A package to put the label on... Support process At any point, when the application cannot connect and 'stops listening for labels' we will automatically generate a support ticket to the 3T Service Desk and your Admin account email address. This will be considered a Priority support ticket and acted on with immediate effect. Where a label cannot be returned, an error label will be produced to advise you of the issue If a label has a hazardous code associated we will generate an additional label to advise of this. * Label generation speed is approximate and based on the quality of your internet connection. Tested as below: http://www.speedtest.net Download speed 73.92 Mbps Upload speed 86.70 Mbps Response time 10 ms

Home - Documentation - Validation and certification (Event Go) Validation and certification Event Go Documention Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview Our test scenarios are meticulously crafted to ensure partners have accurately configured their systems to seamlessly interact with our Delivery as a Service APIs. Prior to going live, partners must successfully pass certification tests to validate integration against our specified requirements, ensuring a reliable interaction with our delivery services. Key verification points include: Estimate Payload Verification: Validate parameters such as weight, preparation duration, alcohol availability, target delivery time, and address accuracy. Delivery Payload Verification: Assess parameters including target collection time, vendor order ID, and special instructions. Request Identifier Mapping: Ensure proper mapping of requestId as a unique identifier for each SaaS delivery. Delivery Creation Verification: Confirm partners create the NEW, UPDATE, CANCEL, COMPLETE delivery API call to verify creation. De How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Top of Page Privacy Policy 'Header' Privacy Policy Title a b

Event Connect About Event Connect Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview How does it work? Onboarding About Event Connect Event Connect is an API logistics integration, aimed a providing a platform that fits the majority of Point-of-sale systems while at the same time giving the Event TMS with all the data it needs to provide the perfect Transport Management result for the customer. What is this partnership? Getting started Delivery simulation Validation and Certification

Home - Documentation - Integration flow (Event Order) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification Integration flow Our Point-Of-Order (Event Connect) integrations put your customers and order management processes front and centre, pushing incoming orders directly from your Point-Of-Sales system to Event TMS. This means for our integration an order flow of: A NEW, an order that has stock allocated is preferred An UPDATE, to the order if it needs to be amended A CANCEL, if the order is cancelled A COMPLETE, once despatched Event is trying to deliver all your orders the more efficient, cost effective say possible, so some rules help acheive this: Event is at Orderline level Imagine a shopping basket, all different products but going to the same destination. Each product is a line number. An order can have multiple products shipping, each one would be a line. For example. 1.001, 1.002, 1.003 An order number must be unique Once cancelled an order number cannot be reused. Date change if any uncertainity on the orders status. You need to tell us where, when and what to deliver The better the address, the more chance it will be delivered correctly. We validate on Google addresses The delivery date is required, we can calculate a collection date. The quantity, weight and dimensions or we dont know what to pack on a truck Event Go Documention Event Order sync flow Basic NEW order A customer can place an order at anytime. The 1st point to clarify is 'when' to tigger the NEW order through the Event Order API? This is usually when it has a stock allocation and the order is a confirmed. This can be 3, 4 or more days before due collection date. It can be 1 or 2 days. The planning cycle would expect to generally receive the orders the day before collection is due for optimisation, carrier allocation and notification. A basic order flow would be an order, with multiple orderlines, triggered to Event through Event Order. Event will validate the order, plan the order and trigger back a route informing you how and when the order will be collected. Event. NEW order Order accepted Plan result TMS Planning optimisation Event Connect Updating an order An order can be updated many times before it is despatched. To trigger these updates through Event Order, you can use the UPDATE prefix. Event uses this prefix to simply update the existing order rather than create a duplicate order. An UPDATE can be for many reasons BUT should always only be for actual changes to the order that affect its delivery. For example these are primary Update types: Quantity, weights Delivery Date Order instructions Product components We don't expect to receive updates that are triggered through your POS because the order is viewed and no primary update is made. Unneccessary messaging generates unlooked for cost. Are UPDATEs the same for parcels and pallets? An UPDATE can also be considered to be a 'pack confirmation'. So for a parcel, packing the orders and generating the actual weight and dimensions of the package. The enables Event TMS to calculate the correct mode and carrier to make the delivery, in the same way for palletised goods, the last UPDATE is always the last instruction for delivery at that moment in time. Event. TMS Event. TMS Plan result NEW order Order accepted UPDATE order UPDATE order Order accepted Order accepted Event Connect An order short? Short despatch, partial despatch, out of stock. All situations at the point of a truck leaving a depot to deliver that require attention. The prefered and most straightforward process is to cancel of the short and to input a new order for it, a new unique order or a new orderline. Original order 1.001, cancel off. Input order 1.002 as this would be a unique order. next... Additional information

Home - Documentation - How does it work? (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information How does it work? Here is an example of how we will take care of the last-mile logistics on your behalf: Customer creates an ORDERS and triggers through Event Order API Event TMS plans and optimises the order, allocating it to the best carrier and rate Event Go API will trigger the planned ROUTES back to the customer The preferred Logistics Provider will start the deliver and Event Go can trigger TRACKING UPDATES When the delivery is confirmed, Event Go can trigger DELIVERY CONFIRMATION with PROOF OF DELIVERY (POD) Any additional and approved COST ADDITIONS can be triggered by Event GO Finally, Event Go can trigger the logistics Providers Invoice breakdown to complete the delivery exacution of the order. Event Go Documention Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Onboarding

Home - Documentation - Overview (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Overview Welcome! Event Go is our last-mile delivery product that directly connects you to your logistics network. Through our external APIs, you can seamlessly request updates on the status of your orders delivering or delivered to your customer’s. This section provides documentation and resources to assist you in setting up your POS integration to receive delivery status updates using our suite of API's to your logistics network. Event Go Documention next... How does it work? Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Top of Page Privacy Policy 'Title' Privacy Policy Title a b

Home - Documentation - Getting started (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Getting started Environment-Specific Endpoint: In this section, you’ll find a comprehensive list of endpoint URLs tailored to different environments. Whether you’re testing on staging, developing locally, or production, ensures seamless integration by selecting the appropriate URL corresponding to your environment. Here is the Environment Specific Endpoints: UAT - POST https://event3tuat.azure-api.net /Oasis/omf PROD - POST https://event3t.azure-api.net /Oasis/omf General API Management Gateway - https://event3tuat.azure-api.net Event Go Documention Additional information Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Delivery simulation

Self-serve rate card import Uploading rate cards for carriers you connect with To use a non parcel carrier, you will need to upload a rate card A rate card simply shows where a carrier will deliver to and how much that delivery will cost... If you are using ROUTE in Event you will need to connect to carriers. To allocate routes to your connected carrier you need a rate card. Carriers in Event have a standard universal rate card or you can arrange and negotiate your own rates. This guide assumes you have created an account with a carrier, connected to them through Event and now need to upload your negotiated rate card so you can start allocating routes. Connect and allocate Decide on a carrier and create an account [contract] with the carrier (outside of Event) Connect to your chosen carrier through Event* Receive a 'carrier now connected' notification Create a rate card, upload. Start allocating routes to your carrier * A carrier will add themselves to EVENT through being invited. They only need to be invited once and in doing so will create access, login details and a 'connected' presence in the Event ecosystem overall for all current and future Accounts to connect to. You just need to upload a rate card.. * There is not set requirement for naming a rate card upload file. We will add a date time stamp to make sure it is unique Do not change the format of these rate cards! Download, change the date but not the headers or the tab names Which rate card do i use? The rate card templates are simply based on the a tariff in WEIGHT or PALLET based. Are you adding a groupage pallet tariff or one based on weight? hint: FTL is always added as weight. See the examples below to help you quickly create a rate card. If creating an FTL tariff, use the Template 1. This includes EXW. If creating an Groupage PALLET based tariff, use the Template 1 If creating an Groupage WEIGHT based tariff, use the Template 2 Standard plt / weight tariff click to download Template 1 FTL all postcode Rate card template PLT - Day / night / weekend / holiday 19-04-2023 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc This tariff includes where a carrier provides different costs based on the time of day or day of week It is only for the FTL sheet, not for Groupage Column J cannot be used if any of columns O-T are being used. Leave J as = blank Column U can be used with either column J or columns O-T. It can also be used on its own. The daytime setting can be configured in AccountVITALS / Setup Basics / Rate Card Bank holidays can be configured in AccountVITALS / Setup Basics / Holidays The headers for columns O-U will be used to show as the servie in Change Carrier Template 2 Groupage all UK postcode rate card template PLT. Upto 10 plts 12-02-2019 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Template 3 Rate card template weight - Groupage 12-02-2019 - AP Hint: Its important to define if the Groupage tariff is per weight band or pallet. The excel spreed sheet tab defines this Template 4 Rate card template weight bands- Groupage 17-09-2021 - AP This function includes 2 new columns. 'PER' column and 'ROUNDING' column. PER = rate per kg. This can be 1 as std or 100kg ROUNDING = set to round by, e.g. 10 (to mearest 10) The PER calculation example is: 99-250kg line in tariff rate = 39.98 Set PER rate as 100kg Shipped 145kg Set rounding to 10kg (nearest 10kg) so 150kg calculated rate = 39.98 x 1.5 Template 4a Rate card template weight bands with minimum charge 14-09-2022 - AP Template 5 Rate card template pallet per lifts - Groupage 17-09-2021 - AP This function is the standard Groupage rate card by pallet. The difference is a configuration to set between per plt or per lift. This Lift configuration will use the stackability from the Stop. If 7 plts and stackable, lifts = 3 lifts The default is per pallet. Groupage rate card by m3 Template 6 GRP rate card by m3 08-05-2021 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Use column F & G for calculating Stop volume (10-15 m3 band = 4.50 x total m3) Use column H & I for calculating Stop volume as a fixed total cost (10-15 m3 band = 180.00 fixed rate) To set the calcuation at PLANNED or DESPATCHED status, use the configuration in Carrier VITALS To speed up creating multi equipment type FTL rate cards... Template 7 FTL x3 equipment types UK postcodes template 12-02-2019 - AP Template 8 FTL x2 equipment types UK postcodes template 12-02-2019 - AP Distance tariff by metric Template 9 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated from a source postcode and by a metric, i.e. per tonne Distance tariff from point A-B Template 10 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated based on the actual distance banding from any location to any location. It is not dependant on any metric, simply a cost per distance by an equipment type Parcel tariff by service Template 12 Parcel tariff by weight and service 11-10-2021 - AP Tariff for calculating parcel wieght and service through SLM rules What if i want to use a carrier but i have no rate card? You do not need to add a rate card for a carrier to be able to use the carrier in Event. Using Event's 'Spot Rate' function lets you allocate to any carrier at any time Rate Card Validation So once you have uploaded a rate card, AMI will validate the contents and notify you of the result. The validation will include format and contents, providing information, where a failure occurs on what the failure is. Initial validation that must be passed to proceed; 1. Correct column headers Validation will fail if the headers are named differently to the template. Validation error message ' Column headers are not named correctly' 2. Correct order of the columns Validation will fail if the columns are not in the correct position. Validation error message ' Columns are not in the required positions' 3. Carrier ID Validation will pass if the carrier ID exists on the Account being uploaded to and will fail if the carrier does not exist in Account receiving upload. Validation error message for notification and storing ' Carrier ID must match the carrier's code in Carrier VITALS' Specific validation 1. Origin country Is required. Format is ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 2. Origin code Is required. Format can be numbers or letters. CV, 01, 850. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV, 11, 98' 3. Destination country Is required. Format ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 4. Destination code Is required. Format c an be numbers or letters . CV 22 6HL , CV 22, CV , 01, 01000, 10000. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV22, 11, 98' 5. FromBand Is required. A number of at least 0. Can be format 1.000000001. Validation error message 'Must add a number in the format 1 ' Example: for FTL this would be 1 6. ToBand Is required. A number of at least 0. Can be format 1.000000001 if Groupage. Validation error message 'Must add a number in the format 2.000000001 ' Example: for FTL this would be 99999 7. Stop rate Is required if Delivery type = FTL. Format must be 0.00. Validation error message ''Rate must be included for FTL and cannot be left empty. It can be 0.00' 8. Equipment Is required. Validate the equipment type against the Account Equipment database and if a match can be found allow, if no match fail validation. Validation error message '[failed equipment name] is not a valid equipment type for this Account. Please use a valid type or update your equipment' 9. SLM rule Not required. Default is blank. This is a specialist rule for RULE ASSIST only. Max characters = 10 Validation error message where not matching rule is found in SLM 'No matching rule found in Route Assist rules' To use this rule, ROUTE ASSIST rules for the carrier must match those in the rate card. To use this function, add the SLM rules to the ROUTE ASSIST column called 'Groupage type' *this rule will lookup ROUTE ASSIST rule, take the associated Groupage Type and when looking up the rate card, will look to match a SLM rule to the Groupage type added. 10. Mode Is required. Must be LAND, AIR or SEA. AMI will default to LAND if not added. If added but not one of the 3... Validation error message 'Mode must equal LAND, SEA or AIR in this format ' 11. Service Is required. Default is Economy. AMI will default to Economy if not added. If added but not Economy, check for match in Account's Service and update. No validation message. 12. Delivery type Is required. Must be '2' for FTL or '4' for Groupage. Validation error message 'Delivery type must be '4' for GROUPAGE or '2' for FTL' 13. Cost Is required. validation just a number. Must be a number in format 0.00, 200.00. Can be 0.00 if no rate is known. Validation error message 'A rate must be included and cannot be left empty. Format is 0.00. It can even be 0.00 '