Questions, answered.

POS is QGenx’s retail billing system. It handles barcode checkout, promotions, returns and loyalty at the counter, goods receiving in the store, and sales reporting for head office.

Retail stores and multi-store chains that bill by barcode and want counters, receiving and reporting connected. It suits apparel, footwear, lifestyle, supermarkets and similar formats.

No. A single store can start with the counter workflow. The company-and-store structure is there when you grow.

Yes. Companies, stores, employees and users are managed in one shared application with head-office views across stores. We do not claim every brand is a separate legal tenant.

No. It records sales, tax on receipts, returns and stock movement. It is not a general ledger or tax-filing tool.

Offline billing is not part of the current offer. Ask us in a demo about your connectivity and we will say plainly whether it fits.

It connects the counter to merchandise receiving, supplier returns, stock availability and head-office reports in the same system, instead of billing alone.

The cashier scans an item, and its price and tax come from the store catalogue. The bill builds up as items are scanned.

Yes. Measured quantities are supported for loose items.

Promotions are configured by head office. The bill calculates eligible offers automatically, and offers can be assigned to chosen stores.

Yes. A coupon can be applied to a bill and removed again before payment.

POS records how each bill was paid. It does not process card or UPI payments itself.

A return is linked to the original invoice. The resulting credit can be used on a later purchase.

Customers are identified by phone number and points accumulate against that number. You can view a customer’s purchases and points.

Merchandise is loaded per store, and a CSV maintenance route exists for bulk changes. Brand, department, size, colour and measured units are supported attributes.

A historical sales migration route exists. We scope it per project, because source data quality varies.

Users get roles, and menus are controlled by role, so a cashier sees the counter and head office sees reports.

Yes, tax and promotion rules have administration screens. Receipts show tax calculated from those rules.

POS holds a financial-year configuration so documents and stock periods line up with your accounting year.

Head office uploads a delivery file and prepares an advance shipping notice. The store then receives by scanning boxes and products.

Implementation takes between 7 and 20 days, depending on the product you choose. It depends on stores, catalogue size and data cleanliness. We pilot one store first and expand once the workflow holds.

Availability is computed from opening stock and every movement: receiving, sales, returns and supplier returns.

Yes. Counting sessions record scanned quantities. We do not currently offer automatic posting of a count into opening stock.

Supplier goods-return documents record the outward movement as a separate workflow, using the return pricing settings.

Sales summaries, the Sales Abstract, goods-movement reports and customer purchase and points views across stores.

A Telegram reporting component exposes predefined business reports, and scheduled email delivery exists. We confirm what is switched on for you during setup.

Yes. System administration includes activity history, so changes can be traced.

A supporting attendance component captures check-ins with location through Telegram. It is a supporting module, not the core of POS.

Book a 30-minute demo. We start with your store workflow and show the counter, receiving and reports on that basis.

Plans are Basic, Premium and Enterprise. We recommend one after understanding your stores and users. Ask us for details; we do not list prices on the website.

We can load a sample of your catalogue for the demo so you see your own items at the counter.

Support is available by email at support@qgenx.io and WhatsApp. Existing customers are routed to the support process.

Where two workflows benefit from shared data, such as product masters feeding the catalogue, we connect them deliberately, scoped per project.

We configure rules, masters, roles and reports first. Anything beyond that is scoped honestly, with the effort stated up front.

Hosting details are confirmed per project during the demo. See the Privacy Policy for how we handle data in general.

Stockify is QGenx’s warehouse and order-operations system: purchase receiving, customer bookings, stock holds, sales-order approval and pick preparation.

Distributors, wholesalers, brands with their own warehouse and fulfilment teams that receive by barcode and commit stock to customers before dispatch.

No. It does not replace accounting. It focuses on receiving, booking, holds, approval and picking.

Bookings and sales orders are created with the stock position in view, and holds and reservations keep promised quantities separate from free stock.

No. Stockify handles warehouse and order operations only.

Yes. Warehouse and storage-location setup is part of the product.

Receiving, approvals, holds and picks are recorded steps with owners, not cells anyone can overwrite.

A purchase uploaded from a file must be approved before it appears in the receiving queue.

The operator opens an approved purchase and scans products box by box. Each box is recorded against the receipt.

Shortage and excess are recorded against the purchase and shown in inward reconciliation reports.

A booking is the customer’s request. A sales order is a committed document created from it, and it goes through approval.

A proforma document holds its own stock so it can be offered to a customer without confirming a sale.

A deliberate action that reserves everything left on a booking. You can later convert or release it.

Yes. Customer-based order pricing is supported when bookings are created.

Through a validated bulk upload that checks the file before importing, plus a searchable catalogue with variants.

Bulk order booking accepts a file and creates bookings, using the same checks as manual entry.

You define warehouses and storage locations, and pick instructions reference them.

Yes. Users, roles and menus are managed, with session and login controls.

Billing, channel and supplier records, plus reference masters for business configuration.

Purchases are uploaded from a file and listed in a purchase register.

Implementation takes between 7 and 20 days, depending on the product you choose. It depends on catalogue size and locations. We start with one flow, usually receiving or booking, and widen after it works.

Availability and a shelf ledger show stock by product and by recorded location.

Counting sessions capture scans. They record observations and do not adjust the shelf ledger automatically.

Approved sales orders generate pick slips that reference shelf locations, which can be planned and printed.

Yes. A warehouse tracker shows the recorded stage of each document.

Operational reports can be exported to XLSX.

In-application notifications are included.

Packing and packed-quantity invoicing exist in the code but are not offered as finished capabilities. We will say when that changes.

Book a 30-minute demo. We use your receiving and booking flow as the example.

Basic, Premium or Enterprise, depending on warehouses, users and support needs. We discuss this after the demo; no prices are listed on the site.

We can load a sample of your products and a purchase for the demo.

Email support@qgenx.io or message us on WhatsApp.

The two can be connected where it removes work, such as store receiving against warehouse dispatch. This is scoped per project.

We configure first. Anything beyond configuration is scoped and priced openly before work starts.

Confirmed per project during the demo.

Stylify is QGenx’s product master data product. It holds styles, their barcode-level variants and the attributes that describe them.

The single, agreed record of each product: its style, variants, barcodes, prices and attributes, which other systems rely on.

Fashion, footwear and lifestyle teams and anyone with SKU-heavy ranges that live in spreadsheets today.

A style is the product as a design, for example a cotton shirt. Variants are its purchasable forms, such as each colour and size with its own barcode and MRP.

No. It is the product layer. Billing and checkout belong to POS and Billify.

No. It serves as the product master that other products and sheets draw from.

No. It stands alone, and connects to others only when that removes repeated work.

Yes. Attributes are configurable columns with their own values, and you can have many of them.

Choose a master colour and size group and the variants are generated, with barcodes following your rule.

Barcode and SKU identifiers follow settings you control, so they are generated rather than typed.

It is created automatically, so valid rows are not rejected for a missing list entry.

Yes. Products can stay in draft and be published when complete.

You can attach image URLs to styles and variants.

Tax code and unit of measure are held on the product and can be inferred during upload.

CSV and XLSX.

It reads the sheet, previews what will be created or updated, flags rows that fail, and shows progress on large files.

Yes. Uploads can create new records and update existing ones.

Company, stores and financial year, then attribute columns and values, then the products.

We map your columns to the style, variant and attribute structure, then upload a sample category to check it.

Yes. Users and roles control who can edit and who can only view.

Implementation takes between 7 and 20 days, depending on the product you choose. It depends on your attributes and the state of your data. A single category is the usual first step.

Search the catalogue by style or variant and filter by attributes.

Variants carry a status, and visibility can be controlled so inactive variants stay out of use.

Yes. Product and variant data can be exported to XLSX.

Authentication, sessions and administration features are included; we confirm audit detail during the demo.

Valid rows continue and the bad ones are flagged so they can be fixed and re-uploaded.

Access is by role, so stores can be given read access only.

Yes. Listify reads product data for marketplace files; this connection is scoped per project.

Book a 30-minute demo and send us a sample of your product sheet if you can.

Basic, Premium or Enterprise, depending on the size of the range and the number of users. We do not list prices on the site.

Yes, if you share a sample beforehand we can preview it in the upload screen.

Email support@qgenx.io or message us on WhatsApp.

Yes, where a shared product master removes repeated entry. It is scoped per project.

Attributes are configurable by you. Other changes are scoped openly.

Confirmed per project in the demo.

Billify is QGenx’s invoicing product for client-based billing: saved clients and services, draft and confirmed invoices, branded print, and billing and GST reports.

Service businesses, agencies, consultants and any team that issues itemised GST invoices to a set of clients.

No. It prepares invoices, registers and reports. It is not a general ledger.

The catalogue holds products and services, with fields suited to service billing such as service group and billing model.

No. There are no stock quantities in Billify.

Billify works in a company context with its own profile, tax settings and financial year.

No. Billify stands alone.

A draft can be edited or discarded. Confirming allocates the invoice number and fixes the document.

The invoice carries a GST breakdown, rounding is applied, and tax settings are configured in a tax master. Reports cover GST and HSN.

Yes. Copying creates a new draft with the same lines and terms and resets the document-level details.

Yes. Reusable terms can be saved and attached to invoices.

Print it or save a PDF from the browser using the branded layout.

Yes. Manual payment receipts attach to an invoice, with a receipt register and payment reports.

A schedule screen exists for source-invoice schedules, but automatic recurring generation is not promised yet.

Company profile, tax settings, financial year, clients, the service catalogue and your terms.

We load client and catalogue data for you during setup; confirm the format with us in the demo.

You configure numbering, and a number is allocated when you confirm the invoice.

Yes. The company profile sets the document identity, and invoices print in a branded layout.

Yes. Authentication, sessions and access controls are part of the product.

Billify holds a financial-year context for documents and reports.

Implementation takes between 7 and 20 days, depending on the product you choose. Usually short, because it is masters plus a template. Timing depends on how much client data you bring.

Use the invoice register with search and filters.

Yes. A cancellation action exists for confirmed invoices.

Billing, GST, HSN and payment reports, plus a dashboard overview.

Not automatically. Manual receipts and payment reports exist, but overdue tracking and a reconciled receivables ledger are not offered yet.

Reports can be filtered; we confirm export formats during the demo.

Tax settings are configurable in the tax master.

Yes, a billing overview.

Book a 30-minute demo. We use your own invoice layout as the example.

Basic, Premium or Enterprise depending on users and support. We do not list prices on the site.

The company profile controls document identity; we check how close we can match in the demo.

Email support@qgenx.io or message us on WhatsApp.

Not out of the box. Integrations are scoped per project.

We configure first; anything beyond that is scoped openly.

Confirmed per project during the demo.

Listify is QGenx’s marketplace catalogue product. It reads marketplace templates, maps your product fields to their columns and generates catalogue files.

No. It generates files you upload on the marketplace portal. There is no marketplace API publishing.

Flipkart, Amazon and Myntra templates are parsed, and other spreadsheet templates can be mapped using the same mapper. Ask us about a specific one.

Ecommerce brands, D2C labels, catalogue teams and agencies preparing marketplace uploads.

Yes, or load them from a sheet. Listify generates files from the product data it holds.

The attribute set is rich for apparel, but any product with a spreadsheet template can use the mapper.

Stylify is the product master. Listify turns product data into marketplace files. They can share data.

You upload the marketplace’s Excel template and Listify reads its columns, mandatory fields and allowed values.

Connecting each marketplace column to one of your fields, with coverage showing what is still unmapped.

Yes. Value lists can be mapped, for example your colour names to theirs.

Choose a master colour and size group and the variants are generated.

No. They are optional and only work where an AI endpoint is configured. Review them before use.

You can attach image URLs to products and include them in the file.

It has draft status and validation of fields so incomplete products stay out of the file.

From a CSV or sheet, or by authoring styles and variants in the tool.

Set up the marketplace and category, upload its template, and map the fields.

No. Mappings are saved and reused.

As many as you need. The system was built around a very large attribute set for fashion.

Yes. Users, roles and navigation administration are included.

Through identifier settings, so variants get generated codes.

Implementation takes between 7 and 20 days, depending on the product you choose. We start with one marketplace and one category, then widen once the file is accepted.

Pick products and a marketplace, and run an export job. It shows progress and keeps the file.

Yes. Export jobs and history are kept.

Fix the field or the mapping and regenerate. The mapping is saved for next time.

Yes, using bulk style and SKU maintenance.

No. Listify handles catalogue data only.

Yes, through draft status.

The report describes audit logging for catalogue changes. We confirm the depth in the demo.

Book a 30-minute demo. Send us the marketplace template you use and we will map it live.

Basic, Premium or Enterprise, depending on marketplaces and users. No prices are listed on the site.

Yes, if you send it ahead.

Email support@qgenx.io or message us on WhatsApp.

It can read product data from the same master. Scoped per project.

Template mapping is configuration. Anything else is scoped openly.

Confirmed per project in the demo.

Assetify is QGenx’s physical-asset register. Each asset gets a QR-based and barcode-based identifier, with photographs and a named owner.

Hospitals and other site-based organisations that need an asset register with ownership. It also suits any team with physical assets.

Start with one location as a pilot, then add the rest.

No. It is a register and ownership record, not a maintenance, procurement or accounting system.

Yes. Company, Department and Doctor are supported owner types, and doctors need not be application users.

No. It records captures and ownership changes; it does not track location live.

It is browser-based, so capture works from a device with a browser. We confirm hardware in the demo.

Scan the QR code or barcode, complete the template, add photographs and assign an owner. All are saved together.

One to six per asset.

They are generated automatically with a company and location prefix.

Yes. An initial ownership record is created and later changes are retained.

Yes, through configurable templates and controlled master lists.

Yes. Records and details can be updated after capture.

Operational reports with CSV downloads, and a capture dashboard.

Company and locations, then templates and master lists, then users and roles.

Assign each user a location. We note that some read paths do not yet deny access consistently when a non-admin user has no location, so we set locations for all users.

Existing lists can be brought in through a scoped migration. Confirm format in the demo.

Roles with per-user permission overrides, and database-driven navigation.

Each asset needs a QR code or barcode at capture. We can discuss labelling in the demo.

In entity directories you maintain.

Implementation takes between 7 and 20 days, depending on the product you choose. Setup of templates and a location is usually short; the capture effort depends on the number of assets.

Search the register and open the asset’s detail view.

Reassign the asset. The previous owner stays in the history.

In-app operational notifications are included.

The dashboard shows capture and ownership coverage by role.

Yes, CSV reports can be downloaded.

Access follows roles and individual permission overrides.

Login and session controls are part of the product.

Book a 30-minute demo. We can set up a template for your asset type beforehand.

Basic, Premium or Enterprise, based on locations and users. We do not list prices on the site.

Yes, and we recommend it.

Email support@qgenx.io or message us on WhatsApp.

Possible where it removes work. Scoped per project.

Templates are configuration you control. We help set them up.

Confirmed per project in the demo.

StoreX is QGenx’s retail operations system. It has Online Operations for channel orders and packing, and Store Operations for store supply and reconciliation.

They solve different problems and use different stock structures. We keep them separate so each stays clear.

No. It is a back office for orders you already receive, not a storefront.

Orders come in by CSV. Direct marketplace API connection is not part of the current offer.

No. It reconciles retail quantities and creates credit and debit notes, but it is not a ledger.

Brands with online channels, warehouses and stores that need packing, supply and reconciliation to line up.

Their stock structures are separate. Automatic synchronisation between them is not offered.

Packers verify by tracking number or product barcode, and can reprint a label.

Groups of imported orders that move through allocation and packing together.

Uploaded PDFs are mapped to the shipment, and manifests can be printed.

Returns are registered and the product is verified by barcode.

A store-supply route where scanning goods into boxes updates the order, pickslip and packing records together.

It matches provisional retail sales with final month-end files and produces store-level credit and debit notes.

Yes. Employee records, manual attendance and a Telegram check-in feed attendance reports.

From a CSV. Historical order loading also exists.

Channel products must map to warehouse products so orders resolve.

Through business, store and supplier setup and a warehouse layout.

Yes, with CSV and image-link maintenance for styles and variants.

Users and roles control menus, with session checks.

Current and month-end retail sales files, plus invoices.

Implementation takes between 7 and 20 days, depending on the product you choose. We pilot one track and one channel first, then widen.

Independent scan registers and scan activity monitoring are included.

Physical counting records observations without automatic reconciliation.

Yes, as workbooks.

Online sales pivots and period comparisons, stock-to-sales and movement analysis, store stock and sell-through reports.

Invoice-linked stock discrepancy adjustments are supported on the store track.

Yes. Milestones are tracked manually through the supply process.

Live courier tracking is a placeholder and is not offered.

Book a 30-minute demo. Tell us whether online packing or store supply matters first.

Basic, Premium or Enterprise depending on channels, stores and users. We do not list prices on the site.

Yes, send a sample CSV beforehand.

Email support@qgenx.io or message us on WhatsApp.

They can be connected where it removes work. Scoped per project.

We configure first and scope anything beyond that openly.

Confirmed per project in the demo.

Prism is QGenx’s retail and ecommerce reporting product: pivots, comparisons and merchandise views built on data you record or import.

Analysts, merchandisers, channel managers and owners who review trading performance, especially in apparel.

It analyses data that has been imported or recorded. It is not a live checkout system.

It is purpose-built for retail and ecommerce questions, so common views are ready. It does not claim to replace general tools for every use.

No. It works from imported data, and can use data from any source in the right format.

No. It reports on what has happened, with comparisons and gaps.

Style, colour, size, fabric and season make it strongest for apparel, but the pivots work for other retail.

Store, brand, category, period and other attributes, with comparisons between periods.

Stock-to-sale and cover for products and groups.

It shows margin movement and the impact of markdowns together.

It points out where size runs are broken and where refilling is needed.

Yes. Merchandise ranking and internal comparisons are included.

Channel sales, return risk and ageing, and assortment and stock review.

Yes. Reports and datasets download as files.

By CSV imports for trading data: sales, returns and stock.

Products, stores, sales and stock at least. Returns improve return and ageing views.

Yes. Attributes and identifier settings are configurable.

Yes, marketplace and category setup is included for ecommerce views.

Through users, roles and navigation administration.

Implementation takes between 7 and 20 days, depending on the product you choose. We load one month and prove the numbers against your own reports first.

It helps. We review a sample and advise before import.

As often as you review, such as daily or weekly. It depends on your file process.

No. Retail and ecommerce reporting use separate data and are not reconciled automatically.

Yes, using pivots and productivity and space-efficiency views.

Yes, in the ecommerce return risk and ageing view.

We list only verified views. Some inherited screens use simulated figures and are not offered.

Reports and datasets can be downloaded and shared; access is by role.

Yes, datasets download as files.

Book a 30-minute demo and send a sample of your sales file if you can.

Basic, Premium or Enterprise depending on data volume and users. We do not list prices on the site.

Yes, with a sample you are comfortable sharing.

Email support@qgenx.io or message us on WhatsApp.

Where a shared data path removes work, we scope it per project.

We configure existing views first. New reports are scoped openly.

Confirmed per project in the demo.

Eight focused business products covering retail billing, warehouses, product master data, invoicing, marketplace catalogues, physical assets, retail operations and business intelligence.

No. Each product stands alone. Start with the workflow causing the most friction and add another only when it removes real work.

Bring one workflow to a demo. We will point to the product closest to the problem rather than sell the whole family.

Implementation takes between 7 and 20 days, depending on the product you choose. We work in seven stages and pilot with a small group before rollout.

Where two workflows benefit from shared data, they can be connected deliberately. This is scoped per project rather than assumed.

Access control, roles and sessions are part of the products. Hosting and security details are confirmed per project during the demo.

GST-aware billing and reporting are available where relevant, mainly in POS and Billify.

Use the Book a Demo page, choose the products you care about and a convenient time. You can also message us on WhatsApp.