The latest articles on DEV Community by Nazmul Ahsan (@mukto90). https://dev.to/mukto90 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2435755%2Feaf894c0-eacd-46cf-850f-124a832865b7.png https://dev.to/mukto90 en Nazmul Ahsan Fri, 26 Jun 2026 13:36:12 +0000 https://dev.to/mukto90/i-spent-18-months-building-an-ai-native-ecommerce-plugin-for-wordpress-here-is-what-i-learned-1636 https://dev.to/mukto90/i-spent-18-months-building-an-ai-native-ecommerce-plugin-for-wordpress-here-is-what-i-learned-1636 <p>Quick intro: I have been writing WordPress since 2009 and shipping products since 2017. For the last 18 months I have been building <strong><a href="https://easycommerce.dev/" rel="noopener noreferrer">EasyCommerce</a></strong>, an AI-native ecommerce plugin, as a WooCommerce alternative. It has been stable and in production since 2025, nearly 30 releases in, with real stores running on it.</p> <p>A few decisions I would defend:</p> <p><strong>1. Dedicated database tables from day one.</strong> Orders, products and customers live in their own <code>wp_ec_*</code> tables instead of <code>wp_posts</code> and <code>wp_postmeta</code>. More on why in a follow-up post, but the short version is that ecommerce query patterns and the post/meta model do not get along at scale.</p> <p><strong>2. AI as core, not a bolt-on.</strong> The headline feature is a shopping agent with 23 tools that can run a full conversation with a customer, search the catalogue, apply a coupon and place an order. It is agentic, not a prompt box.</p> <p><strong>3. Ship in the open</strong>. I will be posting the architecture calls, the things that broke, and the onboarding numbers here.</p> <p>If you build WordPress or ecommerce products: what is one architecture decision you made early that you would make again?</p> webdev wordpress ai ecommerce