Elfskot becomes Elfsquad. Curious?

Frequently asked questions

Is it possible to connect the Elfskot Product Configurator with other systems?

A configurator is an essential component in the business processes and IT infrastructure. In other words; it must be easy to connect. We took this into account in every step of the development. Connecting and integrating within the existing IT infrastructure has never been easier.

We have created a number of standard plugins, for example with Exact Online, where you only need to log in and the connection runs automatically. In addition, we have developed a REST API and SDK that can be easily linked to any package. Free and freely accessible to all users.

Curious about all our partners and other integrations?

Documentation and downloads of the SDK can be found HERE.

What does an implementation project look like?

Implementation of the configurator can be approached in many different ways. This depends on the product structure (structure of rules), the presentation to users (vendors and, if applicable, customers), and the link with other systems (eg ERP). That is why we often help our customers with a design in the form of a Proof Of Concept, after which you are able to take over the implementation and maintenance.

Stap 1 – Proof Of Concept

Let us prove that Elfskot works for your product. First, we identify the required functionality and outline a layout that works. Then we implement one of the products that is representative for the entire range. Feel free to show it to friends, colleagues, dealers and customers.

Stap 2 – Implementation

Basically, the Proof Of Concept is a turn-key solution; you should be able to implement and maintain the entire product range by yourself. The Proof Of Concept serves as an example (template).
Note: Of course we can help; that is available on demand.

Stap 3 – LIVE en Partnership

We host the application online, so you don’t have to worry about maintenance of data or extra hardware. We guarantee uptime and deliver new updates free of charge.

How long does an implementation take?

This is a question that is asked quite often. The software itself makes it possible to parameterise (fine-tune) very quickly and easily; it does however depend on input. Namely; In order to build product structures (rules), logic must be introduced in both the product package and the argumentation scheme (sales). If this is available, we can create a workable solution very quickly. For example; in one case we have fully implemented 56 complex products in 1 business day.

For reference:

  • Are all products and structures (rules) available? Suppose I choose option A, what are the consequences for option B. Is there documentation available?
  • Can the argumentation scheme of sales (guided selling) be structured into logic? Eg: by default, the configuration contains option A, based on which arguments do I convince a customer to choose option B?
  • Are all articles and all of their master data (prices, texts) available?
    Is it going to be linked to other systems (eg ERP / CRM / PDM)?

Please note that above is absolutely NOT preliminary required to work with the Elfskot Configurator. Forget about Excel; we have the tools to quickly arrange input.

Where is the dividing line between Configure-to-Order and Engineer-to-Order?

This limit seems very diffuse. To answer the question, we must first delve into the definitions:

  • Engineer to order: The product range is not (fully) standardized: R&D is required for every new request.
  • Configure to order: The product range is standardized. Components can be assembled into an end product based on logic.

The crux is in the word “Logic”. Logic contains the conditions within a product package: Option A is not possible in combination with option B and must be correct with option B. Conditions can also follow from parameters: With length x meter, the number of Y legs is required. As soon as these conditions can be cast within logic, it is called Configure-to-Order.

The dividing line between an ETO product package and a CTO product package is therefore also directly determined by the state of the art. We are, moreover, fully cooperating with this: Whereas, five years ago, certain logic was too complex to be put into conditions, the current state of technology may well allow that. For example, the dividing line is shifting from ETO to CTO.

View the entire article about the shift from Engineer-to-Order to Configure-to-Order.

Do you also want to sell stress free?

Discover without obligation what the Elfskot Product Configurator can mean for your organization.

Request a free demo Or contact us