Skip to content
Software

Market Te Lisi POS

Retail POS software for sales, products, stock, purchases and accounting, with a web interface and a Windows client.

Mockup Gallery

Local demo of the real software with fictional grocery products. No customer records or completed transactions are shown.

3 Images

Project Overview

Retail POS software for sales, products, stock, purchases and accounting, with a web interface and a Windows client.

The product covers the work at the till alongside the records behind each sale. Product, stock, purchasing and accounting views place customer transactions and internal retail administration in the same application context.

Built with Python, Django, JavaScript, Windows. The portfolio previews show the project's interface and visual structure.

Case study · Kosovo · Retail

Market Te Lisi POS: retail sales and stock software

A retail application for checkout, products, stock, purchases and accounting views, with a web interface and a Windows client.

Development scope
Retail application development with Python, Django and JavaScript, including a Windows client.
Concrete deliverables
  • Checkout, product search and stock management
  • Purchases, expenses and daily cash-register views
  • Accounting views, a web interface and a Windows client
Visible result
Sales and stock workflows are presented alongside purchasing and accounting functions. The gallery uses a local demonstration of the real software with fictional grocery items.

Checkout is one part of the retail workflow

A cashier searches for products and records a sale; stock, purchases and accounting provide the wider business context. Market Te Lisi POS covers these areas with product, inventory, purchase, expense and daily cash-register views. A useful retail application needs staff to understand the record relevant to their task without losing that context.

Web and Windows views of the same application

The documented stack is Python, Django and JavaScript, with a Windows client. Use the till, product and accounting screens to compare the interface with your shop’s workflow.

A cash total and a stock balance answer different questions

The daily till concerns sales activity; the stock view concerns available products; purchase and expense records support another part of the operation. For your implementation, define what each view should answer and who will use it. Use the same sample product across the review so inconsistent records are easier to identify.

Bring three transactions to the first discussion

For a new POS brief, bring a normal sale, a purchase arriving into stock and a stock correction. Specify the expected record after each action, the staff role involved and the devices in use. Assess payment providers, printer compatibility and data migration against those examples before treating them as included integrations.

Key Features:

Point of sale and product search
Product catalog and stock management
Purchases and expense records
Daily cash register and accounting views

Discuss a similar project

Describe your workflow and what your business needs to do differently. We can discuss requirements, integrations and the scope of a first release.

Pricing is negotiable for each project. We agree the quote after discussing your requirements and the scope of work.

Market Te Lisi POS: retail sales and stock software

info@grevision-ks.com
We use these details to respond to your enquiry. Read our privacy notice.

What we agree before work starts

Your proposal sets out the work, responsibilities and commercial terms. Pricing is negotiable for each project.

Read how we work
  • Code and handover

    Define repository access, deliverables, usage rights and third-party licences in the agreement.

  • Data and confidentiality

    Agree access, confidentiality and hosting responsibilities before sharing production information.

  • Milestones and payments

    Set the project scope, review points, acceptance criteria and payment arrangements together.

  • Launch and support

    Agree launch responsibilities, handover and any support period and response expectations.