Overall health
Yusuf only
User passwords
Choose a company, outlet and user, then choose a password reset or a one-time support login.
Choose a user
The selected user applies to both actions below.
Choose a company to see its users.
Reset the user's password
This replaces their password and signs out existing sessions. The user must create a new password before opening POS or Back Office.
Copy this temporary password now
Shown once. Share it privately with the selected user. They must replace it immediately after signing in.
One-time support login
Sign in as the selected user to debug their POS or Back Office. Their actual password and existing sessions stay unchanged. No password change or account-owner notification is triggered.
Choose a user above to generate a support login.
Copy this one-time login password now
Use the sign-in identifier above and this code in the normal login password field. It can be used once. Generating another code replaces any unused code for this user.
The code expires after 10 minutes. The support session lasts up to one hour and ends when this Yusuf console session signs out or expires. Access stays within the user's permissions. Issuance, login and audited actions are recorded internally.
Yusuf only
Companies & outlets
Delete an outlet and its dependent data, or a company and every outlet in it.
Choose exactly what to delete
Deletion is permanent. Review the dependency counts and type the exact confirmation phrase. A private recovery backup is retained for seven days. China Fish is protected.
An outlet deletion retains company-wide members, wallets, staff and settings. Shared users of another company keep their access there. Provider administrators are retained.
System pulse
Infrastructure overview
One screen for Node.js, the HTTP server, SQLite, memory, event-loop latency, and recent failures.
Node.js process
Runtime resources
Heap memory—
System memory—
CPU since refresh—
Responsiveness
Event loop latency
Persistence
SQLite health
—health-check response
—
Runtime history
Node events
No runtime events yet.
Trace every request
API request logs
Filter by failure, timestamp, method, status, route, IP, user, error, function, or source file.
Loading request logs…
Now on the system
Live access
Active HTTP work, recent IPs, authenticated users, open application sessions, and what each visitor is accessing.
In flight
Active requests
Network presence
Active IPs · 15 min
Identity presence
Active users · 15 min
Authenticated
Open POS sessions
Request stream
Latest access
Traffic intelligence
Landing & access analytics
Request volume, landing-page interest, regions, devices, endpoints, latency, and failure patterns.
Requests over time
Traffic and failures
RequestsFailuresLanding views
Geography
Regions
Region is read from trusted proxy geography headers; direct/private traffic is marked Local or Unknown.
Clients
Device mix
Responses
Status distribution
Marketing
Landing pages
Application surface
Most-used endpoints
Company service billing
Subscriptions
Manage Basic and Pro packages, outlet coverage, value-added services, service periods, and verified offline payments for every company.
Official catalogue
Basic, Pro, and value-added services
Loading service catalogue…
All companies
Subscription management
Loading company subscriptions…
Provider-controlled payment rail
DOKU configuration
Prepare Taro POS-managed QRIS and subscription collection without changing the current cashier flow until every activation requirement is ready.
Manual QRIS remains available.
When DOKU is inactive or incomplete, cashier QRIS continues as the existing external QR/manual confirmation flow.
Global provider
Connection and rollout controls
Merchant access
Company enablement
A company must be explicitly enabled here before any of its outlets can use Taro POS-managed QRIS. Disabled companies continue with manual QRIS.
Loading companies…
Settlement routing
Outlet subaccounts and payouts
Link each outlet to its DOKU subaccount and payout destination. The outlet remains on manual QRIS until its company, mapping, and provider are all ready.
Loading outlets…
PC → production · Yusuf only
Move migration data
On your PC, capture the selected companies and outlets, then choose Export captured data in its run. Upload the file here on production. A complete capture can be exported with native workflow gaps; the package includes those findings. Kafei imports the captured records and images using the same mappings. Production needs no MaxsPOS connection or VPN.
For the final update, resync and complete a full final cutover on the PC, then upload its package here before activation. A staging package keeps the imported outlets inactive.
Application database: SQLite. MySQL runtime support is not ready in this build.
Select the package exported by this same version of Kafei.
Read-only legacy source
MaxsPOS migration
Inspect all 220 tables across maxs_data_center, maxs_disconf, maxs_item, maxs_job, maxs_member, maxs_open, maxs_order, and maxs_shop; then choose enterprises, outlets, and an exact date window. Previewing writes no Taro POS business records.
Loading migration configuration…
Step 1
Verify and inspect the source
The server forces every source session into a MySQL READ ONLY transaction. Credentials stay in the server environment and are never returned to this page, SQLite, logs, or plans.
No source inspection in this session.
Step 2
Choose scope and target
Select the companies, outlets and history to bring into Taro POS.
MaxsPOS companies
0 selectedInspect the source in Step 1 to load companies.
Company outlets
0 selectedAll company outlets start selected. Uncheck any outlet to leave it out.
Select a company to see its outlets.
Transfer options
History date range
All available history will be includedTaro POS destination
No outlets selectedCreate a new outlet, or map each source outlet to an existing empty outlet.
Choose your source outlets firstDestination options appear here after inspection and selection.
Step 3
Migration plan and table coverage
Build a plan to see exact counts, native mappings, archived records, exclusions, warnings, and its immutable hash.
Step 3b · read only
Mapping evidence scan
Run aggregate-only checks for populated tables that still block this exact plan. Reports contain counts, hashes, and review blockers only; they never contain source rows, credentials, or raw company/outlet identifiers. A full scan produces review evidence but never approves a mapping automatically.
Build a frozen plan first.
Step 4 · import data
Start the reviewed plan
Click Start migration to preserve the selected source data and translate it into Taro. MaxsPOS stays open during staging; Taro only reads its database. You can pause and resume, then resync for new or changed source data. After capture, export the package for another Taro server or review the imported data before choosing Go live. Workflow findings remain visible; failed loads and data-integrity errors require attention. Resync before switching if MaxsPOS has received more transactions.
Start queues the exact plan displayed above. It does not make the imported companies and outlets live.
Durable history
Plans and migration runs
Loading runs…
Direct database access
SQLite operations console
Browse data and relationships, run queries, insert or edit records, and create or alter tables, indexes and views. Every change is previewed, backed up and audited.
Cadangan database lengkap
Ekspor SQLite dan SQL
Mencakup seluruh data aplikasi, riwayat migrasi, dan gambar. Unduhan berisi data privat; hanya sesi Yusuf yang membuat ekspor dapat mengunduhnya. Database tetap dapat dipakai selama cadangan disiapkan.
Pilih format untuk membuat cadangan yang konsisten.
Unduh ekspor yang sudah siapSelect a table to inspect its rows.
query.sql
Direct SQL
Write previewUPDATE and DELETE require an outer WHERE clause. Preview runs inside a transaction that is rolled back. Review affected rows and related tables before committing.
Result
Execution output
Query results and write counts appear here.
Confirm reviewed change
Type
Immutable operator trail