JCB US / Canada JCB UK JCB FR JCB CZ JCB NL

Top of Page Privacy Policy Policies Privacy Policy Our Privacy Principles If you read nothing else, please read this: The most fundamental privacy principle 3T Logistics Ltd (“we”, “3T”, “us” and “our”) follow is that by default, anything you add to 3T’s EVENT control Platform is private to your Company. That is, files shared, orders added within a specific EVENT control application requires authentication as a member of that team. 3T is the custodian of data on behalf of the companies that use the EVENT control Platform. We don’t own EVENT user data. EVENT users own their data. They like it that way and so do we. At 3T we believe that more transparency is better than less. We try to make our product easy to use, with settings and options that are easy to find and understand. This is good for privacy, good for the product, and good for 3T customers and users. Privacy goes hand in glove with security and confidentiality. We see these things being the three legs that keep the stool balanced and upright. Each is as important as the other and if one is missing the stool won’t stand. They are all very important to us and we take them very seriously. For the purposes of the applicable data protection laws, legislation and regulations, the data controller is 3T Logistics Ltd. We are registered in England and Wales under company number 03973355 and have our registered office at 5 Smith Way, Grove Park, Enderby, Leicester, LE19 1SX. Privacy Policy LOCATION SERVICES PRIVACY POLICY 1. What Location Data We Collect When you use INCAB, we collect your device's precise location (based on GPS, Wi-Fi and mobile network signals) to provide the app's delivery features. 2. How and When We Collect It We only access your device's location if you grant permission. - While you use the app: to show your position on the job map and to record where each job step (start, arrival, collection, delivery) takes place. - In the background: only after you tap Start on a delivery stop, and only until that delivery is completed or marked as failed. During this time INCAB records your position as the vehicle moves, even if the app is minimised or the screen is off. INCAB does not collect location in the background at any other time. 3. Why We Need Your Location - To show the transport company where the delivery is in real time and to calculate its estimated arrival time. - To keep the customer receiving the goods informed about the delivery's progress and arrival time. - To show your route and stops on the map. - To record where each stop was started, reached and completed as part of the proof of delivery. 4. Who We Share It With - The transport company you drive for, which assigned the job, through the EVENT control Platform. - The customer receiving the delivery, who can see its progress and estimated arrival time. - Service providers acting on our behalf: mapping and routing providers (such as Google Maps) to display routes and calculate arrival times, and Microsoft Azure, which hosts the EVENT control Platform. We do not sell, lease or trade your location data to advertisers or data brokers. 5. Managing Your Choices & Revoking Consent You can change or withdraw location permission at any time in your device settings: - iOS: Settings > Privacy & Security > Location Services. - Android: Settings > Location > App permissions. If you turn off location access, you can still use INCAB, but live delivery tracking and map features will not work. 6. Data Retention and Deletion Location data recorded during a job is kept as part of that job's delivery record on the EVENT control Platform for as long as the transport company needs it for its records. It is deleted if the job is cancelled, and you can ask us to delete your data using the contact options below. We may keep some delivery records for longer where the law requires it. 7. How We Protect Your Data Location and other data are sent over encrypted connections (HTTPS) and are only accessible to authorised users of the transport company and authorised 3T staff. 8. Contact Us For questions about this policy or your data, use the "Contact Us" form in the footer of any page on https://www.3t-event.com .

Top of Page JCB Miami JCB California JCB Edmonton JCB Chicago JCB Czech JCB WPC JCB NL FedEx integration QA Home / JCB Worldwide The story of JCB is one of innovation, ambition and sheer hard work. From small beginnings building agricultural tipping trailers in 1945, to the global force in manufacturing the company has become today. JCB Miami JCB - Miami [interfaced] Account ID: JCBMiami Production event.customer10@3t-europe.com JCBMiami135 QA event.customer7@3t-europe.com JCBMiami1 FEDEX FedEx production account number: 859296319 FedEx production Meter Number: 112760401 FedEx production access key: IfKuzooFOEd6qX0z FedEx access key password: 632fEhHNe9uIhklV0WrOt1zMt JCB Miami address file UPS UPS account number: 583E6Y UPS Access key: j5D4705B7CBB4C588 UPS.com User ID : 333TTTJCBUS UPS.com Password : US333tttJCB! EXW54 Miami AP 210819 DHL DHL account number: 960597529 Country code: US JCB California JCB - California [manual entry] Account ID: JCBAUS2 Production / QA event.customer34@3t-europe.com Eventjcb34 JCB Sacremento EXW rate card AP2211 FEDEX FedEx production account number: 282394251 FedEx production Meter Number: 113912896 FedEx production access key: ROPO6Aizwe9rzcWf FedEx access key password: gM91qBAZpTfHMUrfpgkIcmo88 UPS UPS account number: 583E6Y UPS Access key: 9D5ED571D83DC9FA UPS.com User ID : 333TTTJCBUS UPS.com Password : US333tttJCB! DHL DHL account number: 960597529 Country code: US JCB Edmonton JCB - Edmonton [manual entry] Production prod.event.customer137@3t-europe.com JCBCanada137 Account ID: JCBACA1 UAT uat.event.customer9@3t-europe.com JCBCanda72 JCB Edmonton EXW rate card AP2211 JCB Chicago JCB - Chicago [interface] Account ID: JCBACA1 DEV sparhawk71972@gmail.com Sparhawk72 QA sparhawk71972@gmail.com Ghend1972 PROD event.customer52@3t-europe.com JCBChicago72 QA - DHL DHL account number: 847082869 Country code: US JCB Chicago EXW rate card AP260519 QA - UPS UPS account number: A90032 UPS Access key: 9D5ED571D83DC9FA UPS.com User ID : 333TTTJCBUS UPS.com Password : US333tttJCB! QA - FEDEX FedEx production account number: 510087640 FedEx production Meter Number: 119035731 FedEx production access key: Z7MYIlwqmYG9wA3m FedEx access key password: P37LVi47zKSnfooo3vFIHZhfO JCB Czech JCB - Czech [interface] Account ID: ? Production mirixik160@kahase.com Sparhawk72 QA event.customer52@3t-europe.com Sparhawk72 QA - DHL DHL account number: 304599385 Country code: CZ JCB WPC JCB - WPC [interface] Account ID: ? DEV ACCOUNT wpc@mailnow2.com Sparhawk72 DEV CONNECT xpo@mailnow2.com Sparhawk72 QA ACCOUNT jcbwpc@cnetmail.net Sparhawk72 JCB NL JCB - NL UAT uat.event.customer23@3t-europe.com JCBNetherlands23 interface Account ID: ? Production prod.event.customer69@3t-europe.com JCBNetherlands69 FedEx integration QA FedEx integration replace credentials for QA Below are the indications to request new test credentials. Doing so de-activate any previous ones requested. ------------------------------------------------------------------------ Access to web-services developer resource here login: jcbinbound Pass: jcbinbound1 Page to request credentials: here on this page, change email to the one you want to receive the credentials on: Then Continue and accept. Will display the new credentials and send additional info per email. Full credentials are a combination of both.

3T is a leader in network solutions and logistics / transportation software, 3T's Event software redefines how you optimise the position of your business on a global scale in todays digital world. Event. Start building your next integration with Event Connect Register interest View documentation Technology that improves your business Our Event Connect API solutions are designed to be innovative and easy-to-use, allowing you to build new experiences with our TMS. Speed up your development with our specialised integrations: EVENT Order – order message solutions EVENT G0 – delivered receipt solutions View documentation Order Message solutions EVENT Order is our point-of-order integration pushing incoming orders directly into the planning and optimised plan information back Learn more Order Tracking solutions EVENT Go are a suite of API's that directly connect you to your logistics network through Event. It provides visibility, delivery and invoice detail so you can stay in control of keeping your customers happy. Learn more POD / Invoice solutions EVENT Go includes tracking, proof-of-delivery, additional cost requests and invoice detail from your chosen logistics providers Learn more

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

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 '

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

Home - Documentation - Additional information (Event Order) Event Order API (POS) Additional information For more information on how to integrate your POS with Aptean Event, please visit our API Developer Portal . Event Go Documention About our Partnership How does it work? Integration flow Additional information next... Event Go - Overview Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification

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 / Product Line Carrier Connect API Our connect API landing page is below, here you can download the swagger, see example json requests and code examples. API documentation Once you are ready to get started please send an email over to servicedesk@3t-europe.com . We will send you back an API key that you can use for testing purposes. An API for Carriers to plug into Event This API allows carriers to pull data from Event, update Event with tracking, shipping labels and much more. Retrieve a route from Event In Event each of your routes will have a unique id number, this id can be found in connect. This unique identifier can be used to communicate with Event through our API and pull back route data for a specific route id. Example below. https://event3tdev.azure-api.net/carrierconnect/route/1e11Em49 This will return all the route detail for this route and all the detail for each of the stops on the route. Get all routes by collection date You can also pull all your routes for a given collection date. https://event3tdev.azure-api.net/carrierconnect/routes/2022-09-07 This will return a collection of routes, it will still included all the stop level detail. Get all customers you are connected to in Event If at any time you want to see all of the customers you are connected to in Event, you can call the operation below. https://event3tdev.azure-api.net/carrierconnect/accounts/ No parameter needs to be passed, we will identify who you are by the key you have passed in the request. Update routes and stops in Event The connect API also gives you the ability to send us information and update your routes/stops in Event. For example the below operation can be used to send us back shipping labels, documents and costs. https://event3tdev.azure-api.net/carrierconnect/stops/ Send us tracking updates You can send us back tracking information using the operation below, there is also the option to send us back GPS information so we can track the shipment on route. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Need us to push updates to you? If you need us to push information to you we have got you covered, using the operation below you can register a url for us to send webhook notifications to. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Currently, our recommended best practice for securing Webhooks involves using basic authentication and HTTPS on your endpoint. This will help prevent any altering of any information communicated to you by 3T, prevent any third parties from seeing your webhooks in transit, and will prevent any third parties from masquerading as 3T and sending fraudulent data. 3T performs certificate validation and requires any TLS-enabled (HTTPS) webhook recipients to have a certificate signed by a public trusted certification authority. We do not support sending webhooks to over SSLv2, SSLv3, or any connection using so-called export-grade ciphers. The example response shows the webhooks event you will receive to your endpoint once it is enabled.

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 - 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