Magento Website Migration For Kulzer

Magento Migration

We migrated the German and French stores from Magento 1 to Magento 2, preserving all customer orders, data, and wishlists. Later, we created all other storefronts on Magento 2. Our team carried out the task in phases: each month, we added one or two stores, along with their order data, user information, and wishlists.

One of the difficulties the team faced was migrating wishlists instead of products. We had to create new products by attributes and match them with old ones in the migrated wishlists.

Dealers

Dealers claim much of the site’s functionality. The client has dealers all over the world. Each provides certain products for purchase on the site in a specific country. All the orders go to dealers first to process. We made some configurations for Kulzer to automate the work with dealers:

• To manage dealer-specific products, we implemented a visibility setting: if a dealer doesn’t offer a product, it becomes unavailable for users in that region.
• To show or hide the dealer for users, there is a setting in the admin panel for better personalization and control. Kulzer implemented this feature because some dealers only work with specific Kulzer’s clients. Initially, it was activated for the German store.
• To optimize logistics, we implemented the Minimum Quantity Surcharge setting. If the order total is less than €50, the system automatically adds a fixed €5 delivery fee. The administrator can configure this feature through the dealer management panel, allowing the setting of different shipping costs for various countries.

SAP and Algolia integrations

Before working with us, the client had already used the SAP system and Algolia. We migrated the systems to M2. SAP performs almost all tasks as ERP. This system manages:

• Orders
• Invoices
• Delivery
• Price
• Real-time stock
• Logistics

SAP also handles taxes. In Germany, there are different taxes for dental products and equipment. The system controls the taxes for every product and sets the required tax percentage when purchasing, such as 7% for crowns and 19% for dental equipment.

The client used Algolia on M1 before our collaboration. We added it to the webstore on Magento 2. The system increased the search and category page performance, improving user experience and reducing search times.

Matrix and Barcodes

The website features a crown matrix, which we initially pre-designed. It improved its performance significantly, allowing customers to place orders more quickly. The matrix is a table that displays each crown’s shade, shape, and position. Users simply input the required number of crowns into the corresponding cells.

This data is then converted into barcodes in PDF format. The barcodes are printed in a specific sequence: 48 to 60 barcodes per sheet. First, all the codes for the upper jaw are printed, followed by the codes for the lower jaw.

Each barcode belongs to a specific crown type and contains all the basic information about the product: shade, shape, tooth name, and SKU. The client places the barcodes on boxes with the matching crown type. When users scan the code, they can re-add the product to their cart.

Users can create their own barcode lists, which they can set as public or private. On the Barcode Designer page, they can select the shade and shape of the crown and then create pages with the corresponding barcodes. If they have multiple lists and need to move a barcode to a different page, they can use the Parking Lot field (displayed as “Parkplatz” on the screen). They need to place the barcode in the Parking Lot, navigate to the desired page, and insert the barcode there.

Once the barcode list is ready, a user can add products from the list to their cart, download it for printing, share it with others, or make copies. All lists are automatically saved in their account, allowing a user to reorder them in the future if necessary.

B2B features

Since Kulzer sells a specific product to B2B customers, we have implemented several features to simplify the client’s life.

To register, Kulzer’s client needs to make a request. Then, the manager will register the user and assign them a SAP number (or ID) in the system. There are cases when data changes for clients, such as a legal address. Users can change it upon request through the Kulzer manager. We added the setting for self registration in the admin panel if needed.

There are features that we also added:

• Client prices. Each user’s prices depend on their purchase history. Users won’t see the prices if they hit the order limits.
• Discount system. Almost all users receive discounts and have different prices for every product. For example, if there are 10,000 users on the site, there will be 10,000 different prices for the same product.
• Price visibility. Our team implemented the function allowing the admin to show or hide all prices. As a result, users can’t see them in the cart, checkou​​t, or emails. For some users, they can see prices for a specific product. It depends on how often buyers order and for what price.