Walk through Codesloci ERP
8 of 12 screens are live in the demo. Everything else is visible but marked, with a reason — nothing is a dead link.
How to sign in
The demo has its own login because that is part of the product. These accounts are fictional, the passwords are deliberately fake, and each one sees a different slice of the platform — so it is worth signing in as more than one.
| Role | Password | What they can see | |
|---|---|---|---|
| Administrator | [email protected] | Admin@Demo | Everything, including delete and user management |
| Manager | [email protected] | Manager@Demo | Full catalogue and order write access, no deletes |
| Cashier | [email protected] | Cashier@Demo | Can transact on orders, cannot edit the catalogue |
| Staff | [email protected] | Staff@Demo | Read-only across every screen |
What to try first
- Open an order and walk its status forward — only the transitions the server accepts are offered.
- Cancel a confirmed order and watch the stock go back to the products it reserved.
- Try to cancel it a second time: the release is guarded, so stock cannot double-return.
- Sign in as Cashier, then Staff, and watch the write affordances disappear.
- Resize the window past 1024px and 600px — the rail collapses, then becomes a bottom bar.
Every screen, and whether it is in the demo
Grouped the way the real platform groups them. A screen marked not in the demo is still visible in the demo's navigation — clicking it explains why and offers a walkthrough, rather than doing nothing.
Sign in
Email and password over the seeded accounts, with the demo credentials listed on the card below the form exactly as the product lists them.
Settings
The signed-in account and its role, the theme control (system, light, dark) and the build information the product shows here.
Change password
On the real Settings screen, and it signs out every other session on success.
It needs the refresh-token store the API keeps server-side, so a browser-only mock cannot honestly show the part that matters — the other sessions being invalidated.Dashboard
One overview request backing the whole screen: stock and order summary tiles, an eighteen-month revenue trend, top products, and the low-stock queue.
Products
The catalogue with search, category and stock-state filters. Margin and stock value are computed from cost and selling price, never stored.
Product form
Create and edit, with the same validation the API applies. Cashier and Staff reach a read-only view because the server would reject their write.
Orders
Every order with its lifecycle status, payment status and balance due, filterable by both and sortable on each column.
Order detail
Lines, totals, payments and the status machine. Only the transitions the API allows from the current status are offered, and the stock release is shown as it happens.
New order
Pick a customer, add catalogue lines, and watch stock reserve on save. Totals are derived, not typed — the client sends product ids and quantities only.
Customers, suppliers, stores
Full CRUD resources on the API, reachable today only through it — the Flutter client has no screen for them yet.
Real API resources with no client screen yet. The dashboard reads customers to rank top spenders, which is why they appear there and nowhere else — the demo mirrors the client.Sales, purchases, returns
The other half of the stock lifecycle: purchases bring stock in, sales and returns move it out and back.
Implemented on the API and summarised on the dashboard, but not yet given screens in the client. Showing them here would misrepresent what the product does today.Categories, discounts, users
Supporting resources — the category tree products belong to, discount rules, and user administration.
API-only for now. Categories appear as a product field and a filter, which is the extent of the client’s coverage; user administration is gated to the admin role on the server.Good to know before you open it
- It runs entirely in your browser. There is no server, and nothing you type leaves the page.
- Your edits persist across a refresh, and Reset data in the demo bar puts the sample data back.
- A guided tour starts on your first visit and can be replayed from the demo bar.
- It works on a phone as well as a desktop.