New online shop with standard template

The standard template for the online shops of model Shop2016 is now available. Similar to the previous Amperhof model, it is easy to integrate into websites, but now uses modern technologies and is responsive, adaptative to different screen sizes. In addition, customers benefit from a multitude of new functions.

Although the configuration of the components in the web pages – unlike an individually built shop – cannot be changed, the style (colours etc.) can be customized by web designers. For ambitious users there is also a style editor, so it’s possible to make your first attempts at the design.

The conversion from the previously used standard template is already possible in a few hours.  The new possibilities of the article display and the menu control need some training, (By now, only in German) Information about different shop models is available and about the standard template Shop2016. We have prepared instructions (after login) for users and web designers and are happy to support you with the change.


Delivery is Due!

With the automatic order reminders, customers can always be reminded of upcoming deliveries. A large number of customers gladly accept this notice and update their order.

In the last few weeks many small enhancements have been added to this feature. Of course, the most important thing was the memory of customers who only order occasionally. These can be specifically marked in the communication settings of the PCG.

The time of sending was previously fixed at 9:00 a. m. – now you can select the desired hour for sending.

In order to get more transparency about the function of this automatic, the execution can now be simulated in the admin area of the shop. There is also the possibility to initiate the process by hand. Another new feature is a report that is sent to the admin email after execution.

If the message is sent as an SMS, several SMS numbers can now be stored at the customer’s premises. The internal number check ensures that no mails are sent to Timbuktu by mistake.

Item Representation: DataNatuRe, Ecoinform

Both, DataNatuRe as well as Ecoinform are currently primarily for german data consumers – perhaps that will change some time in the future.

For some time now, DataNatuRe has been building a product database for the organic and natural goods trade. In addition to data from our proprietary “Ökobox”-pool and that of the pioneer in this field, Ecoinform, our shops can now also display data from this new source.

In the online shop we need descriptions, pictures, exact manufacturer information and details of the ingredients. This is important for displaying, filtering and organizing information on the web pages. However, some of these are also important in the ERP backend. Anyone who has already registered new articles in the system knows how time-consuming this process can be.

Of course, it is as simple as possible for the seller if this data is complete and uniform, because then the import can be done automatically. Unfortunately, this is not always the case: why is it so difficult to get good article information for the online shop? Or to put it another way: why is it so difficult to build a unified database?

On the one hand, not every manufacturer has the capacity to present its products well for all sales channels. For example, an image should usually be high-resolution and rich in detail for printing, while for an article list in the online shop a striking and less data-intensive smaller image is more likely.

On the other hand, a central database is used by many people in different positions. They often have a very specific look at the data: Bookkeepers, for example, tend to look at prices rather than pictures, while marketing people focus on the text and the picture, rather than the ingredients. Statisticians compare merchandise categories and need the articles in a certain order. Some mean well and fill in the fields for description-long, descriptive-medium and description-short, others are in a hurry and write a sentence in the “-lang” field.

The article information also differs according to the product group – i. e. there are different data fields for a cheese (e. g. fat content, rind or rind type) than for a wine (drinking temperature or decanting time). And then the structure and type of data are not the same: the fat level is expressed in %, but there must be clear indications in the country of origin. Allergens can be one or 10, certifiers usually have one, but sometimes several.

This complexity is even evident in DataNatuRe’s rather young database, which is designed with modern means and on a broad basis. This way we get all the information for our system, but the preparation is not easy:

  • From the large number of data fields (more than 1000 in total) the relevant data fields for filtering or display in the online shop must be selected – even though the merchandise category assignment in the individual shops usually does not correspond to the data supplier’s specifications.
  • Many numerical values are not entered homogeneously and cannot be compared easily, e. g. during filtering (100ml are 0.1l, but a computer does not know this easily)
  • Despite a lot of trouble with the input masks, I have already seen vegans, which is explicitly not vegetarian, or a chicken broth which explicitly does not contain pork (oh).
  • It often happens that some articles have a super detailed description, others don’t – if these articles stand side by side in the shop, for example, this is noticeable negatively – not to mention article names that wind around the screen.
  • Unfortunately, images are typically not available on the web – optimized for small and large screens, for detail or list display. This is where automated image processing algorithms come into play, which have to cope with very different raw materials.

Last but not least, there is a series of additional information which in turn requires data to be added by other sources. For example, we have our own data pools with information on manufacturers, associations or origin marks.

In order to make the use of all these information details as easy as possible, the InfoPool module is available in the PCG. Not only can groups of articles be edited en-mass, but you can also simplify your work with the help of simple dependency rules. Finally, the information must be correct, even if the manufacturer changes the formulation of a cream, for example.

The different pools can be activated in the shop settings. For fast results, the system can easily add missing information from these data sources, e. g. by assigning them via GTIN. There are also statistics on their use and query options, which can be used during data entry and for checking purposes.

Changes to the permissions system

This is still quite fresh, even if some emails have already arrived. The role assignment has been in the PCG for a long time now, and even if there are other plans to standardize the PCG and shop roles, the current reorganisation should come closer to the conditions in the companies.

Roles are set in the PCG in the employee administration or in the customer/net data.

The most important changes:

  • The super access (i. e. the one with a superpassword) doesn’t get a link to the admin-area anymore – this is only for customer support (and therefore better called super-customer)
  • Only logged-in users in admin role, WebDesigner role or the “drivers with privileges” have access to it, and then only to certain areas.
  • WebAdmins = WebDesigner no longer have access to sensitive data under Geo/Stats/Status
  • Driver MUST be in a driver’s role! Previously, the employee assignment was sufficient.

This means that, among other things, the operating data (key figures, statistics) can only be viewed by the correct “administrator”, usually as the manager.

As a side effect, there are now also easier access possibilities to the admin area directly from the PCG. More about this in a later article.