Clear answers about ZidiCore business software.

It is designed for hotels, lodges, guest houses, restaurants, bars and related hospitality operations. The right module combination depends on whether you need rooms, restaurant service, kitchen workflow, inventory or a mix of these functions.

The hospitality platform supports room and accommodation operations together with restaurant and POS workflows. Confirm the exact modules enabled in your deployment before onboarding.

The platform supports cashier receipt workflows including common 80mm use cases. Test the exact printer, browser and receipt layout you plan to use.

No. Payments your hotel or restaurant collects from guests are operational merchant transactions. Your ZidiCore subscription payment is a separate platform billing transaction.

Yes. Role-aware access is designed so front-office, cashier, service, stores and management users can receive permissions appropriate to their responsibilities.

It supports station structures, pumps, nozzles, tanks, fuel products, prices, deliveries, dips, meter readings, shifts, attendants, supported sales and payments, receipts and operational reporting.

It supports wet-stock related records and reconciliation concepts using tank, delivery, meter, sales and shift information. Reliable results still depend on accurate station measurement and handover procedures.

Those station payment methods can be recorded where configured. Confirm the available methods and settlement workflow for your deployment.

Petrol uses an isolated customer deployment and database model. Infrastructure setup, registration, readiness and optional single sign-on require approved configuration rather than being assumed automatic.

No. Station sales and merchant payment records stay within the Petrol system. ZidiCore subscription billing remains a separate financial domain.

It is a planned product area. Contact ZidiCore to verify which modules, demonstrations, onboarding options and implementation timelines are currently available before making a purchase decision.

The intended scope includes student and admission records, classes and streams, academics and results, fees, attendance, communication, staff access and school reporting. Each capability must be verified in the deployed product.

Curriculum and assessment organization is part of the intended direction, but a school should demonstrate its exact current workflow and verify live support before subscribing.

The intended platform uses authenticated access, server-side authorization, role controls, tenant or deployment isolation and audit-oriented handling of important administrative actions.

No. Fees paid to the school are the school's operational transactions. The school's software subscription payment to ZidiCore is separate.

It is designed for supermarkets, mini-markets, retail shops and growing multi-branch retailers that need checkout, purchasing, suppliers, inventory and management reporting.

Yes. The retail catalogue supports categories, brands, units, products, barcodes and package-aware selling. Product and package setup should be tested before go-live.

It uses a traceable inventory-movement approach for opening stock, purchase receipts, sales, returns, transfers, adjustments, counts and other supported movement types, with warehouse-aware balances.

Yes. Role and permission controls are designed for sensitive actions including pricing, returns, stock and administration. Configure permissions to match store policy.

It supports cashier shifts, till movements, sales history, returns, receipt reprints and X- or Z-style close-shift reporting concepts. Confirm the exact workflow enabled for your deployment.

The implemented ERP covers organization and branch setup, accounts and journals, catalogues, customers and suppliers, sales, purchasing, inventory, expenses, cash and bank operations, reports, service workflows, POS, cashier closeout, roles and controlled corrections.

Yes. It includes branch and stock-location concepts with branch-aware inventory and operational controls. Confirm your plan and onboarding configuration.

Yes. It supports quote-to-order-to-invoice workflows, customer receipts, partial payment and controlled credit or refund processes, along with a faster POS path for counter sales.

Posted history is corrected through controlled workflows such as credit notes, debit notes, refunds, voids, reversals or authorized adjustments. It should not be silently deleted or overwritten.

Available reporting includes operational dashboards, cashier Z-reports, sales, inventory, purchasing, collections and finance views, with supported CSV exports. The exact report set depends on configuration and enabled modules.