Frequently asked questions

ulostock is a multi-branch inventory management system for product-based businesses. It tracks stock by batch, expiry, variant and branch; records POS, invoice and credit sales; manages purchase orders and supplier payments; handles returns; logs expenses; and reports on all of it. Each business gets its own isolated workspace.

Pharmacies and dispensaries, distributors and wholesalers, retail shops and supermarkets, electronics and device dealers, apparel retailers, and any multi-branch business that needs stock counts that are correct in more than one place.

No. ulostock runs in the browser. There is nothing to install and nothing to keep updated, and your team reaches the same data from any device they sign in on.

Sign up, set up your business profile and branches, add your products — individually or by bulk upload — and start recording transactions. Every plan begins with a free trial.

Yes. Products and inventory can both be uploaded in bulk, and the upload is validated before anything is created, so a malformed file is reported rather than half-imported.

Yes. Stock is held per intake rather than per product, so each intake carries its own batch number, expiry date, purchase price and quantity. Items approaching expiry are flagged on the dashboard within a window you configure, and listed in the inventory report.

Yes. Pack-size conversions are defined per product — one carton to twelve packs, one pack to ten pieces — so you can receive stock in one unit, hold it in another and sell it in a third. The conversion can be global to a unit or specific to a product.

Yes. Mark a product as carrying asset identifiers and each physical unit is recorded individually by serial number or IMEI, with its own status and branch. The identifier follows the unit from the purchase order that received it, through any stock transfer, to the sale that sold it and any return that brought it back.

Yes. Products can carry variant options such as colour, size or material with their own values, and the specific combination is recorded on the purchase order item, the inventory, the sale item and the return — so each variant is counted separately, per branch.

Each product can carry its own reorder threshold, falling back to your account default. Anything below it is flagged on the dashboard and in the inventory report, per branch.

Yes. Intakes, sales, adjustments and transfers are written to an inventory movement history you can read back per product and per branch, so a discrepancy has a trail.

Yes — invoicing is a core part of it, not an add-on. Invoice numbers are generated automatically in your own sequence, and an invoice can carry a discount, VAT at your default rate or one you set for that sale, and a shipping amount, with the total resolving as you build it.

Yes. Payments are recorded against the invoice they settle, as many as it takes, each with its own method, date, optional receipt and notes. The invoice moves from not paid to partially paid to paid on its own as they land.

Yes. An order invoice tracks fulfilment separately from payment, so an order that has been paid for but only part-supplied is distinguishable from one that has been supplied but not paid for.

Yes. Set a default tax rate for your business and it applies to new sales, and you can override it on an individual sale. The tax amount is calculated on the total after discount and held on the sale.

Nine: cash, bank transfer, credit, cheque, debit card, credit card, mobile money, POS terminal and online payment. The sales report breaks takings down by method.

Yes. A credit invoice is its own sale type, and payments are recorded against the invoice as they come in. Each invoice carries a status of not paid, partially paid or paid, so the receivables position stays current without a separate ledger.

Yes. Whether invoices can be changed after creation, and whether line-item prices can be edited during a sale, are both business settings — so a shop that wants invoices immutable can have that, and one that needs corrections can allow it.

Yes. A purchase order can sit in a partially-received state with the received quantity recorded per item, and the outstanding balance stays visible on the order until the rest arrives.

A return is processed against the original sale, item by item, with the batches, variants and serial identifiers that went out. Returned stock is restored to inventory automatically, and the return is kept as its own record rather than editing the sale away.

Yes. Each branch keeps its own inventory, sales and staff assignments, a user assigned to several switches between them without signing out, and stock moves between them as a tracked transfer that can require approval. Every report can be read per branch or consolidated. How many branches you get depends on your plan.

Purchase orders, sales, stock transfers, expense records, expense requests, invoice payments and purchase order payments. You configure which need approval and the steps they pass through; approvers approve or reject, and whoever raised a request can recall it before it lands.

They can delegate their approval authority to another user and revoke it on return. Delegations are recorded rather than informal, so a week away does not stall a week of purchase orders.

Roles are built from fine-grained permissions across every area of the system — staff, products, inventory, purchasing, sales, returns, transfers, expenses, reports, dashboard and workflow. Someone can record a sale without being able to delete one, or see stock without seeing margins.

Financial, sales, purchase and inventory reports, plus a P&L statement, P&L per product, daily sales, an inventory analysis and a products-without-inventory list. Each can be filtered by today, the last 7, 30 or 90 days, or dates you choose, for one branch or across all of them.

Yes. Reports download as PDF or Excel.

Yes. Purchase prices and sale prices are held per intake, so the P&L-per-product report shows what each line actually returned rather than a blended average across everything you ever bought.

Yes. ulostock is multi-tenant: every business gets an isolated workspace with its own data, users and configuration, and records are scoped to the tenant that owns them at the data layer.

Whatever your roles allow. Access is enforced per permission across every area, and staff are scoped to the branches they are assigned to.

Yes. Records carry who created and last changed them, product changes are logged, and every approval keeps its own trail.

Yes. Every report exports to PDF or Excel, and your raw data can be requested at any time. Your data belongs to you.