Penahak is not a set of separate products sharing a login. It is one platform with a single accounting core, and every other module posts into it.
The core rule
Modules own operational state. The ERP owns financial truth.
Hospitality knows which room a guest is in and whether it has been cleaned. Restaurant POS knows which table ordered what. Neither of them keeps its own set of books. When money, stock, tax or a customer balance changes, the change is made by a central ERP source document, and the module stores an immutable reference to it.
This is why occupancy reports and revenue reports agree in Penahak. They are reading the same underlying facts.
What is shared
- Party master — one customer, vendor, guest and agent record, used by accounting, CRM, POS and hospitality alike.
- Product and service catalogue — rooms, dishes, minibar items and retail lines all resolve to a central item with its own unit, tax terms and revenue ledger.
- Inventory — one stock engine serves the shop floor, the kitchen and the minibar.
- Posting engine — SalesBill, receipts, payments, vouchers and ledgers.
- Audit trail — every module emits its events into one activity model.
What this means day to day
You can start with just the counter or just the books, and switch other modules on later. Because the ledger and the party master are already shared, adding a module is a configuration job rather than another data migration.
It also means some actions are blocked until configuration is complete. That is deliberate — see Setup gates: why posting is blocked.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support