BudayrOS Frequently Asked Questions

A cloud operating system for pharmacy businesses that connects sales, purchasing, inventory, branches, warehouses, finance, reports, attendance, and access control in one working environment.

Create an account and organization, choose the operating country, complete the organization setup guide, add sites and users or import starting data, then open BudayrOS.

The country determines the organization currency, subscription profile, and available local defaults. Choose the country where the organization actually operates.

Yes. English and Arabic can be switched from public pages and the account page, and the preference is saved for signed-in users.

The Organization Owner is the primary subscription and billing owner. Organization Admin has broad operational and user-management authority inside the organization, subject to BudayrOS rules.

Open Users & Access, create the user, choose the role, assign operational pharmacies/warehouses, then grant only the functional permissions needed.

No. The user must have Purchasing permission and operational access to the receiving site. An organization-owned site outside the user's scope is not a valid destination.

Operational access remains site-scoped. Workflows that need limited visibility into another site, such as requesting a branch transfer, should expose only what is necessary without granting general operating access.

Yes. Site access can include multiple locations and is separate from functional permissions such as Sales, Purchasing, Inventory, or Reports.

The Organization Owner, Organization Admin, or a user with permitted user-management authority can manage organization users within the security rules.

The Organization Owner opens Account & Subscription and selects additional authorized payers. Those users can then see subscription pricing and the payment action.

Yes, when a valid minor-unit configuration exists for the product. Purchasing and wholesale remain whole-unit workflows under the current operating policy.

Sellable stock is separated from Expired / Quarantine, and sales availability checks eligible batches and sellable internal locations rather than relying on total internal quantity.

Use Customer Return, select the relevant pharmacy/shift, enter items and quantities, and choose the applicable settlement. Stock is returned according to batch and state rules.

A customer credit/voucher that can arise from supported return scenarios and remains traceable until it is used or otherwise resolved.

Yes when enabled for the organization. The Organization Owner can configure earning and redemption rules from the account page.

It groups POS operations into a controlled working period and supports financial closing, review, and shift-based reporting.

A Purchase Order records what you intend to buy. A Purchase Receipt records what was actually received into an authorized pharmacy or warehouse and posts stock/financial effects when completed.

Yes, if the user has Purchasing permission and operational access to that warehouse.

Enter the relevant batch and expiry details when receiving tracked products. They are then used by availability, expiry reporting, transfers, and traceability.

Use Supplier Return from an authorized site, choose the supplier, items, quantities and batches, then post after review.

Yes. Low Stock / Reorder surfaces products that need replenishment according to available stock configuration and the user's scope.

Sellable stock can be used in normal sales. Expired / Quarantine is restricted internal stock and is excluded from sellable availability while remaining traceable.

If the quantity leaves the source Expired / Quarantine location, it arrives in the destination Expired / Quarantine location instead of becoming sellable.

To avoid an ambiguous source. Move the quantity you want into one internal location first, or perform separate movements by actual source.

Use it for legitimate stock corrections, stock counts, or opening balances. Record the reason, site, quantity and batch where applicable.

Use it when stock is consumed internally rather than sold. Minor-unit consumption is supported without forcing users to type fractional major-unit quantities.

Use the Expiry Report and the desired date horizon. The Operations Dashboard also shows an expiring-soon indicator for users with reporting access.

Create a Branch Stock Transfer, choose source/destination, product, quantity and batch where needed, then progress through dispatch/receipt according to permissions.

Yes. Relevant transfer records expose the internal source so you can distinguish Sellable, Expired / Quarantine, or another internal location.

Use the transfer workflow that matches the source and destination types. Each applies the appropriate site-access and stock-location rules.

No under the current policy. Minor units are for retail/customer sales; wholesale uses whole configured units.

Yes. Wholesale Return reverses the relevant wholesale stock movement within the user's authorized scope.

Financial accounts, supplier accounts, cash expenses, supplier payments, account transfers and transaction history, subject to user permissions.

No. Cost/profit visibility is a separate permission so operational sales and stock access can be granted without exposing sensitive margin data.

Yes. VAT-aware transactions and reports stay connected to sales and purchasing, with local settings depending on the organization's country profile.

The user needs Supplier Payments permission and access to the relevant account/site. Record the payment, choose the financial account/method and amount, then review the resulting transaction.

Use Account Transfers if you have permission. BudayrOS enforces organization/site scope and serializes balance changes to reduce conflicting updates.

Employees check in and later check out. If a shift crosses midnight, the full duration is attributed to the check-in day in attendance reporting.

Yes, for users with the required attendance/report permissions.

Sales, purchases, product movement, expiry, returns, VAT, attendance, and additional operational reports depending on permissions.

Yes for sensitive operations, allowing management to review who performed important actions and when within the organization.

15 complete days from the exact moment the organization is created under the current subscription policy.

The successful payment adds a full subscription period after any unused trial or paid time, according to the organization's country subscription profile.

Under the current pricing model, users are unlimited and not billed separately; pricing is based on the organization and active sites defined by the country profile.

No. Archived sites are excluded from active-site pricing under the current model.

They should not. Tenant isolation and site-scoped rules keep operational data within the user's organization and authorized scope.

The role, functional permission, or operational site scope is probably different. Ask an Organization Admin to review Users & Access.

A site outside your operational scope is intentionally unavailable for actions that require access to that site.

The quantity may be in Expired / Quarantine, split across internal locations, or held in a batch that is not eligible for the operation. Review Stock Balance and the actual batch location.

Pricing and payment are shown only to the Organization Owner and users explicitly authorized to pay.

Open the BudayrOS User Guide, then choose the task from the table of contents or search within the guide.