Product catalog and variants
Categories, attributes, variant combinations, bulk upload by spreadsheet and media management for product images and videos.
Selling online looks simple from the customer's side: browse, add to cart, pay. Behind it sits software that manages products and stock, takes payments, routes orders to the warehouse, handles returns and, in a marketplace, pays many sellers their share. This guide explains how ecommerce and marketplace software is organized and helps you decide between a hosted platform and a custom build.
Ecommerce software runs an online store where one business sells its own products. It includes the storefront customers see and an admin area where your team manages products, prices, stock, orders, discounts and customers. Marketplace software adds a third party: independent vendors who list their own products, fulfill their own orders and receive payouts after the marketplace keeps a commission.
That difference matters. A single-brand store is mainly a catalog and an order engine. A marketplace also needs vendor onboarding, listing approvals, commission rules, settlement reports, dispute handling and controls that stop one seller from seeing another seller's data. This extra layer is where much of the complexity, and cost, of marketplace projects lies.
Both models can run on a hosted platform, where a provider operates the software and you pay a subscription plus transaction or app fees, or as custom software you own and host. Many businesses start hosted and later move to custom, or combine the two, as their catalog, order volume or business model becomes more specific.
Products are created with titles, descriptions, images, prices, tax categories and variants such as size or color. Each variant has its own stock count and SKU, the code your team and warehouse use to identify it.
Customers find products through categories, search and filters such as price, brand or size. Good search tolerates spelling mistakes and understands the everyday words your customers use for products.
The cart holds items, applies coupons and calculates taxes and shipping. Checkout collects the address, offers delivery options and hands payment to a payment gateway, which reports success or failure back to the store.
A confirmed order reduces stock, notifies the warehouse or vendor and generates an invoice. Once packed, it gets a shipping label and tracking number through a courier integration.
Customers track orders, request returns or exchanges and receive refunds. Each return follows rules about the eligibility window, quality checks and whether the item goes back on sale.
In a marketplace, each completed order is split into the vendor's share, the platform commission and any fees. Payouts are calculated on a schedule, often after the return window closes, and vendors see statements in their own dashboard.
Not every business needs every module. Start with the ones tied to your biggest bottleneck.
Categories, attributes, variant combinations, bulk upload by spreadsheet and media management for product images and videos.
Sign-in by email or phone OTP, saved addresses, order history, wishlists and optional guest checkout for first-time buyers.
Keyword search, filters by attribute, sorting options and merchandising controls that let your team promote or pin selected products.
Coupons, tax calculation, shipping rules, cash on delivery where offered, and payment gateway integration for cards, UPI, net banking and wallets.
Stock levels synchronized with a warehouse, ERP or point-of-sale system, so the website does not keep selling items that are already gone.
Order statuses from placed to delivered, partial shipments, cancellations, invoices, and courier integration for labels and tracking.
Return requests with reasons and photos, approval rules, pickup scheduling, quality checks and refunds to the original payment method or as store credit.
Seller registration, document verification, listing moderation, commission rates by category or vendor, settlement cycles, deductions for returns and payout statements.
Separate permissions for catalog managers, customer support, warehouse staff and finance, with activity logs for sensitive changes such as price edits and refunds.
Hosted ecommerce platforms such as Shopify, or open-source options such as WooCommerce on WordPress, let a business launch a store quickly with themes, payments and add-on apps. They are often the sensible choice for a first store. Costs grow through plan upgrades, paid apps and transaction fees, and deep changes to checkout, pricing logic or marketplace rules can be limited or depend on several plugins working together.
A custom ecommerce or marketplace platform suits businesses with specific pricing rules, B2B accounts, complex catalogs, marketplace commissions and payouts, or tight integration with ERP and warehouse systems. You own the code and the customer experience, and there are no platform transaction fees beyond what payment gateways charge. In exchange, you take on hosting, security updates, performance work and ongoing development.
Our view: If you are validating demand or selling a modest catalog, start on a hosted platform and invest in product content and marketing. Consider custom development when the platform itself is your business model, as with most multi-vendor marketplaces, when platform limits keep shaping decisions you would rather make yourself, or when integration with your operations becomes the main bottleneck. A headless setup, where a custom storefront sits on top of an existing commerce backend, can be a middle path.
An online store sells one business's products. A marketplace lets multiple independent vendors list and sell, while the platform owner runs the storefront, takes a commission and pays vendors their share. Marketplaces need extra features for vendor onboarding, moderation and settlements.
For many first stores, a hosted or open-source platform is the practical starting point because it is faster to launch and costs less upfront. Custom development becomes worthwhile when your pricing, catalog, marketplace or integration needs repeatedly run into platform limits. Some businesses keep the platform's backend and build a custom storefront on top.
Each order is split into the vendor's amount, the platform commission and any fees. Payouts are typically released on a schedule after the return window, with deductions for returns or penalties. Payment gateways that support split settlements can automate part of this, subject to their own eligibility rules.
Yes, through integration with your inventory, ERP or point-of-sale system. Stock can be updated in near real time or synchronized at intervals. The right approach depends on how fast items sell and how many channels share the same stock.
Customers raise a return from their order page with a reason and sometimes photos. The system applies your eligibility rules, schedules a pickup, records the quality check and triggers a refund or exchange. Reports on return reasons help spot sizing or quality problems.
A store on a hosted platform can often launch within a few weeks if product content is ready. A custom store or marketplace typically starts with a focused first release over several weeks to a few months, with vendor tools or advanced promotions added in later phases, depending on scope.
Describe how your team works today. We will tell you honestly whether a ready-made tool, a customized one or a custom build makes sense.