We’re trying to build a small marketplace-style ecommerce platform where different vendors can manage their own products, pricing rules vary per seller, and orders need to be split across multiple fulfillment flows. The problem is that most “standard” ecommerce setups break down pretty quickly once you introduce multi-vendor logic and custom pricing + inventory rules per seller. Right now we’re debating whether to build everything from scratch or use some kind of backend-first commerce system that already handles the core commerce logic (products, carts, orders, payments) but still allows full customization for marketplace-style workflows. What are people actually using for this kind of setup without ending up maintaining a full ecommerce engine internally?
Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.
Answers
Backend bottlenecks become a massive issue when you have dozens of sellers trying to update their inventory at the exact same time. The database locks up and checkout fails for buyers on the frontend. You should look into modular architectures where the core transaction engine runs entirely separate from the vendor management interface. Tools like Spree Commerce let developers swap out specific modules for cart logic while keeping the rest of the stack intact.
Separation of the frontend layer definitely solves a lot of those database issues during peak traffic. The catch is finding a reliable logic layer that developers can actually hook into easily. You can wire up the backend using the ecommerce API here https://medusajs.com/ . The codebase provides all the essential cart operations out of the box for quick deployment. Your engineers will simply construct the specific multi-vendor rules on top of those existing components.