{"id":4779,"date":"2021-07-13T18:23:45","date_gmt":"2021-07-13T12:53:45","guid":{"rendered":"https:\/\/blog.guvi.in\/?p=4779"},"modified":"2026-09-22T14:19:32","modified_gmt":"2026-09-22T08:49:32","slug":"create-your-own-ecommerce-website-like-amazon","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/create-your-own-ecommerce-website-like-amazon\/","title":{"rendered":"How to Build an eCommerce Website Like Amazon or Flipkart in 2026 &#8211; Best Guide"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><strong>TL;DR<\/strong><\/h2>\n\n\n\n<p>To build an eCommerce Website like Amazon or Flipkart, start with an MVP instead of trying to copy every marketplace feature. Your first version needs customer and seller accounts, product listings, search and filters, cart, checkout, payments, order management, reviews, inventory, and an admin dashboard. A practical 2026 stack can use React or Next.js for the frontend, Node.js with Express or NestJS for the backend, PostgreSQL or MongoDB for data, Redis for caching, object storage for product media, and a payment gateway such as Razorpay or Stripe. Build the eCommerce Website as a modular application first, then add more services only when scale requires them.<\/p>\n\n\n\n<p class=\"has-drop-cap\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Should You Know Before Building an eCommerce Website?<\/h2>\n\n\n\n<p>An eCommerce Website like Amazon or Flipkart is more than a product catalogue. It connects customers, sellers, payments, inventory, orders, search, reviews, shipping, and administration in one system.<\/p>\n\n\n\n<p>The easiest way to build an eCommerce Website is to begin with the core buying and selling flow, then add advanced marketplace features in stages. You do not need Amazon-level infrastructure for the first version.<\/p>\n\n\n\n<p>This guide explains the features, architecture, development steps, and updated 2026 tech stack needed to create an eCommerce Website from scratch.<\/p>\n\n\n\n<p>If you are still learning the basics, <a href=\"https:\/\/www.guvi.in\/blog\/web-development-roadmap-for-beginners\/\" target=\"_blank\" rel=\"noreferrer noopener\">web development roadmap<\/a> before starting the project will help.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Makes an eCommerce Website Like Amazon or Flipkart Work?<\/h2>\n\n\n\n<p>A successful eCommerce Website makes it easy for users to discover products, compare options, trust sellers, complete payments, and track orders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Easy Product Discovery<\/strong><\/h3>\n\n\n\n<p>Use clear categories, useful filters, fast search, product suggestions, and simple navigation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Trust and Product Information<\/strong><\/h3>\n\n\n\n<p>Show clear product images, descriptions, prices, seller details, delivery information, ratings, reviews, and return policies.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Simple Checkout<\/strong><\/h3>\n\n\n\n<p>Keep the cart and checkout flow short. Support the payment methods your target customers actually use and show the full order amount before payment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Reliable Order Experience<\/strong><\/h3>\n\n\n\n<p>A good marketplace should keep inventory, payment status, shipping status, cancellations, returns, and notifications connected.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">eCommerce Website Architecture at a Glance<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Layer<\/strong><\/td><td><strong>What It Handles<\/strong><\/td><td><strong>Practical 2026 Options<\/strong><\/td><\/tr><tr><td>Frontend<\/td><td>Product pages, cart, checkout, dashboards<\/td><td>React, Next.js<\/td><\/tr><tr><td>Backend<\/td><td>Business logic, orders, sellers, payments<\/td><td>Node.js + Express\/NestJS<\/td><\/tr><tr><td>API<\/td><td>Frontend-to-backend communication<\/td><td>REST or GraphQL<\/td><\/tr><tr><td>Database<\/td><td>Users, products, orders, inventory<\/td><td>PostgreSQL or MongoDB<\/td><\/tr><tr><td>Cache<\/td><td>Sessions, carts, frequent reads<\/td><td>Redis<\/td><\/tr><tr><td>Search<\/td><td>Product search and filters<\/td><td>Database search first; OpenSearch\/Elasticsearch at scale<\/td><\/tr><tr><td>Media storage<\/td><td>Product images and files<\/td><td>S3-compatible object storage<\/td><\/tr><tr><td>Payments<\/td><td>Checkout and payment confirmation<\/td><td>Razorpay, Stripe or another supported gateway<\/td><\/tr><tr><td>Authentication<\/td><td>Login and role-based access<\/td><td>Secure sessions\/JWT with customer, seller and admin roles<\/td><\/tr><tr><td>Deployment<\/td><td>Hosting, scaling and monitoring<\/td><td>Cloud platform + CDN + monitoring<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>For a beginner project, keep the architecture simple. A modular monolith is easier to build, test, and deploy than starting with many microservices.<\/p>\n\n\n\n<div style=\"background-color: #099f4e; border: 3px solid #110053; border-radius: 12px; padding: 18px 22px; color: #ffffff; font-size: 18px; font-family: Montserrat, Helvetica, sans-serif; line-height: 1.6; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); max-width: 750px;\"><strong style=\"font-size: 22px; color: #ffffff;\">\ud83d\udca1 Did You Know?<\/strong> <br \/>\n<p><a href=\"https:\/\/www.aboutamazon.com\/news\/books-and-authors\/books-are-in-our-dna\" target=\"_blank\" rel=\"noopener\"><strong>Amazon <\/strong><\/a><strong>started as an online bookstore in 1995 before growing into one of the world&rsquo;s biggest eCommerce platforms. It shows how an eCommerce website can start with one clear product category and expand over time. <\/strong><\/p>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Core Features Your eCommerce Website Needs<\/h2>\n\n\n\n<p>Update the current feature list to this order:<\/p>\n\n\n\n<ol>\n<li><strong>Customer Accounts<\/strong> \u2013 registration, login, profile, saved addresses and order history.<\/li>\n\n\n\n<li><strong>Seller Accounts<\/strong> \u2013 seller onboarding, product management, inventory, orders and payouts.<\/li>\n\n\n\n<li><strong>Admin Dashboard<\/strong> \u2013 manage users, sellers, products, categories, orders, refunds and reports.<\/li>\n\n\n\n<li><strong>Product Catalogue<\/strong> \u2013 titles, descriptions, images, variants, prices, stock and categories.<\/li>\n\n\n\n<li><strong>Search and Filters<\/strong> \u2013 search by product name and filter by category, price, brand, rating or availability.<\/li>\n\n\n\n<li><strong>Cart and Wishlist<\/strong> \u2013 add, remove, update quantity and save products for later.<\/li>\n\n\n\n<li><strong>Checkout and Payments<\/strong> \u2013 addresses, shipping choice, coupons, payment and confirmation.<\/li>\n\n\n\n<li><strong>Inventory Management<\/strong> \u2013 update stock when orders are placed, cancelled or returned.<\/li>\n\n\n\n<li><strong>Order Management<\/strong> \u2013 order creation, payment state, fulfilment, delivery, cancellation and returns.<\/li>\n\n\n\n<li><strong>Ratings and Reviews<\/strong> \u2013 verified reviews and moderation controls.<\/li>\n\n\n\n<li><strong>Notifications<\/strong> \u2013 email, SMS or push alerts for important order events.<\/li>\n\n\n\n<li><strong>Security and Permissions<\/strong> \u2013 protect customer data and separate customer, seller and admin access.<\/li>\n<\/ol>\n\n\n\n<p>These features are enough to make the first version useful without copying every Amazon or Flipkart function.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Build an eCommerce Website Step by Step<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1: Define the Marketplace Model<\/strong><\/h3>\n\n\n\n<p>Decide whether the platform will sell your own products or allow multiple sellers. Amazon and Flipkart are marketplaces, so a true marketplace version needs separate customer, seller and admin workflows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2: Plan the Database<\/strong><\/h3>\n\n\n\n<p>Create models for users, sellers, products, categories, product variants, inventory, carts, orders, payments, reviews and addresses. If you use MongoDB, <a href=\"https:\/\/www.guvi.in\/blog\/guide-to-data-modeling-in-mongodb\/\" target=\"_blank\" rel=\"noreferrer noopener\">MongoDB data modeling guide<\/a> can help you structure collections and relationships.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 3: Build the Frontend<\/strong><\/h3>\n\n\n\n<p>Create the homepage, category pages, product pages, search, cart, checkout, account area and seller dashboard. Interactive actions such as adding products to a cart depend on JavaScript events; see <a href=\"https:\/\/www.guvi.in\/blog\/guide-for-events-in-javascript\/\" target=\"_blank\" rel=\"noreferrer noopener\">JavaScript events guide<\/a> for the basics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 4: Build the Backend and APIs<\/strong><\/h3>\n\n\n\n<p>Create APIs for authentication, products, carts, orders, payments, reviews and seller operations. <a href=\"https:\/\/www.guvi.in\/blog\/what-is-rest-api\/\" target=\"_blank\" rel=\"noreferrer noopener\">REST API guide<\/a> explains how frontend and backend systems exchange data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 5: Add Authentication and Roles<\/strong><\/h3>\n\n\n\n<p>The platform should clearly separate customer, seller and administrator permissions. Protect private routes and never trust role information sent only from the browser.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 6: Integrate Payments<\/strong><\/h3>\n\n\n\n<p>Create the order on the server, send the user through the payment flow, and verify the payment result on the backend before marking the order as paid.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 7: Add Inventory and Order Logic<\/strong><\/h3>\n\n\n\n<p>Prevent overselling, update inventory carefully, store order status changes, and handle cancellation, refund and return states.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 8: Test the Full Buying Flow<\/strong><\/h3>\n\n\n\n<p>Test registration, search, filters, cart updates, checkout, failed payments, successful payments, stock changes, order history and admin actions before launching the eCommerce Website.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 9: Deploy and Monitor<\/strong><\/h3>\n\n\n\n<p>Deploy the frontend, backend and database, use HTTPS, configure backups, add logs and monitoring, and test the site on mobile as well as desktop.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Best Tech Stack for an eCommerce Website in 2026<\/h2>\n\n\n\n<p>Do not present one stack as the only correct choice. Use this practical recommendation:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Option 1: MERN Stack<\/strong><\/h3>\n\n\n\n<ul>\n<li>MongoDB<\/li>\n\n\n\n<li>Express.js<\/li>\n\n\n\n<li>React<\/li>\n\n\n\n<li>Node.js<\/li>\n<\/ul>\n\n\n\n<p>This is a good choice for a portfolio project because JavaScript can be used across the application. Link <strong>MERN Stack projects<\/strong> once to <a href=\"https:\/\/www.guvi.in\/blog\/best-mern-stack-projects-ideas\/\" target=\"_blank\" rel=\"noreferrer noopener\">MERN Stack project ideas<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Option 2: Next.js + Node.js + PostgreSQL<\/strong><\/h3>\n\n\n\n<ul>\n<li>Next.js for the web application<\/li>\n\n\n\n<li>Node.js\/NestJS or Express for backend services<\/li>\n\n\n\n<li>PostgreSQL for relational marketplace data<\/li>\n\n\n\n<li>Redis for caching<\/li>\n\n\n\n<li>Object storage for product media<\/li>\n<\/ul>\n\n\n\n<p>This stack works well when the marketplace needs strong product pages, structured order data, server-side rendering, and room to scale.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Option 3: Other Valid Backend Choices<\/strong><\/h3>\n\n\n\n<p>Java with Spring Boot, Python with Django\/FastAPI, and PHP with Laravel are also valid. Choose the stack your team can build, secure, test, and maintain well.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-style-default\"><img decoding=\"async\" width=\"1024\" height=\"682\" src=\"http:\/\/blog.guvi.in\/wp-content\/uploads\/2021\/07\/amazon-1-1024x682.jpg\" alt=\"Applications for ecommerce \" class=\"wp-image-4782\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-1024x682.jpg 1024w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-300x200.jpg 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-768x512.jpg 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-1536x1024.jpg 1536w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-600x400.jpg 600w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1-945x630.jpg 945w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/amazon-1.jpg 2000w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" title=\"\"><\/figure>\n\n\n\n<p>&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Storage, Database, Cache and Search<\/strong><\/h3>\n\n\n\n<p>For the platform:<\/p>\n\n\n\n<ul>\n<li>Store product images and documents in object storage.<\/li>\n\n\n\n<li>Store users, products, orders and inventory in a database.<\/li>\n\n\n\n<li>Use Redis for caching or short-lived data when needed.<\/li>\n\n\n\n<li>Start with database search for a small catalogue.<\/li>\n\n\n\n<li>Add a dedicated search engine such as OpenSearch or Elasticsearch only when search complexity or catalogue size justifies it.<\/li>\n<\/ul>\n\n\n\n<p>The database design is especially important because the platform has connected data such as products, variants, sellers, customers, inventory, payments and orders.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Security Checklist for an eCommerce Website<\/h2>\n\n\n\n<p>Before launch:<\/p>\n\n\n\n<ul>\n<li>Use HTTPS everywhere.<\/li>\n\n\n\n<li>Hash passwords with a trusted password-hashing library.<\/li>\n\n\n\n<li>Validate and sanitize user input.<\/li>\n\n\n\n<li>Use server-side authorization for customer, seller and admin routes.<\/li>\n\n\n\n<li>Never store raw card details yourself when a payment gateway can handle them.<\/li>\n\n\n\n<li>Verify payment callbacks or webhooks on the server.<\/li>\n\n\n\n<li>Add rate limiting to sensitive endpoints.<\/li>\n\n\n\n<li>Protect sessions and tokens.<\/li>\n\n\n\n<li>Keep dependencies updated.<\/li>\n\n\n\n<li>Back up important data.<\/li>\n\n\n\n<li>Log important account, payment and order actions.<\/li>\n<\/ul>\n\n\n\n<p>Security should be part of the eCommerce Website architecture from the beginning, not something added after launch.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Real-World Example: Building a Small Marketplace MVP<\/h2>\n\n\n\n<p>Suppose you are creating an eCommerce Website for local electronics sellers. Start with three roles: customer, seller and admin.<\/p>\n\n\n\n<p>Customers can search products, add items to a cart, pay and track orders. Sellers can add products, update prices and stock, and view their orders. The admin can approve sellers, manage categories, review orders and moderate products.<\/p>\n\n\n\n<p>Build this as one full-stack application first. Once the platform gets more traffic, you can separately improve search, caching, image delivery, notifications and other areas instead of rebuilding the whole platform from day one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common Mistakes When Building an eCommerce Website<\/h2>\n\n\n\n<ol>\n<li><strong>Trying to copy every Amazon feature:<\/strong> Build the buying and selling flow first.<\/li>\n\n\n\n<li><strong>Starting with microservices too early:<\/strong> Keep the first eCommerce Website architecture simple.<\/li>\n\n\n\n<li><strong>Ignoring inventory rules:<\/strong> Stock changes must work correctly during orders, cancellations and returns.<\/li>\n\n\n\n<li><strong>Trusting payment success from the browser:<\/strong> Verify payments on the server.<\/li>\n\n\n\n<li><strong>Ignoring mobile users:<\/strong> Test every important page on smaller screens.<\/li>\n\n\n\n<li><strong>Weak role permissions:<\/strong> Customers, sellers and admins should not have access to the same actions.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Build Your Own Full Stack Web Applications<\/h2>\n\n\n\n<p>Building an eCommerce website helps you practise frontend, backend, databases, APIs, authentication, and deployment in one project.<\/p>\n\n\n\n<p>If you want to build these skills step by step, explore the <a href=\"https:\/\/www.guvi.in\/full-stack-development-course?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=create-your-own-ecommerce-website-like-amazon\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>HCL GUVI\u2019s Full Stack Development Course<\/strong><\/a>. It covers the core technologies needed to build complete web applications and work on real projects, including eCommerce platforms.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>Building an eCommerce Website like Amazon or Flipkart is easier when you treat it as a series of smaller systems rather than one huge project. Start with users, products, search, cart, checkout, payments, inventory, orders and administration. Then add seller tools, caching, advanced search, notifications and scaling features as the platform grows.<\/p>\n\n\n\n<p>For a beginner or portfolio project, the best eCommerce Website is not the one with the most features. It is the one where the complete customer-to-order flow works correctly, the code is organized, the data is secure, and you can clearly explain how the frontend, backend, database and APIs work together.<\/p>\n\n\n\n<p>If you want to strengthen the full development flow before building the project, use&nbsp; HCL GUVI\u2019s<a href=\"https:\/\/www.guvi.in\/blog\/full-stack-developer-roadmap\/\" target=\"_blank\" rel=\"noreferrer noopener\"> full-stack developer roadmap<\/a> as a learning reference<\/p>\n\n\n\n<div class=\"wp-block-buttons is-horizontal is-content-justification-center is-layout-flex wp-container-1 wp-block-buttons-is-layout-flex\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">FAQs<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1789125952351\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>1. How do I create an eCommerce Website like Amazon or Flipkart?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Start with user accounts, product listings, search, cart, checkout, payments, orders, inventory and an admin panel. Add seller features if you are building a multi-vendor marketplace.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789125965338\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>2. Which tech stack is best for an eCommerce Website?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>MERN is a practical choice for JavaScript developers. Next.js with Node.js and PostgreSQL is another strong option. The best stack is one your team can build, secure and maintain well.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789125976667\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>3. Can a beginner build an eCommerce Website?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes. Start with a small single-vendor or basic marketplace project instead of trying to reproduce Amazon. Build one feature at a time and test the complete order flow.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789125995256\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>4. What database should I use for an eCommerce Website?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>PostgreSQL and MongoDB can both work. PostgreSQL is useful for strongly related transactional data, while MongoDB can be convenient for flexible product data. Choose based on your data model and team skills.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789126010816\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>5. What features should an eCommerce Website have?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>The core features are login, products, categories, search, filters, cart, checkout, payments, inventory, orders, reviews, seller tools where required, and an admin dashboard.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789126022856\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>6. Do I need microservices for an eCommerce Website?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>No. Most beginner and MVP projects should start with a modular monolith. Move selected parts to separate services only when traffic, team size or technical requirements make it useful.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789126034184\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>7. How do I make an eCommerce Website secure?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use HTTPS, secure authentication, server-side authorization, input validation, trusted payment gateways, rate limiting, dependency updates, backups and monitoring.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1789126052714\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>8. How can I make an eCommerce Website scalable?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Keep the application modular, optimize database queries, add indexes, use caching and a CDN, move media to object storage, monitor slow areas, and scale only the components that need more capacity.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>TL;DR To build an eCommerce Website like Amazon or Flipkart, start with an MVP instead of trying to copy every marketplace feature. Your first version needs customer and seller accounts, product listings, search and filters, cart, checkout, payments, order management, reviews, inventory, and an admin dashboard. A practical 2026 stack can use React or Next.js [&hellip;]<\/p>\n","protected":false},"author":76,"featured_media":5218,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[294],"tags":[],"views":"33354","authorinfo":{"name":"Reemsha Khan","url":"https:\/\/www.guvi.in\/blog\/author\/reemsha-khan\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2021\/07\/Ecommerce-Blog-300x157.jpg","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/4779"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/76"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=4779"}],"version-history":[{"count":38,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/4779\/revisions"}],"predecessor-version":[{"id":139949,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/4779\/revisions\/139949"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/5218"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=4779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=4779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=4779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}