WyntIQ is designed as a local-first Windows desktop product for operations where internet is unreliable, delayed, restricted, or unavailable. The architecture keeps daily work on the customer machine first, then supports controlled sync, export, backup, and integration paths when the network or deployment model allows it.
The desktop application is built around local availability. Users can log in, create records, process inventory, scan QR codes, generate reports, and maintain audit history on the installed machine even when there is no internet.
Operational records are stored on the customer device using a local database. This supports fast search, local reporting, QR workflows, and continued work during outages.
WyntIQ separates operational actions by role so the right person can request, approve, issue, procure, account, or administer without exposing unnecessary controls to every user.
QR records connect digital data to physical items, kits, documents, assets, and requests. This helps field teams confirm the right item quickly without searching through paper trails.
WyntIQ treats local records as the source of field activity. When multiple devices are used, sync must be designed around the customer environment: internet relay, LAN, offline file package, or a controlled customer server. The production sync policy is confirmed during deployment so data movement matches operational security requirements.
For serious offline operations, users must know what has been created locally, what has been shared, what is pending, and what needs admin review. WyntIQ's roadmap keeps this as a core product pillar rather than a hidden background feature.
Important changes are stored as traceable events so later synchronization can compare what happened, when, and by whom.
Imported or synced records should use stable identifiers to reduce repeated imports and accidental double processing.
When two users change the same operational record offline, an admin-visible review path is safer than silent overwriting.
Deployment can use internet, LAN, secure customer relay, removable media packages, or future managed sync service.
WyntIQ is built for controlled environments, but formal enterprise security approval depends on the final customer deployment model, policies, and infrastructure. The product is prepared for stronger hardening as pilots move into production.
| Area | Current Product Direction | Customer Deployment Consideration |
|---|---|---|
| User access | Role-based login and operational screens for admin, officer, store, accounts, vendor, and technician-style workflows. | Customer should define actual roles, approval limits, and account ownership before rollout. |
| Passwords and activation | Local authentication and controlled online/offline activation codes for trials and paid licenses. | Enterprise deployments can require stronger policy, device registration, and admin review. |
| Audit trail | Operational actions are recorded with user, action, time, and context so managers can review what happened. | For legal or defence use, audit retention, export format, and inspection workflow should be agreed in writing. |
| Email credentials | Mail setup uses provider-based configuration and secure local credential handling where enabled by the desktop environment. | Organisations should use app passwords, approved SMTP providers, or internal mail relays. |
| Backups | Local backup and restore planning protects data before updates, migration, or machine replacement. | Customer SOP should define daily backups, offline copy, restore test, and admin custody. |
Many customers already have data in spreadsheets, SQL databases, ERP systems, Azure environments, or operational applications. WyntIQ should not force a risky migration on day one. The safest path is staged import, mapping, validation, then controlled integration.
Start with CSV or spreadsheet imports for inventory, assets, vendors, and opening stock. This is easiest for pilot customers and keeps risk low.
Map customer SQL Server, SQLite, PostgreSQL, MySQL, or Azure SQL data fields into WyntIQ structure with read-only review before live import.
For mature customers, connect approved APIs, ERP exports, or a customer relay service so WyntIQ can exchange data under IT control.
WyntIQ is being improved for large operational catalogs: thousands, lakhs, and eventually very large item sets. Scale is not just a UI problem. It needs indexing, pagination, import validation, backup discipline, and a deployment design that matches the customer workload.
Search, filters, pagination, and database indexes reduce load when item lists become large. Bulk import should validate data before it becomes operational stock.
Updates should keep backups, avoid destructive migrations, and preserve local customer data. Release notes are reserved for meaningful product updates and serious fixes.
Before a large deployment, WyntIQ should be tested with customer-like data volume, real user roles, backup restore, offline expiry, and sync conflict scenarios.
Local inventory, demands, approvals, QR workflow, reports, PDF/email workflow, activation, backup planning, accounts desk, and Windows installer delivery.
Customer role mapping, larger data imports, field workflow tuning, backup SOP, trial-to-paid activation, and proof testing with real operational data.
Managed relay, LAN/offline bundle sync dashboard, device management, Active Directory or LDAP, advanced conflict review, and customer server deployment patterns.
WyntIQ can be reviewed against your operating environment, users, databases, security requirements, backup policy, and offline workflow before you start a deployment.