2.2.1. Login via Coolblue Cafetariaplan API
4.3.1 Transaction communication
Example: Fully automated integration
Coolblue Business Cafetariaplans
Customizable cafetariaplan solutions for our business partners to create tailored customer journeys.
Over time Coolblue will expand the cafetariaplan 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 cafetariaplan customer journey with Coolblue. Not all steps and features are necessary or feasible for every integration. We advise to integrate in incremental steps, starting with essential steps and adding more features as needed.
Feedback is always welcome: please share your questions, comments and concerns with your Coolblue Specialized Sales consultant.
This document uses the following terminology:
In order to configure a cafetariaplan 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 cafetariaplan provider:
Note: It is also possible to set up a single closed community for all employers of the same cafetariaplan provider. This setup provides the same assortment and single landing page for every employer.
In order for the employee to access the Coolblue website, they need to be logged in.
Note: Regardless of the onboarding approach, employees are not able to see draft orders or any previously created orders in their Coolblue account. It is the responsibility of the cafetariaplan provider to display pending or placed orders to the employees if this feature is needed.
This integration requires the cafetariaplan provider to register the employee at Coolblue before they are redirected to the Coolblue website.
The login process is done in two steps:
After receiving the token and parameters, the client can also add a parameter for the return URL. This parameter will be used for the Call to Action button on Coolblue’s Thank You page. The parameter is called returnurl. Keep in mind that this parameter should be a valid URL.
In order to see the assortment available at Coolblue, employees have to visit the Coolblue website. Coolblue does not provide separate websites for cafetariaplan integrations. Instead, the main website is customized for employees linked to a cafetariaplan.
The cafetariaplan provider is responsible for redirecting employees to the Coolblue website using the URL provided by Coolblue.
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.
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 cafetariaplan 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 cafetariaplan. It contains links to different product categories available in the assortment. This page is only visible to customers that are part of the cafetariaplan, 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 select on the cafetariaplan provider platform. Coolblue creates a single closed community per employer, and its assortment includes all product types eligible for the cafetariaplan. It is the responsibility of the cafetariaplan 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.
The ordering process via cafetariaplans is performed in multiple steps.
First, the employee selects desired products and provides customer details required to create a draft order at Coolblue. Draft orders include a snapshot of the shopping cart (products and prices), contact details, delivery details, company ID and any other relevant information necessary for placing actual orders later.
A draft order has an expiry period, which is managed by Coolblue, and by default is 24 hours. Draft order price is preserved in this time frame.
The cafetariaplan provider can retrieve the draft order details from the Cafetariaplan API and use this information to approve or reject the order. Once the order is approved, the cafetariaplan provider needs to call the Cafetariaplan API to convert the draft order.
As soon as the draft order is validated and accepted on the cafetariaplan provider system, it can be converted into an actual order at Coolblue by calling the Cafetariaplan API. This action has to be taken within the expiry period of the draft order.
After an order is created at Coolblue, the cafetariaplan provider can request the status of the order. As soon as this status changes to indicate that the order has been shipped, the employee should receive the order within a single day. This information can be used to determine at what date the cafetariaplan benefit should start for the employee.
There are several types of transactional communication sent to Coolblue customers:
For cafetariaplan 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.
An example of a feature-reach fully automated customer journey with a custom Coolblue implementation tailed for the cafetariaplan provider: