Frequently Asked Questions

It is built for suppliers, principals, independent warehouses, 3PL providers, and teams that need controlled visibility across stock, orders, and warehouse activity.

Yes. Vision Logix WMS runs as a secure web application, so authorised users can access it through a browser without installing desktop software.

Yes. The system is designed for multi-warehouse operations, with role-based access so users only see the warehouses and data they are allowed to work with.

Yes. Stock count sessions can be scoped to a warehouse, principal, count type, and stock holding scope such as full counts, cycle counts, spot checks, damaged stock, or quarantine stock.

Yes. Count sheets are blind count sheets. They show product, barcode, location, batch, expiry, and count reference details, but not the system quantity.

Yes. Stock can be separated by status such as available, damaged, infested, quarantine, returned, hold, and expired where applicable.

Yes. Principal users are restricted to their own principal scope, and warehouse users are restricted to assigned warehouses. This is enforced server-side, not only by menu visibility.

Stock-changing workflows are designed to create movement and audit records so receiving, transfers, stock counts, adjustments, returns, and order activity can be traced.

Yes. Orders can be suspended with a reason so issues such as pricing, stock, or customer queries can be resolved before fulfilment continues.

Yes. The system supports short picks and discrepancies, with controls to prevent invalid over-picking and to keep picked quantities visible on the order.

Yes. Delivery debrief can capture delivered, returned, damaged, and short-delivered quantities with reasons and comments where the workflow is enabled.

Transfer loads and co-loads can support grouped warehouse movement where the operational rules allow it. Access rules still prevent users from seeing principals or warehouses outside their scope.

Yes. Task assignment is limited to users inside the current user's organisation or assigned warehouse scope. Cross-tenant assignment is blocked server-side.

Yes. The notification bell shows task reminders, ticket updates, feature suggestion updates, approval alerts, and system notifications.

Yes. Users can log tickets, add comments, upload screenshots or documents, and track progress. Vision BI support can manage the support queue.

Yes. Users can submit feature suggestions. Vision BI can review them, mark them for the roadmap, suggest custom development, reject them, or close them with decision notes.

POPIA does not automatically require all systems to be hosted only in South Africa. Cross-border data handling must be managed properly with appropriate safeguards and agreements.

Access is controlled through ASP.NET Identity roles and tenant scope. Vision BI, principal, and warehouse users have different permissions and data visibility rules.

Important workflow actions such as order status changes, transfers, stock counts, task updates, ticket changes, and approvals are logged where audit tracking has been implemented.

The system uses authenticated access, role-based permissions, tenant-scoped queries, HTTPS in hosted environments, database controls, backups, and restricted administrative access.

Some packages may include standard modules and user allowances, while additional users, modules, integrations, or storage-heavy features may be priced separately depending on the agreement.

Setup, onboarding, data migration, integrations, EDI work, and custom development may be quoted separately when they fall outside the standard platform package.

Standard support is available Monday to Friday, 08:00 to 17:00. Emergency system support is available for critical platform issues.

If a feature is useful to the standard platform, it may be considered for the roadmap. If it is specific to one organisation, Vision BI may recommend a separate custom development quote.