Can I buy just the POS, or just the accounting?

Modules are entitled per workspace rather than sold as separate products, and the published plans bundle them in sets. In practice that means the entry plan is a commerce and till plan without full accounting, and accounting arrives on the tier above. The pricing page prints which modules sit at which tier.

How many modules are there?

The platform entitles 31 modules that have a backing service shipping in this build, of which 19 are written up in depth on the features page. Four have their own page here, chosen because they are the four things Bangladeshi buyers actually search for.

Why do these pages list things the product cannot do?

Because the alternative is a demo that wastes a morning. Every capability entry carries a limit as well as a claim, written from the shipped code, and the limit is rendered at the same size as the claim rather than as a footnote.

How current are these claims?

The shipped code behind them was read on 2026-08-19, and that date is printed here and at the top of each page. If a page says something is not built and it now is, the page is stale and we would rather hear about it.

Modules

The modules, written from the shipped code

Name: BizRP
Price: 1990 BDT
Availability: InStock

Point of sale, inventory, accounting and the Mushak registers, each described with what it does and where it stops. Written against the code rather than the roadmap, with the date it was read printed on the page.

Reviewed 19 August 2026

The short answer

Four modules are covered in depth here: the till, stock, accounting and VAT. Each page lists its capabilities with a limit attached to every entry that has one, written by reading the shipped code rather than the roadmap.

The platform entitles 31 modules in total with a backing service. The rest are on the features page, which is a better read than a landing page that repeats it at greater length.

How these pages are written

Every capability claim on these pages comes from one module in this site's source, written by reading the shipped code, and every entry in it carries a limit as well as a claim. The limit is rendered in the same reading column at the same size as the claim, not as fine print, because a buyer who meets the limit in the demo instead of on the page is a buyer we have spent money to annoy.

The code behind these entries was last read on 2026-08-19. Where something is not built, the page says so in the same voice it uses for the things that are.

The modules covered in depth

Module pages published so far, with how many entries carry a limit
Module	What it covers	Entries with a limit
POS	Any phone is a till. Camera scanning, split payment, shift reconciliation, and offline behaviour explained in full.	2 of 11
Inventory	Typed warehouses in a hierarchy, transfers with stock in transit, batch and expiry, movements that post to the ledger.	0 of 8
Accounting	July to June fiscal year, period locks, deduction at source on supplier payments, Bengali digits on prints.	1 of 7
VAT and Mushak	Three Mushak artefacts produced, three not, named in a list with nothing implied.	3 of 6

That last column is the useful one. A module page with nothing in it is a module page nobody checked.

The rest of the platform

The platform entitles 31 modules with a backing service, of which 19 are written up on the features page. Rather than publish thin pages for the rest, here is what they are, with the features page as the place to read about them.

Manufacturing
Assets
Projects & Timesheets
Quality Management
Sales
Procurement
CRM
HRMS
E-commerce + Storefront Builder
Support
Billing / Subscriptions
Catalog (Products, Brands, Categories, Attributes)
Media / DAM
Settings
Reports / BI
Integrations module

If one of those is the reason you are here, the features page covers it and we would rather point you there than write a landing page that repeats it at greater length.

The argument for buying these together

Every one of these modules is available as a standalone product from somebody in this market, and several of those standalone products are better at their one job than we are. The argument for a single system is not that each part is best. It is that the joins do not leak.

The sale at the till deducts from the same stock the purchase order filled.
The stock movement posts to the same ledger the bank reconciliation runs against.
The Mushak register the counter feeds is the register the VAT return figure is computed from.
The item the till scanned is the catalogue record the storefront sells.

Each of those joins is a place where two separate products need somebody to export, import and reconcile. Count the hours that currently costs you. That number, and not the feature list, is what decides whether one system is worth it.

Questions people ask

Can I buy just the POS, or just the accounting?: Modules are entitled per workspace rather than sold as separate products, and the published plans bundle them in sets. In practice that means the entry plan is a commerce and till plan without full accounting, and accounting arrives on the tier above. The pricing page prints which modules sit at which tier.
How many modules are there?: The platform entitles 31 modules that have a backing service shipping in this build, of which 19 are written up in depth on the features page. Four have their own page here, chosen because they are the four things Bangladeshi buyers actually search for.
Why do these pages list things the product cannot do?: Because the alternative is a demo that wastes a morning. Every capability entry carries a limit as well as a claim, written from the shipped code, and the limit is rendered at the same size as the claim rather than as a footnote.
How current are these claims?: The shipped code behind them was read on 2026-08-19, and that date is printed here and at the top of each page. If a page says something is not built and it now is, the page is stale and we would rather hear about it.