SKYEMBER

Work / Representative system

Business Operations Platform

Turning pharmacy operations into one connected workflow.

Industry
Pharmacy / Operations
Scope
Product · UX · Engineering
Platform
Web application
Status
Representative project

Business Operations Platform

Al-Noor · Gulshan counter

Live

Sales order

SO-10482

City Care Clinic · 4 Oct 2026

A. Rahman · counter

Processing

Rs 12,480

Payment confirmed

Panadol 500mg tablets

Qty 24 · Batch B-441 · Exp 08/2027 · Bin C-12

FEFO · earliest eligible batch

One web application for pharmacy operations: the order, the batch it may take, and the stock it holds.

The work is more complicated than the transaction.

A pharmacy order is not simply an item and a quantity. Custom software development for this kind of business software has to hold payment state, batch eligibility, stock reservation, fulfillment, and the people acting on the record — in one place, while the counter is still moving.

That is why the surface looks dense. The density is the work. Inventory workflows and FEFO rules are not decoration around a checkout form; they are the reason the record exists.

One order. Everything it depends on.

SO-10482 is the same sales order shown on the homepage proof — opened here so the dependencies stay attached to the document. Payment, stock, batch, and dispatch are not a separate architecture chart. They are why this line can move.

Document context

SO-10482

City Care Clinic · Panadol 500mg · Qty 24

  • Payment Confirmed
  • Stock 24 reserved
  • Batch B-441 · FEFO
  • Dispatch Waiting
  1. Order
  2. Payment
  3. Batch
  4. Reservation
  5. Fulfillment

Software engineering for a business workflow means keeping these links on the order, not scattering them across tools the counter cannot see together.

Designing around constraints.

The platform is shaped by rules the operation already has. The interface does not invent the physics of the pharmacy; it makes those rules legible while work is happening.

01

Batch selection

The system needs to know which inventory should move, not simply whether inventory exists. FEFO selects the earliest eligible batch that can fulfill the line.

02

Reservation

Reserved and available are different states. A confirmed order holds stock without pretending it has already left the bin.

03

Traceability

The order stays connected to its batch and activity history, so a later question about the line can be answered from the same record.

04

Workflow

Payment, checking, reservation, posting, and dispatch are different states. Software engineering here means making those stages explicit and visible.

The order is only one part of the system.

The homepage showed one operational record. Here the same record sits inside the wider platform — orders, inventory, purchasing, accounts, and activity sharing one product language.

Business Operations Platform

Operational system

  • Orders

    SO-10482 in progress at the counter

  • Inventory

    Batches, bins, and eligibility

  • Purchasing

    Receipts that replenish the same stock

  • Accounts

    Payment and posting to the ledger

  • Activity

    A history the next person can trust

Breadth without five separate products. The areas agree because they share the same operational record.

Designed around the work, not the software.

The interface is judged by whether a person at the counter can see the state of the work. Labels and layout follow the operation, not a generic admin template.

  • Clarity

    Complex operational state should be understandable at a glance.

  • Context

    A decision should carry the information needed to make it.

  • Continuity

    An action should remain traceable through the rest of the workflow.

Software that respects the workflow.

Before choosing screens, the model asks four questions. They keep custom software development honest when pharmacy operations refuse to fit a simple form.

  • State

    What stage is this work in?

  • Data

    What records does this action depend on?

  • Rules

    What constraints must hold?

  • Trace

    What happened, when, and by whom?

What the system is designed to make possible.

These are design intentions for the representative system — not measured outcomes from a published engagement.

  • Clearer workflow state across the counter and the back office
  • Traceable stock decisions tied to batch and expiry
  • Connected operational records instead of disconnected screens
  • Fewer handoffs that depend on memory alone

Project

Name
Business Operations Platform
Industry
Pharmacy / Operations
Scope
Product · UX · Engineering
Platform
Web application
Status
Representative system

Have a workflow this complicated?

Start a conversation