Table of Contents

Table of Contents

1. Glossary

2. Onboarding at Coolblue

2.1. Employer Onboarding

2.2. Employee Onboarding

2.2.1. Login via Coolblue Closed Community Management API

3. Offboarding at Coolblue

3.1. Employee Offboarding

3.1.1. Offboarding via Coolblue Closed Community Management API

4. Retrieving remaining business credit

4.1 Retrieving remaining business credit

5. Setting up a Single Sign On connection

5.1 Credentials to establish Single Sign On connection

5.2 Customer journey

6. Coolblue Website

6.1. Closed Community Portal

7. Orders

7.1. Create an order

7.2. Select the correct payment method

7.3. Post-order processing

7.3.1 Transaction communication


Coolblue SSO integration 

Customizable Closed Community solutions for our business partners to create tailored customer journeys.

Over time Coolblue will expand Closed Community capabilities and customizations to introduce new and expand existing features. We make all reasonable efforts to maintain backwards compatibility. In an unlikely event when a breaking change is required, we ensure to inform our partners at least two weeks in advance.

The capabilities described in this document are building blocks that allow our partners to integrate various parts of the Closed Community customer journey with Coolblue.

Feedback is always welcome: please share your questions, comments and concerns with your Coolblue Specialized Sales consultant.

1. Glossary

This document uses the following terminology:

2. Onboarding at Coolblue

2.1. Employer Onboarding

In order to configure a Closed Community for a new employer, their company has to be manually registered in Coolblue systems. The registration process involves several parts:

After this initial registration, Coolblue sends the following information to the employer  provider:

  1. Landing page URL. It has to be used when redirecting employees to the Coolblue website. Also known as redirect URL
  2. Closed Community ID. This ID serves as a parameter to identify the correct closed community and is used for user onboarding in the company’s portal

2.2. Employee Onboarding

In order for the employee to access the Coolblue website, they need to be logged in.

2.2.1. Login via Coolblue Closed Community Management API

This integration requires the business customer to register the employee via their identity provider at Coolblue before they are redirected to the Coolblue website.

The login process is done in two steps:

  1. The employer calls the Coolblue API to create a new account for the employee. The required data includes first name, last name, email address and business credit budget. In response, the API returns a successful or unsuccessful response for the newly registered employee. Refer to the contracts section at the end of this document.
  2. The user selects Coolblue from the company’s identity provider. After that, the user gets redirected to Coolblue where they log in with their company specific credentials and afterwards get redirected back to their company identity provider. After validating their identity, the user gets redirected back to the landing page of the Coolblue & company Closed Community.


3. Offboarding at Coolblue

3.1. Employee Offboarding

Via the DELETE endpoint, an employer can call Coolblue Closed Community Management API to remove an employee from the company immediately. Besides removal, the remaining business credit of an employee gets revoked, which prevents the employee from spending this budget.

Note: calling the delete endpoint unlinks the employee from the Closed Community only. The Coolblue account for the given user remains. This makes sure that, in the case of returns, the employee can still access their account to contact Coolblue’s customer service without the interference of the employer.

3.1.1. Offboarding via Coolblue Closed Community Management API

The offboarding process is done in a single step:

  1. The employer provider calls Coolblue Closed Community Management API  to remove an account of the employee from the Closed Community. The required data includes Closed Community ID and email address. In response, the API returns a successful or unsuccessful operation for a removed employee. Refer to the contracts section at the end of this document.

    Besides removing the user from the Closed Community, any remaining business credit gets revoked. This prevents the employee from spending this budget on behalf of the employer.


4. Retrieving remaining business credit

4.1 Retrieving remaining business credit

Via the GET endpoint, an employer can call Coolblue API to retrieve the remaining budget of an employee.

Retrieving the remaining business credit requires only one step:

  1. The employer provider calls the Coolblue API to  request the remaining credit of the employee from the Closed Community. The required data includes Closed Community ID and email address. In response, the API returns a successful or unsuccessful operation. Refer to the contracts section at the end of this document.

5. Setting up a Single Sign On connection

The Single Sign On connection makes sure the user gets redirected to the identity provider of the employer. Currently, we only provide a Single Sign On connection for OpenID. Other software is not supported.

5.1 Credentials to establish Single Sign On connection

To set up a Single Sign On connection, the employer needs to provide three values, for both acceptance and production:

Please note: Coolblue can only redirect users to the company’s identity provider when the employee is onboarded via the Closed Community Manager API. The SSO connection provided by Coolblue disables all other log-in methods.

5.2 Customer journey

  1. Employee goes to Coolblue.nl
  2. Employee logs-in
  3. Coolblue recognized user as an Open ID customer
  4. Redirects user to identity provider of employee, based on the well-known URL
  5. Employee verifies its identity via the identity employer
  6. Employee gets redirected to the Closed Community and is logged-in with the created account and added credit (previously done in the Closed Community API).

6. Coolblue Website

In order to see the assortment available at Coolblue, employees have to visit the Coolblue website. Coolblue does not provide separate websites for Closed Community integrations. Instead, the main website is customized for employees linked to a Closed  Community.

The business customer is responsible for redirecting employees to the Coolblue website using the URL provided by Coolblue via their identity provider.

Please note that the Coolblue website differs per country:

Note: It is not possible for employees to order products from the assortment of the website in another country.

6.1. Closed Community Portal

A closed community portal is a closed environment on the Coolblue website that has a custom landing page, limited assortment and extra features available only for Closed Community employees.

The landing page of the closed community has to be configured as part of onboarding the employer based on the limited assortment of the Closed Community. It contains links to different product categories available in the assortment. This page is only visible to customers that are part of the Closed Community, and is thus not visible to regular customers of Coolblue.

Note: It is not possible to show employees only specific product types (e.g. only phones or laptops) based on what they may be ordering on behalf of their employer. Coolblue creates a single closed community per employer, and its assortment includes all product types eligible for the Closed Community. It is the responsibility of the business customer provider to validate that the type of the selected product is correct. To facilitate the validation, Coolblue provides an API for retrieving product information that includes the product types.

7. Orders

The ordering process via a Closed Community is performed as any regular order and has a different method of paying for their products

7.1. Create an order

After the employee is successfully onboarded in the Closed Community, the user can enter the company specific storefront. Ordering a product does not differ from the regular consumer flow within Coolblue. Placing products in the shopping cart allows users to order their products.

7.2. Select the correct payment method

In the Coolblue checkout, the user sees multiple payment options. Amongst them is the ‘Business credit’ option. The employee should select this option to use their credit given by the employer.

Note: when a user tries to order products which are excluded by the employer, the business credit will not be deducted.

7.3. Post-order processing

7.3.1 Transaction communication

There are several types of transactional communication sent to Coolblue customers:

For Closed Community orders the communication is split: the employee receives the communication about the order and delivery, whereas the employer receives the invoicing information. Some types of emails can be disabled completely depending on the needs of the integration.