Frequently Asked Questions

We charge standard support rates of R950.00 hour for support requests.

Our software is built on Native PHP using a strict Model-View-Controller (MVC) architecture. It is designed to run seamlessly across two primary environments:

• Local Deployments: Windows servers running Local AMPPS.

• Live Deployments: Standard Linux servers utilizing cPanel Shared Hosting.

If the application fails to display on-screen errors, the server has likely suppressed them for security reasons. You can find the exact cause of the crash by checking the server's Apache error logs. For local AMPPS environments, navigate to D:\AMPPS\apache\logs to review the latest log entries.

There is no separate settings controller. All primary administrative configurations are managed directly from your main Admin Dashboard page.

Yes. The system is built with South African statutory compliance in mind. It natively handles standard 15% VAT logic, statutory tax year periods, and strictly adheres to IFRS Accounting Principles for all generated financial records.

This is a built-in safeguard. The web application checks stock availability by querying the QtyAvailable database field in Sage Evolution 200 ERP, rather than the QtyOnHand field. This ensures that stock already allocated or reserved for pending sales orders is not accidentally oversold online.

When a web order is placed, the integration logic automatically links the transaction data directly to your Sage Evolution 200 database. The order is mapped to the INVNUM table to generate the invoice, and individual items are recorded in the Sales Order Lines table to ensure ledger accuracy.

Security is not an afterthought; it is built into the foundation of the platform. By utilizing a strict MVC architecture, your database logic is completely isolated from the public interface. Furthermore, the system is routinely audited to prevent modern web vulnerabilities, including:

• SQL Injection (SQLi): All database queries use secure prepared statements.

• Cross-Site Scripting (XSS): Automated data sanitization prevents malicious script execution.

• Cross-Site Request Forgery (CSRF): Secure token validation is required for all form submissions and state-changing actions.