Skip to main content

General concepts

Introduction to products​

This section is designed to make users aware of some of the concepts that come into play when uploading and managing products in EVA.

Not a PIM system - pushed in via API​

Although you can set infinite product properties and identifiers on your products, EVA is not a full-blown replacement for a PIM system in which you manage product content from a user interface. This is why we rely on a 3rd party tool pushing this data in via an API.

Single product database​

To run your stores and e-commerce, EVA taps from a single product catalog globally. You can subdivide which store can sell which items via Assortments, but ultimately it starts with a single product master data across all stores, hosted in the cloud.

Prices and products are split​

In many traditional POS systems products and their prices are part of one and the same dataset. EVA makes a split here. Prices are separately managed via your Pricelists, allowing you to use the same single product globally by applying different prices per location or country.

No prices and orders without products first​

Before you can sell products in EVA, they have to exist in our database. And one step before that: before you can even set prices on products, the products have to exist in EVA first. This makes uploading products the essential first step of your EVA journey.

In case you want to backfill historical orders to EVA, you also need the related products to be in EVA first. When you have outlet stores that can sell items from many seasons ago, this could mean uploading years worth of products.

Product Hierarchy​

EVA allows you to load products in a hierarchical manner.

A common example: you sell a certain style of T-shirt in 3 different colors, each in 5 different sizes.

By structuring your products as such, you allow users to easily see what colors a product comes in, or to let you quickly apply discounts on parent product, which then automatically apply to underlying items.

Images are synced to our CDN​

When importing products you can give us image URLs. During the import proces,s EVA will access that URL and fetch the images. They will be automatically synced to our CDN, which will then be used to generate the images in our applications. This is to ensure speedy image loading.