Trust is key when it comes to just about all of our interactions, be it business or personal. Regardless of how successful a relationship is, trust is always something that has to be built, tracked and maintained.

At its most fundamental level, trust is built one person at a time, at self-consciousness levels. Social distancing and our new work-from-home culture pose challenges when it comes to building trust, especially in new relationships.

This newfound distancing we all find ourselves in also presents larger and quicker opportunities to erode trust, which affects the social capital and resources needed to operate in a healthy and productive relationship. 

In the field of e-commerce, one of the most vital factors for the business is how the user interacts with the website. If the king is content, then the queen is usability. The website should be designed for the user’s needs in the first place. That’s why every business owner should make sure, that the tendency of the client-oriented approach is followed. The client wants to have a possibility to feel admiration, to think slow and do fast. If you want to generate income in your business – figure out how to achieve unique advantages over the competitors.

Most likely, at least once you faced the issue when customer session does not work except an account page etc. And usually, it’s not obvious why. Is it a bug? No, actually that is the case when it’s not a bug, it’s kind of feature.

The Magento page cache library contains a simple PHP reverse proxy that enables page content caching. There are two types of distinguished content: private and public.

The “private” content is being served for each user separately and represents the personalized data of a customer. E.g. shopping cart, wishlist, customer addresses, notification messages. This data should not be cached on the server side, and should not be shown to more than one user. The private content is stored on the client’s side by Customer Data JS component (Magento_Customer/js/customer-data.js). However, this is a topic for another blog post. Today we will focus on the second content type – public content, or rather the cacheable content and its variations in terms of customer grouping.

As everyone who uses Magento knows, in most cases after each order, the customer receives an order confirmation email which contains some useful information about an order that has been just placed. However, sometimes, it would be great to provide some additional information alongside with an order confirmation – such as payment information. There are some ways in Magento for extending emails with custom info, but often they require a lot of time and deep technical knowledges. Let’s leave these ways for people who has an extra time and review the simple and fast way how to add an invoice information to the order confirmation email.

It is a good idea to create a new layout handle in Magento when we need to be able to easily customize styling of pages or enable/disable specific blocks for the customer groups. Here is how.

In this article I’d like to explain how to create multiselect product attribute which will allow to restrict actions depending on a customer group. This feature can be used to hide price of the product, disable product addition to cart or set other restrictions basing on a customer group.

Back to Part 1.

In Magento, customers don’t use special numbering by default; however it is possible to change this. We need to add a record to the eav_entity_store table with entity_type_id = 1, increment_prefix = CU and increment_last_id = CU001000.

In Magento, order numbers are generated starting from 100000001 and up by default. Many companies want to use a custom value so that customers don’t know exactly how many orders have been placed before. Others need a custom value to match other parts of their system. The field increment_id is present in various entity tables to store this number.