This is where the office does its daily work. Stock, sales, purchasing, finance, e-documents, CRM, POS and definitions sit in one tab, on one database. You enter documents, scan lists, and set who sees what.
A record entered on mobile in the field and an order a dealer places on the portal both end up here. Different screens, one record.
Who is it for?
Accounting and finance, sales operations, purchasing, warehouse planning and customer service teams do their daily work here, and company managers check the state of the day on the same screens. IT sets up users, roles and company definitions; each team works in its own documents and lists.
With branch- and warehouse-level permissions you can run several locations in one account. Decisions, definitions and most approvals stay on the web; mobile and B2B fill in around it.
What does it do?
You open product cards and check stock movements. You turn a quote into an order, the order into a delivery note, the delivery note into an invoice. You place purchase orders, follow cash and bank movements, and send e-invoices and e-despatch notes from the same place. POS and CRM records live in the same account.
Lists update as records are saved. On the dashboard, low stock, open orders, late collections and pending e-documents sit side by side, so you read the day from records instead of guesses.
Why does the data stay in one place?
Stock that leaves the warehouse leaves it on the delivery note and the collection too, because it is one record. A B2B order goes straight into the web sales queue. A stock movement made on a warehouse phone shows up in the web list. The integration agent writes data from your existing system into the same records, so nobody keeps a second spreadsheet.
Key capabilities
Stock and warehouse
Product cards, barcodes, units, warehouses and stock movements. Counts, transfers and low-stock alerts. In multi-warehouse setups, permissions decide which branch sees what.
Sales and purchasing
Sales runs quote, order, delivery note, invoice. Purchasing runs request, order, goods receipt. Supplier invoices connect to finance.
Finance and e-documents
Cash, bank, collections and payments are handled here. e-Invoice, e-Archive and e-Despatch go out from the same place, and you see a document's status next to the document.
CRM, POS and definitions
CRM from lead to opportunity, POS for retail, cafe and restaurant, and shared definitions for accounts, prices, units and tax. You enter a definition once and every module uses it. Company, branch, warehouse, user and permission setup also happens here.
Dashboard
Arrange the panels your way and put stock, sales and finance summaries side by side.
A typical workday
In the morning someone checks open orders and critical stock on the dashboard. Sales approves quotes, the warehouse prepares delivery notes. Finance posts collections and someone scans the e-document queue. In the afternoon management looks at sales and collections by branch. At close, the day's movements agree across the lists, since they were all written to one database.
That replaces the morning ritual of merging spreadsheets. Work does not slow down; you just stop hunting for where things are.
Relationship to other products
- Mobile: Field and warehouse entries write to the same database.
- B2B Portal: Dealer orders arrive in the web sales and stock process.
- Integration: Data from Mikro and Logo shows up in the records Platform Web displays.
Mobile, B2B and integration work at the edges. Platform Web is the center.
Security and permissions
Accounts are isolated from each other. Screen and document access follows roles and permissions, and data access follows branch and warehouse scope. It is wise to separate who can do finance and e-document actions. Adding users, changing roles and offboarding are handled here between IT and the business.
Where to start
Most setups open with Platform Web: company and definitions, stock, sales and finance modules, users. Mobile, B2B or integration are added as the need appears. Only what you license is switched on.
For the first step, set up definitions and the organization structure, then run one process end to end, for example stock, sales, e-document. Decide in advance when the old spreadsheet stops being used; otherwise two sets of records survive.
FAQ
Is Platform Web enough on its own? Many businesses start with it alone. Mobile comes when the field grows, B2B when the dealer channel grows, Integration when an existing system stays.
Do I have to take every module? No. Starting with stock and sales and opening e-documents and finance later is common.
Is e-document a separate product? No. It belongs to the module family and is managed from Platform Web.
Where are the reports? Dashboards and lists are on Platform Web. See Reporting for details.
How do we handle many branches and warehouses? Define company, branch, warehouse and permissions up front. Users only see their own scope, which also cuts down on sales from the wrong warehouse.
Next step
Try it free, or talk to the team and work out together which modules you need.