B2C shop: conversion to Hyvä

When an order arrives, a rule decides which warehouse delivers: shipments abroad go to the second warehouse, in Germany the choice depends on the product category, for example gift ribbon. The value is stored on the order and shown as a column in the order grid.

On weekdays at 10 and 12 o'clock the orders are exported as CSV files, separated by warehouse, and transferred by SFTP. Only orders that can be processed are exported, and each order only once. A custom SFTP module handles the connection, listing, downloading and archiving of files.

The warehouses drop shipping lists via SFTP. On weekday afternoons they are loaded, and the shipments are created in the shop with a tracking number from DPD within Germany or from Asendia abroad. The processed file moves to an archive, and errors are reported by email.

Shipping costs are calculated from a table by destination and order and can be maintained in the admin.

As soon as a shipment is saved, the invoice is created automatically, and a cron job sends the invoice email every minute. Nobody has to create or send invoices by hand.

The invoice PDF is custom built, with logo, address, item table, totals and footer.

Order numbers follow a custom scheme and continue the previous numbering.

Files such as legal texts can be attached automatically to order emails, so customers receive them together with the confirmation.

The frontend is switched from the previous theme to Hyvä. Hyvä relies on Tailwind CSS and Alpine.js and needs far less JavaScript than the default Magento theme.

The familiar look of the shop stays. Header, menu, home page, category pages and product pages are rebuilt element by element in the new theme.

A bar in the cart and in the shop shows how much is still missing for free shipping.

Title, description and keywords for pages such as contact can be maintained in the admin, also per store view.

Each category gets a color field in the admin that is used for its display in the shop.

Customers withdraw via a form on the website, as § 312k of the German Civil Code requires. My Withdrawal Button module for Magento 2 served as the basis, and I adapted it to the customer's wishes. Requests land in an admin grid with a view per request, the request is logged with the IP address, and the team receives an email.

Visitor consent is collected through a consent manager, and the content security policy of the shop is whitelisted for the services in use.

Base price details and further mandatory information for German retail are integrated into the shop and adapted to the design.

Customers rate products directly in the shop. A reminder email asks them for a review after the order.

A blog and an HTML sitemap support visitors and search engines.

Magento, PHP and the installed modules are kept up to date, and problems are fixed.

New features are built by agreement, from small requests to custom modules.

The server is monitored and backed up, so the shop stays available and can be restored quickly if something goes wrong.