Litekart v2.0

We ship decently fast

Started in 2014 as ShopNx, Litekart has evolved into a powerful ecommerce platform. Today, it powers over 800+ stores worldwide, offering enterprise-grade features with the flexibility of custom development.

Built with ❤️ by our amazing contributors

Version v8.37
September
Week 37 2025
  • Fixed Meilisearch filter strings for correct string matching.
  • Development points:
  • - Added proper HTTP status codes to error responses in admin orders list endpoint
  • Improved query validation for admin orders list endpoint by adding Zod schema and error response for invalid parameters.
  • Fixed HTTP status codes in error responses for post-sale payment handlers and admin orders list endpoint.
Version v8.36
September
Week 36 2025
  • Enhanced user experience by providing a more informative error message.
  • Addressed an issue with deleting addresses that could cause confusion for users.
  • Improved error message when deleting an address that violates a foreign key constraint.
  • Improved user interface by hiding admin not approved warning.
  • Resolved error with creating a stripe session and finding currency table.
  • Fixed security issue by hiding sensitive information and resetting link in admin-forgot-password route.
  • Fixed issue with listing customers in admin route.
  • route
  • Refactored code for email verification page, including removing unused variables and simplifying return statements.
  • Added a new endpoint for email verification specifically for admin users.
  • Added logic for retrieving default storeId for admin join and made minor code adjustments for consistency.
  • - Removed storeId from token and userId validation logic in auth handlers
  • Litekart removed from login page to accommodate for white labeling.
  • White labeling feature introduced with `isWhiteLabeled` variable and removal of Guides on login page.
  • Fixed order number typecast and ts-error, and updated order_no to be an integer and parentorderno to be a sequence.
Version v8.35
August
Week 35 2025
  • Addition of storeId check for exporting remaining products on the /export/admin-products page to ensure accurate data transfer.
  • Bug fixes for exporting products and creating stores: The commits address bugs related to exporting products and creating stores, indicating efforts to improve the functionality and user experience of the platform.
  • Fix for the country list at store creation to address any potential issues with selecting countries for store locations.
  • Implementation of customer_id instead of user_id for improved user identification and tracking.
  • Implementation of a new identifier system: The commits involve changing the user_id to customer_id, indicating the implementation of a new identifier system for customers.
  • Improvements to data accuracy and management: The changes made in the commits suggest a focus on improving the accuracy and management of data within the platform, potentially leading to a more efficient and reliable system.
  • The meilisearch version has been reverted to 0.48.2.
  • The storeId has been fixed in the auth/signup process.
  • Improved customer query functionality with the addition of storeId and updates to order and confirmation processes.
  • New admin API routes have been added for managing return reasons with CRUD operations.
  • The customer list has been separated from the user list.
  • Implementation of new admin API routes for managing return reasons and updates to dependencies for improved performance.
  • Separation of customer list and user list for improved organization and management.
  • The aws-sdk dependencies have been updated to the latest versions.
  • Introduction of new features, such as admin activities and notification history, and updates to existing endpoints.
  • The create-order function has been separated and confirm-order has been moved to its own file.
  • Admin activities have been introduced, including a new endpoint for admin user registration and a new feature for tracking notification history.
  • Shipping zone creation now occurs after the store has been created.
  • Customer queries now require a storeId.
  • Improved functionality and bug fixes related to shipping zones, formatting, and order detail loading.
  • Refactored schema relations to reference the AdminUser model instead of the Customer model, and replaced Customer references with AdminUser.
  • Development Point 3: Adding new features and functionality, such as API handlers for products, imports, carts, and settings, as well as creating initial e-commerce API routes and database schema files.
  • Updated Stripe API version and simplified database migration scripts, as well as updating TypeScript build and buildx scripts.
  • Development Point 1: Refactoring and improving type safety in the codebase, including updating the customer schema and replacing references to the Customer model with AdminUser.
  • Development Point 2: Improving security and functionality in the authentication handlers, including updating password validation and adding token validation checks.
  • Improved type safety and refactored customer schema and handlers for better organization and maintainability.
  • Added new API handlers for products, imports, carts, and settings routes, and created initial e-commerce API routes and database schema files.
  • Enhanced security by fixing password validation and implementing token validation checks in auth handlers.
  • Refactored chat schema to use OpenAPI variants and updated return type checking in handlers.
  • Refactoring of chat schema references to use OpenAPI variants
  • Implemented order management and payment processing endpoints with multiple gateways.
  • Added various admin routes and handlers, as well as core API routes and handlers.
  • Implementation of various admin routes and handlers for background jobs, banners, auth, blogs, and more
  • Development of core API routes and handlers for admin and address management, order management and payment processing, ecommerce functionalities such as shipping, orders, products, and more, and vendor management and cart functionality.
  • API routes for core modules: The commits added API routes for products, orders, settings, and other core modules, allowing for easier access and management of these key components.
  • API routes were added for core modules such as products, orders, and settings.
  • Improved functionality: The addition of these API routes enhances the overall functionality of the project, providing a more comprehensive and efficient system for managing products, orders, and settings.
  • The addition of API routes improves the overall functionality and usability of the system.
  • Streamlined development: By creating API routes for multiple core modules at once, the development process is streamlined and more efficient, saving time and effort for future updates and improvements.
  • This development allows for easier access and manipulation of data within these modules.
Version v8.34
August
Week 34 2025
  • The team then added API routes for core e-commerce functionality, specifically payments, shipping, and checkout.
  • Core e-commerce functionality, including payments, shipping, and checkout, was implemented through additional API routes.
  • Initial API routes and handlers were added for key modules such as checkout, inventory, settings, and varni.
  • Finally, they implemented the initial database schema and API routes for overall e-commerce functionality.
  • The development team also added an initial database schema and implemented API routes to support e-commerce functionality.
  • The initial development focused on creating API routes and handlers for various modules such as checkout, inventory, settings, and varni.
  • Improved organization and structure of product and category URLs.
  • Migration of hierarchical category slugs
  • Migration to hierarchical category slugs
  • Implementation of store-scoped product slugs
  • Addition of new features to improve store functionality
  • Implemented a queue system for image uploads during product imports.
  • Integrated Stripe payment with session management and webhooks.
  • Implemented a queue system for uploading product images during imports.
  • Updated dependencies, including @antfu/eslint-config and @arcjet packages.
  • Added payment handlers for Affirm, PayPal, and PhonePe checkout.
  • Added support for multiple payment gateways, including PayPal, PhonePe, Stripe, and Affirm.
  • Integrated Stripe payment system with session management and webhooks.
  • Implemented multi-payment gateway integration with PayPal, PhonePe, Stripe, and Affirm.
  • Improved product caching and removed unnecessary ordering for better performance.
  • Improved product caching and ordering by moving outside of conditional block and removing createdAt ordering.
  • Focus on data organization and efficiency: Both of these commits focus on improving the organization and efficiency of data within the project, suggesting a focus on creating a solid foundation for future development and scalability.
  • Added payment and user schema: The developer added a new payment and user schema to the project, including relationships between the two and validation to ensure data integrity.
  • Addition of payment and user schemas with proper relations and validation for improved data organization and accuracy.
  • Implementation of database indexes for optimized query performance, leading to faster and more efficient data retrieval.
  • Improved query performance: Database indexes were added to improve the speed and efficiency of queries, potentially leading to a faster and more streamlined user experience.
  • Enhancements to project functionality: These commits suggest that the overall functionality of the project has been improved through the inclusion of new tools and utilities, making it more user-friendly and efficient.
  • Improved development efficiency: With the addition of these new tools and utilities, developers can save time and effort in managing databases and creating sitemaps, allowing them to focus on other aspects of development.
  • Implementation of sitemap generation utilities: The commit includes the addition of utilities that can automatically generate sitemaps for websites, improving website organization and navigation for users.
  • Addition of database management tools: This commit introduces new CLI tools that allow for easier management of databases, making it more efficient for developers to work with their data.
  • Introduction of sitemap generation utilities: This development point mentions the addition of utilities that can automatically generate sitemaps, making it easier to organize and navigate through the various pages of a website.
  • Addition of CLI tools for managing databases: This development point highlights the addition of new command-line tools that allow for easier and more efficient management of databases.
Version v8.32
August
Week 32 2025
  • Eliminated case-insensitive string comparisons in payment method lookups.
  • Enhanced payment method selection by using code instead of name and adding a code field to the response.
  • Fixed payment method selection by code instead of name and added code field to response for more accurate matching.
  • , improved readability and removed case-insensitive comparisons
  • Improved readability by deconstructing parameters for Razorpay order creation.
  • Improved readability of Razorpay order creation parameters by restructuring them.
  • Increased efficiency by removing case-insensitive string comparisons in payment method lookups.
Version v8.31
July
Week 31 2025
  • Enhanced user experience by providing a seamless payment flow.
  • Improved payment processing capabilities for the application.
  • Added confirmation flow for successful payments
  • Implemented Razorpay payment capture feature
  • Improved user experience by streamlining payment process
  • Added support for Razorpay payment capture and confirmation flow.
Version v8.30
July
Week 30 2025
  • Reset lockfile as a chore.
  • Improved consistency in CSS classes and adjusted z-index value.
  • Adjusting z-index value
  • Resetting lockfile and ordering timeline comment
  • display
  • Updating CSS classes for consistency
  • Fixed issue with timeline comment display order.
  • Enhanced stability by resolving bug causing crashes
  • Updated UI design and layout
  • Added new feature for user authentication
  • Added new feature for user authentication: This commit introduced a new feature that allows users to authenticate their accounts, providing a more secure login process.
  • Improved user experience with new authentication feature
  • Fixed bug with image uploading: This commit addressed a bug that was preventing users from uploading images to their profiles, improving the overall user experience.
  • Fixed bug causing crashes in certain scenarios
  • Refactored code for improved performance: This commit refactored the codebase to improve the performance of the application, resulting in faster load times and smoother functionality.
  • Improved aesthetics and usability with UI updates.
Version v8.29
July
Week 29 2025
  • Addition of currency code to parent order for improved tracking and organization.
  • Implementation of search engine crawling prevention: This commit introduces measures to prevent search engines from crawling and indexing the website, ensuring better security and privacy for the website and its users.
  • Implementation of measures to prevent search engine crawling and maintain privacy of the codebase.
  • Addition of currency code to parent order: This commit adds functionality to include the currency code in the parent order, allowing for better tracking and organization of orders based on currency.
  • Disallow all web crawlers in robots.txt for better website security.
  • Add mandatory email and phone fields to store settings for improved user data collection.
  • Disallowed all web crawlers in robots.txt to protect website content.
  • Added mandatory fields for email and phone in store settings for improved user experience.
  • Update query parameter in PageService list method from 'q' to 'search' for improved functionality.
  • Updated query parameter in PageService list method from 'q' to 'search' for improved functionality.
  • Added new features for toggling mandatory phone and email fields in General settings.
  • Fixed issues with ownership and business country settings in the dash/setting section.
  • Fixed issues with ownership and business country settings in the dashboard.
  • Added toggles for mandatory phone and email fields in General settings.
Version v8.28
July
Week 28 2025
  • - Implemented database management scripts and store settings handlers
  • - Added currency exchange rate schema and seed data for INR rate
  • Updated currency exchange rates to be valid for full calendar year.
  • - Fixed currency exchange rate validity period and phone number validation logic
  • Added currency exchange rate functionality including schema and seed data.
  • Fixed phone number validation to only occur when necessary.
  • Implemented database management scripts and store settings handlers.
  • These developments suggest a commitment to improving the overall functionality and usability of the platform for both administrators and customers.
  • The store checkout process now includes validation toggles for phone and email.
  • Mandatory flags for phone and email have been added to the settings schema.
  • The addition of mandatory flags for phone and email in the settings schema suggests a focus on improving data accuracy and completeness.
  • The inclusion of validation toggles for phone and email during store checkout indicates a focus on enhancing the user experience and reducing errors during the purchasing process.
  • Implementation of footer HTML module to payment shipping handler plugins and addition of footer HTML plugin and store configuration.
  • Refactoring of footer-html plugin into footer-settings plugin.
  • Refactoring and merging of footer-html plugin into footer-settings plugin.
  • Implementation of cart and authentication handlers with user management and shipping calculations.
  • Addition of footer HTML plugin and store configuration.
  • Addition of success header field for enquiry form configuration and handler.
  • Implementation of footer HTML module for payment shipping handler plugins.
  • Implementation of cart and auth handlers with user management and shipping calculations.
  • Addition of success header field to enquiry form configuration and handler.
  • Enhancements to the project's functionality and user experience.
  • HTML content support: The news ticker plugin now supports HTML content, allowing for more customization and dynamic content to be displayed.
  • New plugin added: A news ticker plugin has been added, providing users with a new feature to display scrolling news on their website.
  • Addition of a news ticker plugin to the project.
  • The plugin supports HTML content.
  • Enhanced user experience: This new feature enhances the overall user experience and adds more versatility to the website design options.
Version v8.27
July
Week 27 2025
  • Standardizes product field attribute naming for consistency in exports.
  • Enhancements to export functionality: improved field naming, added invoice generation in fulfillment process, and migration to Biome formatter with new import features.
  • Improved sorting and consistency in getOne handler with changes to line item order and product field attribute naming.
  • Improvements to getOne handler: changes order of line items to descending by created date and adds createdAt field to product selection.
  • Migration to a new formatter with added import features.
  • Enhanced functionality in getOne handler with the addition of a createdAt field and improved export capabilities, including invoice generation.
  • Improved functionality and compatibility with updated libraries and dependencies
  • Updated @friendofsvelte/tipex to version 0.0.8
  • Development focused on improving functionality and keeping dependencies up-to-date.
  • Implemented store selection data mapping in create store page
  • Upgraded @friendofsvelte/tipex to version 0.0.8
  • Focus on improving overall functionality: These commits suggest that the development focus was on improving the overall functionality of the project. By adding database management scripts and app initialization setup, the project becomes more functional and powerful, potentially enhancing its capabilities
  • Implemented app initialization setup to streamline the setup process for new users.
  • Improved overall efficiency and organization of the development process by incorporating these new features.
  • Addition of database management scripts: The commits indicate that database management scripts were added, indicating a significant development in the project. This could mean that the project now has the ability to manage and manipulate data, making it more robust and dynamic.
  • Implementation of app initialization setup: The commits also mention the setup of app initialization, which suggests that the project now has a more streamlined and efficient way of starting up and running. This could potentially improve the user experience and make the app more user-friendly.
  • Added database management scripts for easier database maintenance and updates.