On this page and its sub-pages, we describe the ways in which you can set your own preferences for the checkout.
On the , you can configure the following checkout-level preferences:
| Preference   | Values | Default | Availability | Description |
| ------------ | --------------- | ------- | :-----------: | ----------- |
| Product data source | True, False | True |   | If set to true, onboarded product data will be used instead of the information in the request. |
| Override times with fallback times | True, False | False |   | If set to true, your pre-set fallback times will be used instead of the transporter's estimated delivery time. |
| Round price | Off, Nearest Integer, Nearest Five | Off |   | Rounds the returned calculated price to the nearest set value. |
| Return non-displayable transport methods | True, False | False |  | Skrym Checkout API filters transport methods on multiple criteria., e.g.: a failed availability call to the transporter, or exclusions within the Checkout Strategy. If set to true, Skrym returns even the excluded methods, marking them with display: false. |
| Use working days | True, False | False |  | If set to true, Skrym will only consider working days when counting the estimated delivery time. |
| Hide delivery times | True, False | False |    | If set to true, the delivery time will not be displayed in the checkout. |

Apart from these, you can also set additional preferences for each  or even configure your own .

Preferences

Setting your preferences for each transport method

This page introduces how transport methods can be configured to align with your expectations.
Setting Up Transport Methods
You can find all the transporters we support on the  in Scope.
By selecting one, you can view and edit all of its transport methods.
Customer Number and Credentials
To get delivery availabilities from the transporter, you need to provide us with your credentials and/or a customer number. This is done on a transporter-level and is configurable on each transporter's page.
Different transporters have different kinds of credentials, so please reach out to us at  if you need help setting this up.
Transport Method Checkout Code
Each transport method can be assigned a unique checkout code. This code is automatically included in the list of transport methods provided by Skrym when we respond with delivery options in the checkout.
The intention of these codes is to simplify the integration between Skrym and the rest of your operations.
Where the Codes Are Used
These codes are propagated using the below mentioned fields for each of our checkout integrations:
| Integration                                    | Field  | Description                                                        | Documentation                                                                                                                                   |
| ---------------------------------------------- | ------ | ------------------------------------------------------------       | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| <OrganizationChip name={'klarna'} size={26} /> | Name | The code is set to the Name field in each shipping option.       |  |
| <OrganizationChip name={'skrym'} size={26} />  | Code | The code is set to the MethodCode field in each delivery option. |  |
Note: In the absence of specified checkout codes, Skrym defaults to using our own predefined codes for each transport method.
Managing This Data
There are two ways of managing this data with Skrym, either through  or by utilizing our API endpoints.
Using Scope
<IframeComponent src={"https://app.supademo.com/embed/clushxztf0obw4r8t5au6rjm4"} title="Transport Method Checkout configuration"/>
Using Our APIs
Please checkout the  for managing these preferences using the API.
We support the full range of creating, updating, reading and deleting these preferences.

Transport Methods

How to set-up and utilize custom parameters

Custom parameters offer you the flexibility to configure unique inputs tailored to your needs when utilizing Skrym services. We currently support the use of custom parameters within the delivery checkout offering, with plans to extend support to additional services in the future.
This page will guide you in creating these custom parameters in Skrym.

Custom parameters require you to access our dashboard: 

Getting started
Creating and managing custom parameters is easy, just follow these steps:

Datatypes
Custom parameters can be defined as different datatypes, You can also specify if the parameter is a single value or a list of values (array[]).
| Datatype | Description                                                                     |
| -------- | ------------------------------------------------------------------------------- |
| boolean  | A simple yes/no value, sometimes referred to as a tag/flag.                      |
| number   | Any number                                                                      |
| string   | Text                                                                            |
| object   | A object contains multiple other datatypes and works as a parent for the values |
Specially structured strings, resembling non-json strings like arrays are also supported. Learn more about how they are supported under parsing schemas.
Custom Datatype Operations
The following operations are supported for the different custom parameter datatypes:
| Operation           | Custom parameter datatype           | Description                                                                                         |
| ------------------- | ----------------------------------- | --------------------------------------------------------------------------------------------------- |
| less              | number                            | Returns true if the value of a custom parameter is less than a value, false otherwise           |
| greater           | number                            | Returns true if the value of a custom parameter is greater than a value, false otherwise        |
| leq               | number                            | Returns true if the value of a custom parameter is less or equal to a value, false otherwise    |
| geq               | number                            | Returns true if the value of a custom parameter is greater or equal to a value, false otherwise |
| equals            | number, string, boolean       | Returns true if the value of a custom parameter equals a value, false otherwise                 |
| notEquals         | number, string, boolean       | Returns true if the value of a custom parameter is not equal to a value, false otherwise        |
| contains          | []number, []string, []boolean | Returns true if a value is contained in the custom parameter, false otherwise                   |
| notContains       | []number, []string, []boolean | Returns true if a value is not contained in the custom parameter, false otherwise               |
| containsSubstring | string                            | Returns true if a value is a substring of the custom parameter, false otherwise                 |
How to use custom parameters in the delivery checkout
Setting up custom parameters in the checkout strategy
Each custom parameter can be used in the delivery checkout to customize the ranking of transport method. These custom parameters can be used when setting up conditions for the different paths in the checkout strategy. Here's how they can be set

Using them in the checkout flow
Custom parameters are expected to be sent in when making a request for a list of possible delivery options.
They are expected to be sent in JSON format, i.e. A custom parameter called fragile whose value is true can be sent in as "fragile":true. Specially structured strings, that don't strictly adhere to json format are also supported by the use of parsing schemas. For more information, please refer to the section below on parsing schemas.
Here's where the custom parameters can be passed in for each of our checkout integrations:
| Integration                                    | Field  | Description                                                        | Documentation                                                                                                                                   |
| ---------------------------------------------- | ------ | ------------------------------------------------------------       | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| <OrganizationChip name={'klarna'} size={26} /> | order.tags | Can be sent in as part of the tags field within the order field in the request      | . |
| <OrganizationChip name={'skrym'} size={26} />  | customParams | Can be sent in as part of the customParams field in the request | . |
Parsing schemas
Certain systems may be limited in the formats they can send their data in. In order to enable Skrym to interpret these formats accurately, we support the creation of parsing schemas. These schemas facilitate the conversion of structured strings into a JSON format that Skrym can seamlessly process.
Here's how you can work with parsing schemas using 


Custom Parameters

Using transport method codes in the checkout flow

Overview
Skrym allows a user of our system to set specific codes on a transport method level that is to be propagated as part of the list of transport methods that Skrym Responds with during to a checkout integration.
Where in the system these codes can be found
These codes can be set on a method level in the organization_transport_method_checkout_config table (checkout_code field) in the checkout service.
Where the codes are used
Internally, these codes are used to set the value of the MethodCode field in each transport methods we respond with.
These codes are propagated using the below mentioned fields for each of our checkout integrations:
| Integration                                    | Field  | Description                                                        | Documentation                                                                                                                                   |
| ---------------------------------------------- | ------ | ------------------------------------------------------------       | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| <OrganizationChip name={'klarna'} size={26} /> | Name | The code is set to the Name field in each shipping option.       | . |
| <OrganizationChip name={'skrym'} size={26} />  | Code | The code is set to the MethodCode field in each delivery option. | . |
Note: In the klarna flow, we currently fallback to the code field in the transport_method table of the transportation service if no organization transport method checkout code is set for a given transport method
Usage
These are the following endpoints that facilitate the setting, updating, fetching and deleting of these transport method codes.
📝 Add a transport method code
A checkout code can be added for one or more transport methods by providing the code along with the Skrym transport method ID and the corresponding checkout it is to be used in.

📖 Fetch a set transport method code
There are two ways of fetching codes, one to get a single code and the other to fetch all codes associated with the authenticated organization.
🎯 Single Code
A checkout code can be fetched for one transport method by providing the Skrym transport method ID and the corresponding checkout the code should be fetched for.

📋 Multiple Codes
Checkout codes for all transport methods for a given checkout can be fetched by providing corresponding checkout.

🗑️ Delete a set transport method code
A set checkout code can be deleted by providing the Skrym transport method ID and the corresponding checkout the code should be deleted for.


Preference	Values	Default	Description
Product data source	`True`, `False`	`True`	If set to true, onboarded product data will be used instead of the information in the request.
Override times with fallback times	`True`, `False`	`False`	If set to true, your pre-set fallback times will be used instead of the transporter's estimated delivery time.
Round price	`Off`, `Nearest Integer`, `Nearest Five`	`Off`	Rounds the returned calculated price to the nearest set value.
Return non-displayable transport methods	`True`, `False`	`False`	Skrym Checkout API filters transport methods on multiple criteria., e.g.: a failed availability call to the transporter, or exclusions within the Checkout Strategy. If set to true, Skrym returns even the excluded methods, marking them with `display: false`.
Use working days	`True`, `False`	`False`	If set to true, Skrym will only consider working days when counting the estimated delivery time.
Hide delivery times	`True`, `False`	`False`	If set to true, the delivery time will not be displayed in the checkout.