Migration from Merx

When I mentioned that Kart is highly compatible with Merx, I meant that their core concepts are similar. I have maintained consistent names for fields and methods, or at least provided fallbacks where possible. This means porting an existing shop with products from Merx to Kart is feasible.

Ideally, you would uninstall Merx and install Kart, and everything would function seamlessly. However, that's not the case in reality. Here are some tips for addressing the most common issues you may encounter.

If you are trying to migrate, I would be happy to hop on a call with you, help you with it, and improve this guide.

Products

Products and prices can be stored in the cloud with the provider and only synced into Kirby, but overall the blueprint for a product within Merx is very similar to the one in the Kirby Kart plugin
All files for the products are stored in the "media pool" on the products page
The tax rate does not exist in Kart
Additional fields can only be added on the site/blueprints/tabs/product blueprint

Orders

The invoice number is not deduced from the slug/title but from the invnumber-field
Tax on items is the amount in currency, not the tax rate
Items have total, subtotal, discount, tax, in addition to price and quantity
Customers are stored as a reference to user accounts, not as email addresses

Set and flush global messages Translation / Languages