Melons Books is the business and accounting application developed by Melons, also known as Melons Web Development. It brings financial records, client work, documents, and administration into a private, authorised workspace. Melons is based in Amman, Jordan, and was founded by Alaa Al Refai.
A connected workspace for business records
Melons Books helps a team manage the information behind its day-to-day work: clients and suppliers, projects, quotations, invoices, payments, expenses, supporting documents, and communication. It runs with WordPress and provides its own application interface. Available functions depend on the installed version, configuration, and the permissions assigned to each user.
This page describes the application. It does not expose a private workspace or create an account. For questions about Melons Books or a project, contact Melons.
Accounting and documents
- Client, supplier, project, item, and account records linked to the business documents that use them.
- Quotations, invoices, credit notes, bills, expenses, receipts, and payment records with their applicable document numbers and status.
- Posting, reversal, payment-allocation, balance, and reporting workflows for supported transactions.
- PDF documents, statements, exports, and configured email sending, subject to the user’s access.
- Supported migration tools and retained import history, including information brought in from Zoho.
These tools support record keeping; they do not replace review by the people responsible for the business. Users should verify source records, account treatment, taxes, and reports before relying on them for filings or payments.
Client access and support
A client contact can be linked to a particular client and given selected portal permissions. Access is checked on the server for the requested records and downloads. A contact does not automatically see other clients or every function available to staff.
The support workspace keeps requests and conversations together, with staff notes separate from public replies. Where configured, support emails alert an authorised participant to activity; they do not copy private notes or attached files into a notification. Website enquiries can be connected to the team’s business workflow without automatically creating an account or accepted quotation.
Administration, security, and history
Administrators manage internal users, module and action permissions, client portal access, account suspension, and session termination. Security settings support global and per-account email verification-code policies and a dedicated security sender. A separate support sender can be selected independently of normal business correspondence.
Searchable activity and security logs record supported actions. Supported record changes include before-and-after history, while older events keep the information originally recorded. The audit system is designed to exclude passwords, verification codes, tokens, and connection secrets from new event details. Logs are useful evidence of recorded activity, rather than a guarantee that every historical action was captured.
Tasks, reminders, and notifications
Internal users can manage permitted tasks with an assignee, status, priority, due date, time zone, and reminder. Recurring tasks can advance to the next future occurrence after completion. In-app notifications cover supported task, support, email-failure, and backup events, with visibility checked against the recipient’s current access.
Reminders depend on the site’s scheduled processing and user access. They are not guaranteed real-time alerts and do not execute payments or other financial actions. Client portal users do not receive the internal task workspace or staff notification inbox.
Backups and optional connections
Administrative tools can create encrypted backups of supported application data or a supported WordPress installation. Recovery requires the recovery password, a valid archive, and the relevant hosting access. Full backups can contain personal information and configuration as well as accounting records, so they must be protected as sensitive files.
The application contains optional Microsoft OneDrive and Google Drive connectors. Any connection requires explicit administrator authorisation and remains subject to the provider’s policies and account requirements. Google’s current policy prohibits backing up a developer application’s or project’s content to Drive. The existing connector is not presented as an eligible or Google-approved backup service.
Use of cloud functionality is subject to provider permission. No Google or Microsoft endorsement, verification, or certification is claimed. The cloud-data section of our Privacy Policy explains account identity, authorisation tokens, archive contents, disconnection, and deletion.
Privacy, terms, and contact
Read the Privacy Policy for information about data handling and the Terms and Conditions for general use. Any commercial project, hosting, support, or implementation arrangement is governed by its specific agreement.
For application or service questions, email contact@melons.me or use the contact page. Please do not include account passwords, verification codes, or cloud credentials in your message.