FrontAccounting Customization for Travel Agency
Budget: $10 – $30 USD
I currently run FrontAccounting in its default form, but our business is a travel agency and the standard “Item” fields don’t match what we actually sell. I need the core screens—items, sales orders, invoices, and related reports—re-worked so we can create, edit, and track the following services just as smoothly as a product in retail bookkeeping: Flight Booking, Hotel Booking, Tour Packages, Umrah Services, Travel Insurance, Student Consultancy, and Visa Consultancy.
What has to happen
• Extend or repurpose the item master to store travel-specific data (ticket numbers, hotel check-in/out, passenger details, visa expiry, policy numbers, etc.).
• Adjust entry forms and list views so staff can pick the right service type from a dropdown and see only the fields relevant to that service.
• Make sure tax, commission, and cost fields still post correctly to the GL for each new service.
• Update PDFs (quotes, invoices, receipts) so they show the new data cleanly.
• Keep all modifications as modules or clearly commented overrides so we stay upgradable with future FrontAccounting releases.
Tech stack & access
FrontAccounting 2.4 on PHP 8 / MariaDB. SSH and a staging copy are ready; Git is preferred for version control.
Acceptance
1. I can create each of the seven services without touching core code.
2. A test invoice for any service posts to the correct income and payable/receivable accounts.
3. No warnings in FA error logs and pages load within current response times.
If you’ve bent FrontAccounting or other open-source ERPs before, I’d love to see a quick outline of how you’d tackle the item master changes and how long you expect the first working draft to take.
What has to happen
• Extend or repurpose the item master to store travel-specific data (ticket numbers, hotel check-in/out, passenger details, visa expiry, policy numbers, etc.).
• Adjust entry forms and list views so staff can pick the right service type from a dropdown and see only the fields relevant to that service.
• Make sure tax, commission, and cost fields still post correctly to the GL for each new service.
• Update PDFs (quotes, invoices, receipts) so they show the new data cleanly.
• Keep all modifications as modules or clearly commented overrides so we stay upgradable with future FrontAccounting releases.
Tech stack & access
FrontAccounting 2.4 on PHP 8 / MariaDB. SSH and a staging copy are ready; Git is preferred for version control.
Acceptance
1. I can create each of the seven services without touching core code.
2. A test invoice for any service posts to the correct income and payable/receivable accounts.
3. No warnings in FA error logs and pages load within current response times.
If you’ve bent FrontAccounting or other open-source ERPs before, I’d love to see a quick outline of how you’d tackle the item master changes and how long you expect the first working draft to take.
Related categories:
PHP
Website Design
Graphic Design
HTML
Software Development
MariaDB
Git
Database Design