One catalog, synced instantly
Add a new product once. A price or tax change propagates immediately to every location where the product is active. No duplicate items, no parallel lists in Excel.
In a chain with multiple locations, goods are physically in different places — so stock must be owned by each store, on a shared catalog. What syncs instantly across all locations: the catalog (products, prices, taxes), transfer states, minimum-stock alerts, and the consolidated chain-wide dashboard. Physical movement between locations happens through transfers with access controlled by per-POS permissions (each employee limited to the stores they are responsible for), with a full log and goods in transit on a mobile POS (vehicle) until receipt is confirmed.
Products are defined once in the catalog. Each point of sale then has its own stock, may have its own prices and taxes suited to the zone (useful, for example, when combining a store with a HoReCa area).
Add a new product once. A price or tax change propagates immediately to every location where the product is active. No duplicate items, no parallel lists in Excel.
The cashier at Centru sells, the cashier at Botanica sells — without waiting for each other. Each location updates its own stock, and the consolidated chain-wide dashboard stays coherent.
The warehouse is modeled as a location with a logistics role — it does not sell to the end customer, it supplies the stores (or ships online orders directly). Goods receipts from suppliers come in here, transfers to stores go out from here.
The same product can have a different price at Centru vs. Bălți, or a different tax in a zone with a special tax regime. Configurable per location at onboarding.
The typical "send me 30 units" case — step by step, showing what each role sees and where the goods physically are at each moment.
The manager opens the Transfers screen, searches for the product, sees the stock available at each location and initiates the request: 30 units from Botanica to Riscani.
There is no manual "approval at source" step — access to initiating and accepting transfers is controlled through per-source / per-destination POS permissions. Every employee responsible for a POS can be limited to operate only with the store they are responsible for.
Stock is deducted at the source and loaded onto the mobile POS (the delivery vehicle, with its own stock and log). It can no longer be sold at the source or at the destination — you naturally see where it physically is.
On arrival, the destination manager confirms receipt → stock is deducted from the vehicle and added to the destination. If a quantity difference appears, a comment can be added to the log (optional, recommended for audit).
The whole process is logged: who initiated, who dispatched, who received, when (timestamp down to the second). History is immutable by design — it cannot be deleted or edited retroactively from the normal interface.
One vehicle can load at the warehouse for several stores and deliver sequentially, with partial transfers from the vehicle to each destination. At the end of the day you can see what is left on the vehicle.
The vehicle, truck or own courier is modeled as a mobile POS with dedicated stock and a separate log — exactly like any stationary location. Practical effects:
While goods are on the vehicle they cannot be sold at the source (they have left) and cannot be sold at the destination (they have not arrived). Three explicit values on the dashboard: "in my store", "on a vehicle toward me", "on a vehicle away from me".
If goods are missing at receipt, they are precisely located: on vehicle X, between dispatch and delivery. Every vehicle has its own shift report, its own independent audit.
At the end of the day you can see exactly what is left on the vehicle: transit balance, unloaded returns. Useful for reconciliation and for daily control of your own fleet.
Every active vehicle uses 1 POS slot from the package. A chain with 4 stores + 3 own vehicles = 7 slots used. At onboarding we size together how many slots you actually need.
Each product can have a minimum threshold per store — Coca-Cola at Centru can have a different threshold than at Botanica, because sales differ.
When a product's stock drops below threshold, the notification appears on the warehouse operator's dashboard and on the store manager's dashboard. Includes audio cue and browser push (included).
The warehouse operator sees the alerts and manually initiates the transfer to the store that needs it. That way quantity and priority can be adjusted to the real situation (Black Friday, season, promotion).
Issuing the transfer note automatically when the threshold is reached is not a standard delivered function — it is available on request, priced in support hours after we evaluate your rules (optimal quantity, priority, exclusions).
Telegram notifications are included in the package. Email, SMS and WhatsApp Business are quoted individually based on volume and sender account.
Roles are configured at onboarding, starting from standard presets (cashier, store manager, purchasing manager, accountant, director) and adjusted to your scenario. Each right can be limited to one or more locations.
A cashier sells at their own store; they do not see or modify another store's stock unless they are explicitly given that right.
A manager can be granted the right to initiate transfers only between two or three locations in their region — not across all 10 in the chain.
A view-only role across all consolidated reports, without operational rights. Useful for the owner or the network director.
A financial-scope role — sees consolidated invoices and reports, without access to sales operations or stock.
Presets are the starting point — any custom combination is built at onboarding, together with you. Every action is audited with user, timestamp and result.
We are transparent about what is standard delivered and what remains an individual case.
To "hold" goods for a corporate client, the current mechanism is issuing the e-Factura B2B invoice — the pending invoice appears in the list of unpaid invoices and can be tracked there, with the committed stock visible.
We do not have a dedicated function like "reserve 30 units for customer X for 7 days with automatic release". For sophisticated reservations (priority, queues, expiry) we discuss the case individually — this is not a standard product.
The retail-chain suite is optimized for a clear profile, so we can honestly tell you when you have outgrown it.
For chains with up to 10 locations and typical volumes of 5,000 to 20,000 stock movements per day, performance is sized in the Standard and Extra packages. Above the cap you can pay add-ons for additional POS locations (indicative, negotiated individually B2B) — or move up to the higher package when the accumulated add-ons match a larger package.
Changes to each location's stock happen independently — 5 cashiers at 5 different locations scan simultaneously, each receipt is issued in under 1 second, regardless of the load on the others.
For accurate per-location margin accounting, each transfer can carry a defined internal cost (logistics, personnel) that is added to the product price at the destination.
For larger chains or volumes above 20,000 movements/day, we discuss an offer in the Super or Enterprise packages, with individual sizing.
Yes. You get separate reports per location, but also a chain-wide total, with breakdown by location, category, and operator, plus comparison with the same day of the previous week or month. Export to CSV / XLS / XLSX for the accountant or the board.
The difference (less or more than on the transfer note) stays recorded in the log with user, timestamp and comment (optional, recommended for context). You can later filter transfers with differences for reconciliation or investigation.
Yes. The transfer can be initiated directly from one store to another (a "pull" workflow), without passing through the warehouse. Goods sit on the delivery vehicle as a mobile POS, exactly like any other movement between locations.
Not through the normal interface. All records are immutable by design — non-admin operators cannot edit history in any way. Correcting an incorrect transfer is discussed at onboarding as a specific operational flow — it is recorded separately in the log, and the audit trail stays complete (the trace of the mistake is not erased).
You have three configurable options: fulfilled from the warehouse (courier), fulfilled from the store (customer pickup), or fulfilled from the nearest location with stock. The source choice follows your policy, and the location operator receives the picking list.
Yes. A live dashboard with sales/hour per POS, aggregated figure vs. the average of the last 7 days, and an alert when a location drops below 40% of its own average. You do not wait for the next day's report.
The structures above reflect our standard offering, but every client is discussed individually. We adjust the scope (how many POS locations and active vehicles, how many warehouses, how many sites), the onboarding timelines, the role configurations and the alert thresholds based on your business. Custom services (migration from another system, developing the automatic transfer request, additional integrations) are priced in support hours after evaluation. The final binding offer is the one in the written quotation + the signed contract.
20 minutes on the phone: we tell you exactly which package fits the number of stores and active vehicles you have, how the warehouse is sized, and which transfer and alert rules we recommend. No obligation — just numbers and a diagram for your operation.
We look together for 20 minutes at your chain — number of locations, active vehicles, typical transfer volumes, alert rules. We evaluate whether SGApps fits and honestly tell you if a Super or Enterprise offer is warranted. The initial consultation is free.
SGAPPS LABS SRL · Chișinău, Moldova · Continuously in production since 2018 · POS · ERP · MEV fiscal register · Android fleet