Support Center

Support & Contact (stoqio)

Official support guide for stoqio inventory and POS project users. This section covers what support includes, what information to send, and how to get faster resolution.

Support Scope

  • Installation and environment setup issues (Laravel, database, React deploy basics).
  • Configuration help for inventory, invoice, stock, report, and backoffice modules.
  • Bug verification and patch guidance for purchased script version.
  • Route/API integration clarification for existing modules.
Not Included in Standard Support: custom feature development, full business logic redesign, server devops management, and third-party paid service setup beyond provided integration points.

Before You Create a Ticket

  1. Check this documentation pages first (installation, module docs, developer guide).
  2. Clear cache and verify latest code/deployment files are active.
  3. Reproduce the issue in a consistent step-by-step way.
  4. Collect technical evidence (error message, logs, API response, screenshot).

What to Send for Fast Resolution

Required InfoWhy It Matters
Purchase code + product nameSupport verification
stoqio version and deployment typeEnvironment-specific diagnosis
Exact module/page nameTargeted troubleshooting
Reproduce steps (1..n)Reliable issue replication
Error screenshot / console / network outputFaster root-cause identification
Relevant log snippetsBackend-level evidence

Recommended Diagnostic Attachments

  • Browser Network tab response for failing request.
  • storage/logs/laravel.log relevant lines around failure time.
  • Database error snippet (if migration/query issue).
  • Route info from routes/api.php if endpoint mismatch issue.

Priority Topics for Inventory Projects

  • Stock mismatch between inventory and inventory_items
  • Invoice total/VAT/discount calculation inconsistency
  • Sales return or waitlist flow error
  • Feature access middleware blocking module unexpectedly
  • Backoffice permission/rights mapping problem

Response Expectation

Support team typically responds in business support window. Complex bugs may require reproduction and patch cycle. Clear technical details significantly reduce turnaround time.

Best Practices

  • Send one issue per ticket to avoid mixed troubleshooting context.
  • Do not send production credentials in plain text.
  • If access is required, share temporary credentials and revoke after resolution.
  • Keep a staging environment for testing provided fixes before production deploy.