Skip to content

    Omnichannel features

    Here you may find omnichannel features described as part of Consumer journeys for Unified Services.

    Overview

    As there is an increasing demand for products and services both through digital and physical sales channels, there is a need for the implementation of consumer journeys. These Omnichannel solutions will help improve the overall consumer experience.

    We have simplified the implementation of Omnichannel journeys via the use of our Unified API. A few examples of the new implementation are presented on this page.

    Click&Collect

    Click&Collect is becoming a very common consumer journey used in a wide range of verticals. It provides a possibility for your customers to have their orders delivered, and in some cases, an opportunity for them to inspect the goods before bringing them home.

    It means that by using the Unified API, you will create a simple way to handle payments through a Click&Collect scenario. In this section, we will present one such scenario and show one full Click&Collect consumer journey.

    At the moment when your customer checks out from your webshop, a reservation of funds is created. That allows payment via the eCommerce platform. During this process, the Unified API creates a PaymentID reference. This points to the authorisation transaction and enables you to refer to it when requesting the capture of funds at delivery.

    The customer can then go to a physical pick-up place, either a designated pick-up location or your store, and pick up the ordered item(s). In that process, you can use their ECR integration with the Unified API to request the capture by reference to the PaymentID. After that, the transaction state will change to Captured.

    Click&Collect - Basic flow, eCom payment path

    Click

    1. The customer places an order at the webshop.
    2. The webshop registers the order with the Unified API.
    3. The webshop requests authorisation (reservation of funds).
    4. Webshop store order details, auth status, PaymentID, and order reference.
    5. The webshop shares the order reference with the customer.
    US Omnichannel features Click&Collect

    Collect

    1. The customer goes to the local store X for pickup.
    2. The local store uses the ECR system and credentials.
    3. The local store X's ECR lookup order details and authorisation status from the webshop order management system.
    4. The Local store X requests capture "on behalf of" webshop from ECR and the payment is deposited to the webshop.
    5. Product(s) delivery.
    6. The local store X updates its order status.

    Return Management

    Sometimes home deliveries trigger the need for returns, and some customers turn to physical locations for returning goods. Using the Unified API creates a simple way for you to handle refunds related to a goods return in-store scenario.

    When a customer buys and receives goods with the option of home delivery or pick-up at a specific location, you will generate a capture transaction at the time of delivery.

    During the Click&Collect payment process, the Unified API would have already shared with you a PaymentID alongside your own reference. That enables you to refer to the authorisation when requesting the refund. The customer can then go to a designated physical place and get a refund for the item(s) returned.

    In that process, you can use their ECR integration with the Unified API to request the refund by reference to the PaymentID. Then, the transaction state changes to Refunded.

    Return Management - Basic flow, eCom payment path

    Buy

    1. The customer places an order at the webshop.
    2. The webshop registers the order with the Unified API.
    3. The webshop requests authorisation (reservation of funds).
    4. Webshop store order details, auth status, PaymentID, and order reference.
    5. The webshop shares the order reference with the customer.
    6. The goods are shipped directly or picked up by the customer, as explained in the Click&Collect flow.
    US Omnichannel features return management

    Refund

    1. The customer goes to the local store X for return (Refund).
    2. The local store uses the ECR system and credentials.
    3. The local store X's ECR lookup order details and authorisation status from your order management system.
    4. The Local store X requests capture "on behalf of" webshop from ECR and the original payment is refunded from to the webshop.
    5. The customer gets a receipt that confirms the refund.
    6. The local store X updates its order status.

    Next steps

    We have so far described two Omnichannel features: Click&Collect and Return Management. These are not all, so more features will be presented on this page soon.

    Was this helpful?

    What was your feeling about it?