Skip to content
2026 · Custom software
Multi-branch drugstore inventory. Sales, purchases, products, print. The shop-floor side of a pharmacy group.
Farmora
Client
PT Kem Kem Primahusada
Year
2026

Features

  • Several stores on one catalog
  • Products, customers, and vendors
  • Sales and purchases at the counter
  • Barcode on the product
  • Receipts on the shop printer
  • Separate logins per store

The drugstore app next to Prima. Prima is the distributor. Farmora is the toko obat side: products, customers, vendors, stores, users, sales, purchases. Same company group. Different counters.

What they needed

A distributor system does not help the person at the apotek counter. They need to sell, buy, print a receipt, and see the same product list as the other branch. Without fighting over whose spreadsheet is right.

What they got

One catalog across stores. Sales and purchases. Barcode. Print that hits the shop printer, not a “save as PDF” dance. Accounts so each store is not sharing one password.

This is the current inventory line. Operators get a screen they can stand in front of all day.

The cover is a stand-in until we drop live shots in.

If this is you

Several shops, one product list, printers that have to work. If your branches share a catalog and fight over stock numbers, this is the shape we are shipping now.

Developer notes

.NETC#Next.jsPostgreSQL

Next.js UI on a .NET API. SignalR when the screen needs to update live. Barcode and PDF on the client. A tray app and print agent so the shop printer is not a browser dialog. PostgreSQL.

Got something to ship?

Tell us what you run. A company site, search visibility, or a system that replaces the spreadsheet.