**Chart Insights**: Dive into the "Shipments Per Hour" chart to identify peak shipping times. Adjust your operations to manage high-demand periods more effectively.
An effective filtering bar is nestled on the left side of the date filter. This feature empowers users to precisely narrow down the displayed shipments based on personalised criteria. Notable options within this filtering bar encompass: - **Couriers**: Facilitates the selection of specific couriers for tracking purposes. - **Friendly Service Name**: Enables searches for shipments linked to specific courier presets via the Friendly Service Name filter. Service IDs or preset names can be input here. For example, the "IPX-DPDND" Service ID or the corresponding name "DPD Parcel Next Day" can be utilised. Reference to the "[How to Add a Courier Service](https://shipping-documentation.despatchcloud.app/books/courier-directory/page/how-to-add-a-courier-service)" document can provide further insights into courier services and presets. - **API Account**: This option allows the selection of API accounts for tracking, which is particularly useful when multiple accounts are in use. - **To Country**: Offers the ability to focus on shipments destined for particular countries. - **Tracking**: This feature permits the tracking of shipments with specific statuses, including "Booked," "Collected," and "Delivered." - **On-Time/Late**: This feature facilitates tracking shipments with defined time-based statuses such as "Expected Late," "Expected On Time," "Delivered Late," or "Delivered On Time." These filtering options allow users to tailor their tracking experience to align with their specific requirements.Click to Play or Pause the video
# Integrating Your Voila Account on Mintsoft ## **Overview** This document provides step-by-step instructions for integrating your shipping account with Mintsoft. ### **Configuring a Courier Integration on [](https://shipping-documentation.despatchcloud.app/uploads/images/gallery/2025-02/tT4voila.png)** Follow these steps after logging into your Mintsoft account: 1. **Expand the "Connect" Menu:** - From the left side menu, expand the "Connect" entry. 2. **Select "Courier Integrations":** - From the expanded "Connect" menu, select the "Courier Integrations" option. 3. **Locate "HubEurope":** - In this example, we will use "HubEurope". Click "Custom" to find it. Once officially released, it will be under the "Partners" tab. For other couriers, select the desired option from these tabs and lists. 4. **Select "HubEurope":** - Choose "HubEurope" from the list of couriers. 5. **Add Account:** - Click "Add Account" in the top right corner of the page. 6. **Fill in Account Details:** - **Password:** Enter your "API Token". - **AccountNo:** Enter your "API User". - For more information on obtaining these details, visit our **[API Accounts page](https://shipping-documentation.despatchcloud.app/books/api-accounts/page/api-accounts).** - Once the details are entered, click the "Add" button on the right side of the page. 7. **Sync Services:** - After creating an account and redirecting to the previous page, click the yellow "Sync Services" button. This action pulls a predefined list of presets into Mintsoft. Ensure that you provide the list of required presets to Despatch Cloud. Only the Despatch Cloud team can populate the presets list, and future additions must be requested via a support ticket. They will create the appropriate presets on the API Account with matching IDs and company authentication for the courier client. [](https://documentation.despatchcloud.com/uploads/images/webp/Shipping/Shipping_MI_01-06.webp) ### **Selecting a Courier Integration** To select and use the newly installed courier, follow these steps: 1. **Expand "Shipping Management":** - From the left side menu, expand the "Voila Management" option. 2. **Choose "Courier Service Selection":** - Click the "Courier Service Selection" option from the listed entries. 3. **Select Your Courier:** - Locate the "Courier Service" dropdown and select the appropriate courier you wish to use. [](https://documentation.despatchcloud.com/uploads/images/webp/Shipping/Shipping_MI_07-08.webp) # Print More on 6x4: API Quick Guide ## **Overview** This document outlines how to enhance the printing of information on 6x4 thermal paper using API customisation. This is achieved by adjusting keys such as "label\_size" and "generate\_packing\_slip" to include order details, item specifics, and quantities on a single packing slip. ### **Efficient 6x4 Printing on [](https://shipping-documentation.despatchcloud.app/uploads/images/gallery/2025-02/tT4voila.png)** To enable the printing of additional information on a 6x4 paper size using the API, adjust the following keys in the API request: - **"shipment":** **{** **"label\_size"**: **"8x4"**, **"generate\_packing\_slip"**: **true** **}** Once these keys are configured as specified, the output can still be printed on a 6x4 paper. This customisation appends the order reference number ID and the individual items within the package to the bottom of the paper. The printed details include the SKU, Item Description, and quantity (qyt) for each item. It's important to note that this method can accommodate up to three items within a single shipping slip; however, if an attempt is made to include more than three items, an additional 6x4 paper will be utilised. To observe the real-time functionality of this customisation, you can experiment with it in our API playground. [Navigate to the API Playground](https://playground.courierapi.co.uk/index.php) and follow the steps outlined below to gain insights on effectively implementing this feature: 1. In the API request's shipment section, ensure "label\_size" is set to 6x4 and "generate\_packing\_slip" is set to false. 2. Click "Send Request" then "View Label" to generate and view the shipping slip. 3. Observe the shipping label without the packing slip at the bottom. 4. Return to the API playground and modify "label\_size" to "8x4" and "generate\_packing\_slip" to true. 5. Click "Send Request" again, followed by "View Label." 6. Witness the inclusion of a packing slip at the bottom on the same 6x4 roll used for shipping labels. You can apply the same keys in your API requests for similar outcomes, compatible with any courier.Click to Play or Pause the Video
# Requesting Low-Volume Royal Mail Tracking ## **Overview** If you ship between 25,000 and 300,000 items annually and wish to utilise Royal Mail's parcel tracking application, follow these steps to request Low Volume Royal Mail Tracking: - **Contact Your Account Manager** - Initiate the process by contacting your designated account manager. Inform them of your interest in low-volume Royal Mail Tracking. Your account manager will facilitate the connection with Royal Mail API support. - **Connect with Royal Mail API Support** - Your account manager will put you in contact with Royal Mail API support. This team will guide you through the steps to enable low-volume royal mail tracking for your shipments. - **Register for an App** - Following instructions from Royal Mail API support, register for an application on the Royal Mail Developer Portal at https://developer.royalmail.net/. This registration is crucial for obtaining the required credentials for tracking. - **Create an Application** - Once registered, create a new application on the Royal Mail Developer Portal. This process will generate a unique client key and secret for your application. - **Obtain Client Key and Client Secret** - After creating the application, note the provided client key and secret. These credentials will be used during the authentication process for both Royal Mail and Click and Drop APIs. - **Configure Authentication** - Enter the client key and client secret in the authentication section of your Royal Mail or Click and Drop API settings. This configuration is essential to enable tracking functionality for your shipments.**Limitations of Low-Volume Tracking: **Remember that Low-Volume Royal Mail Tracking has limitations. It allows only two daily tracking events spaced 12 hours apart. Be mindful of this restriction when planning and managing your tracking activities.
Following these step-by-step instructions, you'll successfully request and set up low-volume Royal Mail Tracking for your shipping operations. Contact Royal Mail API support for further assistance if you encounter any challenges. # The Windsor Framework ## **Overview** The **Windsor Framework** is a bilateral agreement between the United Kingdom (UK) and the European Union (EU) that governs the trade relationship between Great Britain (GB) and Northern Ireland (NI) following Brexit. This framework replaces the Northern Ireland Protocol and is designed to simplify customs procedures while ensuring that Northern Ireland retains access to the EU Single Market. This document outlines the implications of the Windsor Framework on your shipping operations, the data required for creating compliant shipment labels, and the necessary steps to ensure continued compliance. ### **What Is the Windsor Framework?** The Windsor Framework introduces new customs and trade regulations that govern the movement of goods from Great Britain to Northern Ireland. Key aspects of the framework include: - **Simplified Customs Procedures:** The level of customs data required depends on the trade category: - Business-to-Consumer (B2C), - Consumer-to-Consumer (C2C), - Business-to-Business (B2B). - **Green and Red Lanes:** - **Green Lane:** Goods that are deemed "not at risk" of entering the EU will be subject to simplified checks and fewer customs requirements. - **Red Lane:** Goods considered "at risk" of entering the EU will require a full customs declaration, including additional details to ensure compliance with EU regulations. - **Timelines:** Initial changes were scheduled to take effect by **30 September 2024**, with full compliance expected by **31 March 2025**. However, timelines remain subject to UK government updates. Please refer to the official HMRC guidance for the latest updates, **[UK government’s official guidance.](https://www.gov.uk/government/publications/the-windsor-framework)** ### **How the Framework Affects Your Shipping Process** When shipping from Great Britain to Northern Ireland, additional data is required in shipment label requests to ensure accurate customs declarations and correct routing. Data requirements vary between **B2C/C2C** and **B2B** shipments. #### **For B2C and C2C Shipments** - **Basic Consignment Data:** - Sender and recipient names, addresses, and contact details - Parcel weight and total consignment value - A plain English description of the shipment contents - **Customs Formalities:** B2C shipments typically require simpler customs data when following UK Carrier Scheme guidelines, provided the goods are **not at risk** of entering the EU. #### **For B2B Shipments** B2B shipments require more detailed data so that your shipment can be classified as either “green lane” (not at risk) or “red lane” (at risk). In addition to the basic consignment data, you must provide: - **Mandatory Fields:** - **Sale Type:** Specify whether the shipment is B2B or B2C - **Number of Pieces and Total Value:** Comprehensive details of the goods. - **Commodity Details:** - Commodity codes (HS codes) – 6 or 10 digits, as required. - Descriptions, quantities, unit weights, and unit values - Country of manufacture - Deferment account details (if applicable for customs charges). - **UKIMS Number:** - Either the sender’s or recipient’s **UKIMS number** is required. - If missing, the shipment defaults to B2C rules and may be considered **at risk**. - **EORI Number:** - The sender’s **EORI number** is mandatory. - If a recipient’s **UKIMS number** is provided, their **EORI number** must also be included. - **Clearance Declaration Details:** These details differ based on the lane: - **Green Lane (Not at risk):** Only minimal extra data is needed when UKIMS details are included. - **Red Lane (At risk):** Requires a **full international dataset**, similar to an H1 declaration, along with additional customs information and may be subject to EU duties. ### **Data Fields Required When Creating Shipping Labels** Please check the courier requirements table for the couriers that you are using to fully comply with the courier requirements for the Windsor Framework: To ensure compliance with the Windsor Framework, the following key fields must be included in shipment label data: #### **Core Data Fields** - **Sale Type:** Identifies whether the shipment is **B2B, B2C, C2C, or C2B**. - **Commodity Details (for B2B Shipments):** - **Commodity Code (HS Code).** - **Detailed Description:** quantity, unit weight, unit value, country of origin. - **UKIMS Number:** shipper and/or recipient. - **EORI Numbers:** shipper’s EORI required; recipient’s EORI required if UKIMS details are included. - **Additional Commodity Details:** as required by the carrier.Our documentation will be continuously updated as new regulations emerge, including carrier-specific compliance requirements.
**Courier Requirements**| **Fields/Courier** | **RoyalMail** | **Whistl** | **RoyalMail ClickAndDrop** | **Yodel** |
| **Supported Sales Types:** | B2B / B2C | B2B / B2C | B2B / B2C | B2C |
| **courier.sale\_type** | Required | Required | Required | N/A |
| **ship\_to.ukims\_number** | Required for B2B shipments unless ship\_from.ukims number isn't entered | N/A | Required for B2B shipments unless ship\_from.ukims number isn't entered | N/A |
| **ship\_from.ukims\_number** | Required for B2B shipments | N/A | Required for B2B shipments | N/A |
| **ship\_to.eori\_number** | Required for B2B if ship\_to.ukims number is entered for B2B | N/A | It is required for B2B if ship\_to.ukims number is entered for B2B | N/A |
| **ship\_from.eori\_number** | Required for B2B | N/A | Required for B2B | N/A |
| **item.sku** | Required | Required | Required | Required |
| **item.quantity** | Required | Required | Required | Required |
| **item.description** | Required | Required | Required | Required |
| **item.value** | Required | Required | Required | Required |
| **item.currency** | Required | Required | Required | Required |
| **item.origin\_country** | Required | Required | Required | Optional |
| **item.hs\_code** | Required | Required | Required | Optional |
| **item.weight** | Required | Required | Required | Optional |
| **courier.export\_reason** | N/A | N/A | N/A | N/A |
| **courier.sender\_deferment\_account** | N/A | N/A | N/A | N/A |
| **Note** | Either ship\_to UKIMS or ship\_from.ukims number is required for B2B shipments | UKIMS and EORI numbers should be configured on Whistl interface | Either ship\_to UKIMS or ship\_from.ukims number is required for B2B shipments |
| **Fields/Courier** | **Evri Corporate** | **Hermes Corporate** | **DPD UK** | **DPD Local** | **DPD Ireland** |
| **Supported Sales Types:** | B2C / C2C / C2B | B2C / C2C / C2B | B2B, B2C, C2C | B2B, B2C, C2C | B2B, B2C, C2C |
| **courier.sale\_type** | N/A | N/A | Required | Required | Required |
| **ship\_to.ukims\_number** | N/A | N/A | Required for B2B shipments unless ship\_from.ukims number isn't entered | Required for B2B shipments unless ship\_from.ukims number isn't entered | Required for B2B shipments unless ship\_from.ukims number isn't entered |
| **ship\_from.ukims\_number** | N/A | N/A | Required for B2B shipments if not at-risk goods | Required for B2B shipments if not at-risk goods | Required for B2B shipments if not at-risk goods |
| **ship\_from.vat\_number** | N/A | N/A | Required for B2B At Risk Goods | Required for B2B At Risk Goods | Required for B2B At Risk Goods |
| **ship\_to.vat\_number** | N/A | N/A | Required for B2B At Risk Goods if ship\_from.vat\_number not entered | Required for B2B At Risk Goods if ship\_from.vat\_number not entered | Required for B2B At Risk Goods if ship\_from.vat\_number not entered |
| **ship\_to.eori\_number** | N/A | N/A | Required for B2B if ship\_to.ukims number is entered for B2B | Required for B2B if ship\_to.ukims number is entered for B2B | Required for B2B if ship\_to.ukims number is entered for B2B |
| **ship\_from.eori\_number** | N/A | N/A | Required for B2B | Required for B2B | Required for B2B |
| **item.sku** | Required | Required | Required | Required | Required |
| **item.quantity** | Required | Required | Required | Required | Required |
| **item.description** | Required | Required | Required | Required | Required |
| **item.value** | Required | Required | Required | Required | Required |
| **item.currency** | Required | Required | Required | Required | Required |
| **item.origin\_country** | Required | Required | Optional for B2C&C2C but Required for B2B | Optional for B2C&C2C but Required for B2B | Optional for B2C&C2C but Required for B2B |
| **item.hs\_code** | Required | Required | Optional for B2C&C2C but Required for B2B | Optional for B2C&C2C but Required for B2B | Optional for B2C&C2C but Required for B2B |
| **item.weight** | Required | Required | Required | Required | Required |
| **courier.at\_risk** | N/A | N/A | Required | Required | Required |
| **courier.export\_reason** | N/A | N/A | N/A | TBD | |
| **courier.sender\_deferment\_account** | N/A | N/A | N/A | TBD | |
| **Note** | TBD |
| **Fields/Courier** | **RoyalMailIntersoft** | **ProCarrier** | **Hermes** | **DHLParcelUKCloud** |
| **Supported Sales Types:** | B2B / B2C | TBD | B2C / C2C / C2B | B2C / B2B / C2C / C2B |
| **courier.sale\_type** | Required | TBD | N/A | Required |
| **ship\_to.ukims\_number** | Required for B2B shipments unless ship\_from.ukims number isn't entered | TBD | N/A | Required for C2B. Required for B2B if ship\_from.ukims is not entered |
| **ship\_from.ukims\_number** | Required for B2B shipments | TBD | N/A | Required for B2B |
| **ship\_to.eori\_number** | Required for B2B if ship\_to.ukims number is entered for B2B | TBD | N/A | Required for C2B. Required if ship\_to.ukims is entered |
| **ship\_from.eori\_number** | Required for B2B | TBD | N/A | Required for B2B |
| **item.sku** | Required | TBD | Required | Required |
| **item.quantity** | Required | TBD | Required | Required |
| **item.description** | Required | TBD | Required | Required |
| **item.value** | Required | TBD | Required | Required |
| **item.currency** | Required | TBD | Required | Required |
| **item.origin\_country** | Required | TBD | Required | Optional |
| **item.hs\_code** | Required | TBD | Optional | Optional |
| **item.weight** | Required | TBD | Required | Required |
| **courier.export\_reason** | N/A | TBD | N/A | Required for B2B |
| **courier.sender\_deferment\_account** | N/A | TBD | N/A | Required for B2B |
| **Note** | Either ship\_to UKIMS or ship\_from.ukims number is required for B2B shipments | TBD | B2B isn't supported by Evri so there is no need for UKIMS and EORI Number |
| **Fields/Courier** | **DHLParcelUK** | **SecuredMail** | **Fedex** | **DPDC2C** |
| **Supported Sales Types:** | B2C / B2B / C2C / C2B | B2B / B2C / C2B | TBD | TBD |
| **courier.sale\_type** | Required | Required | TBD | TBD |
| **ship\_to.ukims\_number** | Required for C2B. Required for B2B if ship\_from.ukims is not entered | Required for B2B shipments unless ship\_from.ukims number isn't entered or Required for C2B shipments | TBD | TBD |
| **ship\_from.ukims\_number** | Required for B2B | Required for B2B shipments | TBD | TBD |
| **ship\_to.eori\_number** | Required for C2B. Required if ship\_to.ukims is entered | Not Required | TBD | TBD |
| **ship\_from.eori\_number** | Required for B2B | Not Required | TBD | TBD |
| **item.sku** | Required | Required | TBD | TBD |
| **item.quantity** | Required | Required | TBD | TBD |
| **item.description** | Required | Required | TBD | TBD |
| **item.value** | Required | Required | TBD | TBD |
| **item.currency** | Required | Required | TBD | TBD |
| **item.origin\_country** | Optional | Required | TBD | TBD |
| **item.hs\_code** | Required | Required | TBD | TBD |
| **item.weight** | Required | Required | TBD | TBD |
| **parcel.dim\_width** | Not Required | Required | TBD | TBD |
| **dim\_height** | Not Required | Required | TBD | TBD |
| **dim\_length** | Not Required | Required | TBD | TBD |
| **dim\_unit** | Not Required | Required | TBD | TBD |
| **courier.export\_reason** | Required for B2B | Required | TBD | TBD |
| **courier.sender\_deferment\_account** | Required for B2B | N/A | TBD | TBD |
| **Note** | TBD | TBD |
| **Fields/Courier** | **Huxloe** | **DGInternational** | **CollectPlus** | **PPI** |
| **Supported Sales Types:** | TBD | TBD | TBD | TBD |
| **courier.sale\_type** | TBD | TBD | TBD | TBD |
| **ship\_to.ukims\_number** | TBD | TBD | TBD | TBD |
| **ship\_from.ukims\_number** | TBD | TBD | TBD | TBD |
| **ship\_to.eori\_number** | TBD | TBD | TBD | TBD |
| **ship\_from.eori\_number** | TBD | TBD | TBD | TBD |
| **item.sku** | TBD | TBD | TBD | TBD |
| **item.quantity** | TBD | TBD | TBD | TBD |
| **item.description** | TBD | TBD | TBD | TBD |
| **item.value** | TBD | TBD | TBD | TBD |
| **item.currency** | TBD | TBD | TBD | TBD |
| **item.origin\_country** | TBD | TBD | TBD | TBD |
| **item.hs\_code** | TBD | TBD | TBD | TBD |
| **item.weight** | TBD | TBD | TBD | TBD |
| **courier.export\_reason** | TBD | TBD | TBD | TBD |
| **courier.sender\_deferment\_account** | TBD | TBD | TBD | TBD |
| **Note** | TBD | TBD | TBD | TBD |
| **Fields/Courier** | **Starlinks** | **UPS** | **ArrowXL** | **ParcelHub** |
| **Supported Sales Types:** | TBD | TBD | TBD | TBD |
| **courier.sale\_type** | TBD | TBD | TBD | TBD |
| **ship\_to.ukims\_number** | TBD | TBD | TBD | TBD |
| **ship\_from.ukims\_number** | TBD | TBD | TBD | TBD |
| **ship\_to.eori\_number** | TBD | TBD | TBD | TBD |
| **ship\_from.eori\_number** | TBD | TBD | TBD | TBD |
| **item.sku** | TBD | TBD | TBD | TBD |
| **item.quantity** | TBD | TBD | TBD | TBD |
| **item.description** | TBD | TBD | TBD | TBD |
| **item.value** | TBD | TBD | TBD | TBD |
| **item.currency** | TBD | TBD | TBD | TBD |
| **item.origin\_country** | TBD | TBD | TBD | TBD |
| **item.hs\_code** | TBD | TBD | TBD | TBD |
| **item.weight** | TBD | TBD | TBD | TBD |
| **courier.export\_reason** | TBD | TBD | TBD | TBD |
| **courier.sender\_deferment\_account** | TBD | TBD | TBD | TBD |
| **Note** | TBD | TBD | TBD | TBD |
| **Fields/Courier** | **DxExpress** |
| **Supported Sales Types:** | TBD |
| **courier.sale\_type** | TBD |
| **ship\_to.ukims\_number** | TBD |
| **ship\_from.ukims\_number** | TBD |
| **ship\_to.eori\_number** | TBD |
| **ship\_from.eori\_number** | TBD |
| **item.sku** | TBD |
| **item.quantity** | TBD |
| **item.description** | TBD |
| **item.value** | TBD |
| **item.currency** | TBD |
| **item.origin\_country** | TBD |
| **item.hs\_code** | TBD |
| **item.weight** | TBD |
| **courier.export\_reason** | TBD |
| **courier.sender\_deferment\_account** | TBD |
| **Note** | TBD |
**Note:** Ensuring the same key is used in both Peoplevox and **Voila** is crucial for establishing a successful connection.
### **Setting Up the Courier Integration in Peoplevox:** To integrate a new courier service via API, follow these steps: 1. **Navigate to Integrations:** In your Peoplevox dashboard, **click** on "Integrations." 2. **Access Carrier Integrations: Select** "Carrier Integrations" from the available options. 3. **Add a New Integration:** **Click** "Add New" to begin the setup process. 4. **Name Your Integration:** **Enter** a descriptive name for the courier integration. 5. **Set the Timeout:** **Enter** "30 000" for the timeout value. 6. **Enter the API Key:** **Enter** the secure key you generated earlier. 7. **Enter the Endpoint:** **Enter** this endpoint URL which is static and remains consistent: ``` https://production.courierapi.co.uk/api/couriers/v1/third-parties/peoplevox/create-label ``` 8. **Specify the Version Schema:** **Set** the version schema to "2.0." 9. **Configure Document Types:** - **Document Type 1: Carrier Label** - Name: **Enter** `documentReference` - Reference: **Enter** `Carrier Label` - Print Template: **Select** the customer's preferred shipping label template. - **Document Type 2: Customs Documentation** - Name: **Enter** `documentReference` - Reference: **Enter** `Customs documentation` - Print Template: **Select** the customer's customs documentation template. - **Document Type 3: Packing Slip Domestic** - Name: **Enter** `Packing Slip Domestic` - Reference: **Enter** `Packing Slip Domestic` - Print Template: Please **select** the appropriate template [](https://shipping-documentation.despatchcloud.app/uploads/images/gallery/2025-02/carier-integration-peoplevox-voila2.webp)Click the image to enlarge
### **Setting up linking to Voila** Provide Voila with the generated random Pairing Key you generated earlier or create a new one if you are starting here: [Randomkeygen.com](https://randomkeygen.com/) **In the [Playground](https://playground.heyvoila.io/) or in [Postman](https://shipping-documentation.despatchcloud.app/link/176#bkmrk-%F0%9F%9A%80-quick-start-guide%3A), send a POST Request to this endpoint:** [https://production.courierapi.co.uk/api/couriers/v1/third-parties/peoplevox/link-auth](https://production.courierapi.co.uk/) ``` headers: {'api-user': 'YOUR API USER', 'api-token': 'YOUR API USER TOKEN'}, ``` **This is the JSON to POST** - change the authorisation header to the key we generated earlier, and change the address to the address you're shipping from: ```json { "peoplevox_authorization_header" : "RandomGeneratedKey", "ship_from": { "name": "Fake Company", "phone": "01377 334140", "email": "customer.support@fake.com", "company_name": "Fake Company", "address_1": "Unit 99, Warfield Road", "address_2": "", "address_3": "", "city": "Fakefurt", "postcode": "YO250FK", "county": "East Yorkshire", "country_iso": "GB", "company_id": "03764419", "tax_id": "284256444", "eori_id": "GB284256444000", "ioss_number": null } } ```Populate the information above with live customer details
### **Set up a Smart Shipping group in [****](https://playground.heyvoila.io/)** Find detailed instructions for setting up **[Smart Shipping in Voila by following this link](https://shipping-documentation.despatchcloud.app/books/smart-shipping/page/smart-shipping)** #### **Setting up a Service Type in Peoplevox that Corresponds to a [Smart Shipping Group in ](https://playground.heyvoila.io/) ** 1. **Navigate to** 'Outbound Goods' and then **click** 'Carriers.' 2. **Select** 'Add New' for a new carrier or 'Edit' an existing carrier. 3. In the 'Name' field, **enter** the desired service type (e.g., 'DPD Saturday 10 am', 'Ebay', 'Etsy' or 'First Class'). 4. In the 'Code' field, **enter** the **exact same** name as the Smart Shipping Group (e.g., 'DPD Saturday 10 am'). This ensures proper matching. 5. **Click** 'Add' or 'Save.'**Important, verify that the 'Code' matches the Smart Shipping Group name precisely.**
[](https://shipping-documentation.despatchcloud.app/uploads/images/gallery/2025-02/setting-up-a-service-type-voila-peoplevox-a.webp)Click the image to enlarge