Configure and optimize your checkout process

The Skrym checkout functionality combines an intuitive no-code user interface for configuring logic with
powerful extensions that make your checkout more dynamic.
There are two ways of using the functionality:

Using the  Skrym 
Use a  with a checkout provider

To get started, we recommend becoming familiar with a , which is the core
concept of the checkout functionality.
After that, dive deeper by exploring the configurable 
and  that can be used to further boost your checkout.
If you need any help setting up or have any questions, don't hesitate to reach out to .

Checkout

Configuring the ranking and presentation of shipping options

A Strategy is a set of scenarios and rules that enable you to tailor how shipping options
are presented to customers during the checkout process.
<MermaidChart
title="Applying a Strategy"
subtitle="Applying a strategy to a shopping cart results in a list of possible delivery choices."
chart={flowchart LR     C([Cart]) --> S([Strategy])     S --> Options     subgraph Options         direction TB         opt1([DHL Service Point])         opt1 ~~~ opt2         opt2([PostNord MyPack Collect])         opt2 ~~~ opt3         opt3([Budbee Box])     end}
/>
Depending on how you configure the strategy, it will determine the order, pricing, delivery time and
presentation (e.g. badges, description) of the shipping options.
Anatomy of a Strategy
A Strategy works like a decision tree, where each branch represents a set of conditions that must be met for the branch to be applied.
When a cart is applied to a strategy, the tree is evaluated and will result in one tactic being applied.
<MermaidChart
chart={flowchart LR     St([Strategy]) ---|Conditions| TBA([Tactic Branch])     St([Strategy]) ---|Conditions| TBB([Tactic Branch])     TBA ---|Conditions| TA1([Tactic])     TBA ---|Conditions| TA2([Tactic])     TBB ---|Conditions| TB1([Tactic])}
/>
This design is flexible and easy to overview - even for the most complex scenarios.
| Term | Description |
| --- | --- |
| Strategy| A complete "logic tree" consisting of multiple Tactic Branches and Tactics. |
| Tactic Branch | A grouping of tactics to be applied under certain conditions. Example: Collection of rules you want to apply for orders to be shipped to Germany. |
| Tactic | Contains the logic determining the output of the strategy. Applying a strategy always results in one Tactic. |
| Condition | Set of logical evaluations that will be either true or false, determining which path of the Strategy will be applied.Example: Destination country is Germany. |
Now that you understand the basics, you are ready to create your first Strategy.

Strategy

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

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

Test the performance of alternative strategies

A/B testing allows you to compare different  in real-time by directing a portion of user traffic to each variant.
For example, you could assess how your conversion rate differs after adding a new Tactic/Condition before using the new Strategy in production.
How It Works
A/B testing is straightforward:

Create multiple strategies that you want to test against each other.
Assign a percentage of traffic to each strategy.
Schedule the test to start automatically distributing traffic based on your settings.

Feel free to go through the step-by-step guides below to learn how to work with A/B Testing on Scope:

  
    Create ➕
    Schedule 📆
    Extend ⏳
    Abort ❌
  
  
        
            
        Follow these steps to create an A/B Test:
        1. Navigate to the *Strategies* page.
        2. Click on *Add New* under the A/B-tests section.
        3. Configure your test settings.
        4. Save the test configuration.

        **Note:** The test remains in a *DRAFT* state and will not run until scheduled.

        <Callout type="info" title="Important">
            The traffic allocation is randomized based on user sessions, not each individual checkout page load. If a user reloads the checkout within the same session, they will see the same options. 
        </Callout>

    </TabPanel>
    <TabPanel>
        <IframeComponent src="https://app.supademo.com/embed/clw6k5vyu00d312fp8v76y1kk" title="Schedule an A/B Test" />

        To schedule an A/B Test:
        1. Go to the *Strategies* page.
        2. Select the test you want to schedule.
        3. Click on *Schedule*.

        The system will automatically start the test at the specified start date.

    </TabPanel>
    <TabPanel>
        <IframeComponent src="https://app.supademo.com/embed/clw7fpz1n03wv1g3vn085hm0t" title="Extend an A/B Test" /> 

        To extend an A/B Test:
        1. Visit the *Strategies* page.
        2. Select the test you wish to extend.
        3. Update the *End Date*.
        4. Click *Save*.

        The test will continue until the new end date.
        
    </TabPanel>
    <TabPanel>
        <IframeComponent src="https://app.supademo.com/embed/clw7fydia03ze1g3v3d17e663" title="Abort an A/B Test" />

        To abort an active A/B Test:
        1. Navigate to the *Strategies* page.
        2. Click the *Abort* button on the desired test.

        This will immediately stop the test, reverting traffic distribution to the default production strategy.

    </TabPanel>
</TabPanels>


A/B Testing Statistics
You can view statistics from your A/B tests by navigating to the individual A/B test page from the .
For each A/B test, you can see the following statistics:

Total number of presentations
Total number of conversions and conversion rate
Number of confirmed orders for each transport method
Average displayed shipping price for confirmed orders
Average shipping cost you incurred for confirmed orders
Average profit and loss you incurred on shipping


If you have any questions or concerns, please feel free to reach out to !

A/B Testing

Here you can find the reference for all of Skrym's API endpoints within the Checkout functionality.
It is divided into three parts:

Checkout API: Get the shipping options, reserve a delivery, and confirm the order payment.
Statistics API: Get data points collected throughout the use of your checkout.
Transport Method Config API: Configure transport method-specific behavior.

If you have any questions or need help, please contact us at .