<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Imagemagick on Mateusz Najdek - blog</title><link>http://blog.najdek.me/tags/imagemagick/</link><description>Recent content in Imagemagick on Mateusz Najdek - blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>mateusz@najdek.me (Mateusz Najdek)</managingEditor><webMaster>mateusz@najdek.me (Mateusz Najdek)</webMaster><lastBuildDate>Sat, 15 Nov 2025 12:00:00 +0200</lastBuildDate><atom:link href="http://blog.najdek.me/tags/imagemagick/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineering for Efficiency: Building a Custom Product Configurator to Automate Logistics</title><link>http://blog.najdek.me/posts/building-icup-custom-configurator/</link><pubDate>Sat, 15 Nov 2025 12:00:00 +0200</pubDate><author>mateusz@najdek.me (Mateusz Najdek)</author><guid>http://blog.najdek.me/posts/building-icup-custom-configurator/</guid><description>Context: In the world of personalized e-commerce on marketplaces like Allegro, the biggest bottleneck isn&amp;rsquo;t manufacturing—it&amp;rsquo;s matching the user&amp;rsquo;s design to the specific transaction without errors. Here is how I solved this problem with code.
The Problem: &amp;ldquo;Which &amp;lsquo;Anna&amp;rsquo; ordered this mug?&amp;rdquo; Selling custom products on Allegro (Poland&amp;rsquo;s largest marketplace) comes with a specific disconnect: the design tool lives outside the marketplace.
Most competitors solve this lazily: after designing a mug, they ask the user to &amp;ldquo;Type your Allegro Nickname&amp;rdquo; in a form.</description></item></channel></rss>