Stock Project FAQ

Stoqio FAQ & Troubleshooting

Frequently asked questions for stoqio inventory and POS operations, including stock, invoice, report, user roles, and deployment behavior.

General

Yes. Core operations are company-scoped and warehouse-scoped. Ensure correct company_id and warehouse selection during testing.

Usually due to role-right permission or feature preference gate. Check role rights and company_feature_preference flags.

Product master exists, but no effective stock batch available in inventory_items or quantity already consumed.

Stock-out behavior uses mode values like FIFO, LIFO, or RANDOM depending on configuration and service logic path.

Common causes: direct DB edits, incomplete migration patches, failed return/transfer flow, or custom code bypassing service layer updates.

Core types include sale, purchase, return, draft, quotation, and expense.

Check item-level VAT and discount values in invoice_items, then verify header aggregation in invoices.

Confirm SELL_RETURN feature is active, route is accessible, and original sale reference exists for return flow.

Stock arrival does not always auto-close waitlist. Reservation/claim/release transitions must complete based on your workflow settings.

Use stock guard request endpoints and approval actions from authorized roles.

Check auth token, middleware (auth:api, throttle:api), and permission/feature middleware assignments.

Use versioned endpoints under /api/v1. Keep frontend API clients synced with current route definitions.

SPA rewrite rule is missing on frontend host. Configure web server fallback to index.html.

Use date range filters, ensure DB indexes for high-usage columns (company_id, warehouse_id, date, invoice_no), and avoid unbounded queries.