.jpg)
The SYMSON onboarding process consists of several steps.
Before you start, you should define your objectives for implementing SYMSON. Among many others, SYMSON can be used for goals such as:
It is important to have the underlying goals clear to all stakeholders of the pricing process before we start with the onboarding.
Figure 1: the onboarding process of SYMSON
The first step (i1) is to select the desired use case for SYMSON. This could be one or more of the following solutions:
The second step (i2) is to consider which data sources are necessary to realise the desired goal, the resulting strategies and use cases. This results in a data format in SYMSON, which can be fed by the downstream systems such as an ERP. Examples of data points are order lines, EAN codes, cost prices, mark-ups and supplier prices. SYMSON has specific requirements for the data format that must be agreed in advance.
The next step (i3) is to see how the data stream can flow automatically in SYMSON. This can be done through our API documentation where the link can be made by yourself, or through a SYMSON partner who will help you with the connection - all with the necessary security and control. In addition, an examination is carried out on whether external data flows (such as market prices) are necessary to include.
Step 4 (i4) in the process is to build strategies through a combination of basic components, business rules and notifications. This strategy is built together with you, based on the desired use case and goals. In the next step (i5), product (groups) are assigned to the correct strategy. This can be based on imported attributes or on manual selection.
Figure 1: the onboarding process of SYMSON
In the next step (i5), product (groups) are assigned to the correct strategy. This can be based on imported attributes or on manual selection.
The Dynamic Engine (i6) and Compute Engine (i7) are very related to each other. The Dynamic Engine ensures that if something changes in the input data, the calculated prices in the Compute Engine automatically change according to the predetermined strategies.
In the next step, the results (i8) can be verified, the price change between new and old can be analysed and the history of price changes can be reviewed. Once we go through the full cycle, SYMSON can learn from the data that has been collected and suggest improvements for new configurations, strategies and outcomes.
Figure 2: the onboarding process of SYMSON
The above process is a dynamic process, completed in a number of cycles during Onboarding, before SYMSON can be fully integrated. Both our technical support team and our partners can support in this process, in order to speed up adoption in your organisational process.
