Adding more functionality to the checkout

Extensions are standalone tools that can be combined and integrated into Skrym's .
They leverage the data available in the checkout to provide additional functionality:


 Check which of your transporters are available to deliver the order before presenting the options to the customer.


 Determine what package(s) to pack and send the order in even before it has been confirmed.


 Get dynamic pricing and/or exclusions based on order data.


 Provide your customers with the carbon footprint of their order, helping them make more informed choices about their delivery options.



Extensions

Through our transporter integrations, we can verify which transport methods can deliver to the desired destination address.
Depending on the transporter, this may include an indication of the delivery time as well.
Supported Transporters
| Transporter                                                                           | Service availability | Time interval   | Supported countries |
| ------------------------------------------------------------------------------------  | :------------------: | :-------------: | :-----------------: |
| <OrganizationChip name={'instabox'} size={21} />                                      |          ✓           |        ✓        |    SE, DK, FI       |
| <OrganizationChip name={'postnord'} size={21} />                                      |          ✓           |        ✓        |        SE           |
| <OrganizationChip name={'budbee'} size={21} />                                        |          ✓           |        ✓        |    SE, DK, FI       |
| <OrganizationChip name={'earlybird'} text="Early Bird" size={21} />                   |          ✓           |        ✓        |        SE           |
| <OrganizationChip name={'airmee'} size={21} />                                        |          ✓           |        ✓        |        SE           |
| <OrganizationChip name={'bring'} size={21} />                                         |          ✓           |        ✓        |      SE, NO         |
| <OrganizationChip name={'dbschenker'} text="DB Schenker" size={21}/>                  |          ✓           |        ✓        |        SE           |
| <OrganizationChip name={'posti'} size={21}/>                                          |          ✓           |                 |      SE, FI         |
| <OrganizationChip name={'dhl'} text="DHL" size={21}/>                                 |          ✓           |        ✓        |        SE           |
| <OrganizationChip name={'retailerTransporter'} text="RetailerTransporter" size={21}/> |     configured       |   configured    |     World wide      |
Are you using your own stores as pick up points? Please see  to see how we handle it!
Using Fallback Delivery Times
Skrym applies fallback values for delivery time if:

You configure a preference to use fallback values instead of the transporter's estimation. See .
The transporter does not return a delivery time but confirms the address is valid.

In the case of using fallback delivery times, Skrym returns:

No delivery times: if both the fallback times are missing or invalid.
Single delivery time: If only one fallback time is valid.
Both delivery time: If both fallback times are valid.


If Skrym is unable to validate the delivery address, the transport method will not show at all unless specifically configured to disregard the availability check.
This is in order to prevent showing methods that are actually unavailable.

Data Requirements
In order to be able to use the availability function successfully, the following data is required:
|        Data       |  Explanation                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| :-------------------:  | ----------------------------------------------------------------------------------------------------------------------------------------------|
|    Credentials       | Almost all transporters require some form of authentication for us to call their availability API. This can be set up on the transporter page in    |
|    Enabled           | For Skrym to run any checks at all the methods need to be enabled in                                                                                |

Availability Checks

Adding Package Recommendation to the Checkout

Optimization determines the exact size of the parcel(s) to be sent.
This naturally results in more accurate delivery option estimations, especially if coupled with  for cost calculation.
To enable order optimization in the checkout, you simply need to:

Onboard your packages.
Contact Skrym to enable the optimization in the checkout

It is also always suggested to onboard product data to easily enable any integration.
To read more about how our order optimization works, head over to .

  
    Data requirements
    Exception handling
  
  
        
        Skrym follows specific steps to determine which products should be sent for optimization. The process involves:
    1. **Checking Product Type:** Skrym examines the products type field to identify physical products eligible for optimization. Non-physical products are excluded from the optimization flow.
    2. **Extracting Product Data:** Skrym retrieves product dimensions and weight for optimization in two ways:

        2.1 **From the Request:** If the request contains product dimensions for all physical products, Skrym uses that data for a checkout optimization (although this still requires onboarded package data).
    
        2.2 **From the Database:** You can onboard products and utilize their dimensions for optimization. To use this approach, you must provide an external ID (reference) in the order and set the `onboard-products` checkout preference to true under `klarna-shipping-assistant` / `API`.

    </TabPanel>
    <TabPanel>
    Skrym handles two main cases of incomplete product data during optimization:

    1. **Empty Product Reference:**
    - If the `onboard-products` preference is false, Skrym uses the dimension data provided by the caller. 
    - If the data is valid, optimization proceeds as usual. If the data is invalid, the optimization fails, and the flow continues without any optimization results (this can negatively affect other extensions such as costs/availability/emissions). 
    - If the `onboard-products` preference is true, but the product reference is empty, 
        - Then products cannot be fetched from the database due to the lack of an identifier.

    2. **Empty Product Type:**
    - If the product type is empty, Skrym will disregard the product in the optimzation.
    - If the dimensions are invalid and the product reference is valid, the product is not sent for optimization.

    </TabPanel>
</TabPanels>



Optimization

Adding shipping cost calculator to the checkout

The Cost extension allows you to calculate the cost of delivery based on your digital transport agreements and order data.
If enabled, the response from  can contain the delivery costs for each transport method.
These costs can be further tweaked by your specific  and .
Data Requirements
To calculate the cost of delivery, Skrym needs the following data:


Your transport agreements: You can learn how to upload your agreements .
Skrym will generate a digital version of it, using it to calculate the cost of delivery.


Optimization (optional): With optimization in the checkout enabled, Skrym can find the exact parcel to and therefore calculate the costs more accurately.



Cost

Adding emissions calculator to the checkout

The Emissions extension allows you to calculate the estimated emissions of delivering the order.
If enabled, the response from  will contain the estimated shipping and packaging emissions for each transport method.
Learn more about our .
Data Requirements
To estimate the order emissions, Skrym needs the following data:


Available packages: You can upload your (or your warehouse's) packages on .


Package fill materials: You can upload your (or your warehouse's) fill materials on .


Optimization: Optimization is required to calculate how much packaging and filling material is used, and how much space will the parcel take up in the transportation vehicle.

