Fazeel Malik ✓ Подтверждено

← 1 of 28 →

Freedom Fun USA: Webflow + Odoo Rental Booking & Operations Platform Webflow storefront connected to a custom Odoo 19 backend: leads, quotes, online payments, crew dispatch, and reporting in one system. Live site: freedomfunusa.com Stack: Odoo 19 (Python, OWL, QWeb), Webflow, IPOS Pay, Mapbox, Quo SMS, Twilio Overview Freedom Fun USA is an inflatable and party rental business. The public website runs on Webflow, and all order management behind it runs on Odoo. I built a suite of six custom Odoo modules that takes a customer from their first website inquiry through booking, payment, and event-day delivery, with no manual data entry between steps. The Challenge A rental business runs on many connected steps, and each one is a place to lose time or money: Website inquiries had to reach the sales team without copy-pasting. Bookings needed event dates, delivery zones, fees, deposits, damage waivers, and tips. Customers needed to pay deposits and balances online, including tips after the order was fully paid. Field crews needed to see their jobs and tell customers when they were on the way. Managers needed reliable payment and sales reports. Years of orders in a legacy system (ERS) had to move into Odoo. The Solution Webflow → CRM → Rental POS → Payment → Coach → Reporting Lead capture. A Webflow form submission hits a custom webhook in Odoo and instantly creates a lead in a purpose-built CRM, with partner records created automatically. Lead management. Sales staff work leads in a stage-based kanban pipeline with SLA tracking, SMS and email outreach, and a salesperson security group. Quoting and booking. One click on “New Quotation” opens a custom Rental POS (built in OWL) with the lead preloaded. Staff add products, travel and misc fees, damage waiver, tip, deposit, discounts, and event address, with zip-code delivery checks. Customer communication. Branded HTML quote and invoice emails go out with a printable contract and a payment link. Customers sign a digital waiver and contract. Online payment. Public pay pages accept card, Google Pay, and Apple Pay through a custom IPOS payment provider. They support deposits, remaining balances, and tip-only payments. Saved cards can be auto-charged for the remaining balance on event day. Event-day operations. Coaches (the field crew) log into a portal and see only their assigned jobs. They tap En Route, which calculates an ETA with Mapbox and texts the customer through Quo SMS. Reporting. Managers get a reporting suite covering sales, payments, tax, receivables, tips, credits, customers, signatures, and commissions. The Six Modules Module Role freedomfun_crm Standalone lead and pipeline system with stages, SLA cron, auto partner creation, and sale-order linkage. custom_freedomfun_usa Webflow webhook receiver, company and CRM settings, salesperson security group, and product and category helpers. custom_ipos_pay Odoo payment provider for the IPOS gateway: charges, refunds, test/live toggle, and a settlement-sync cron. custom_rental Core rental hub: POS, quotes, pay pages, contracts, wallets, audit logs, and the reporting suite. freedomfun_coach_portal Coach portal, assignment rules, En Route tracking, SMS logs, and a manager dashboard. ers_migration Imports and syncs legacy ERS orders into Odoo rentals, with per-company credentials and a dry-run wizard. Key Features Webflow-to-Odoo webhook that turns website forms into CRM leads Custom Rental POS with fees, deposits, damage waiver, tips, and zip delivery checks Digital contracts and waivers with signature capture Public payment pages for quotes and invoices (card, Google Pay, Apple Pay) Saved cards with automatic balance charging on event day Raincheck and credit wallets applied to orders Coach portal with Mapbox ETA and automatic customer SMS Full audit trail: email logs, payment logs, and order audit history Legacy ERS data migration with dry-run mode and migration logs Manager reporting: Month-to-Date, Tax, Sales Gross, Payments, Receivables, Credits, Tips, Customers, Signatures, and Commission Technical Highlights Dependency-cycle avoidance. freedomfun_crm deliberately depends on neither Odoo’s crm app nor custom_rental, because that would create a cycle through the website module. Rental and CRM connect through a soft link instead: a freedomfun_lead_id field on sale orders and an overridden “New Quotation” action. Payment safety. The rental layer extends the IPOS charge controller with double-pay guards, tip handling, card saving, and payment logging. Stale transaction cleanup. A scheduled job cancels abandoned draft or pending payments that never reached the gateway after five minutes, so customers can retry cleanly. Payment reconciliation. The “Odoo Pay” report matches Odoo payment transactions against IPOS batch and live status data, using settlement fields (RRN, funding date, fees) synced by cron. Safe migration. The ERS sync stores x_ers_* identity fields to avoid duplicates, runs on a schedule, and has a dry-run wizard to preview imports before they are committed. Role-based access. Portal record rules ensure coaches see only their assigned orders. Modular design. Each module has a single responsibility and a clear install order, so migration tooling can be installed only where it’s needed. Integrations Webflow (webhooks), IPOS Pay (payments and refunds), Mapbox (routing and ETA), Quo (SMS), Google Pay and Apple Pay, and the legacy ERS system (data migration). Result The business runs its entire rental operation, from the first website inquiry to the final crew drop-off and financial reporting, on one Odoo backend behind its Webflow site.

← 1 of 4 →

Freedom Fun CRM: Custom Lead & Pipeline System for Odoo A self-contained Odoo CRM built for a rental business: website leads, stage-based pipeline, SLA tracking, and a direct path from lead to quote. Stack: Odoo 19 (Python, XML views), mail, sms, sale Module: freedomfun_crm (v0.1.8) Overview Freedom Fun USA needed a lead system shaped around how a rental business sells, not a generic sales funnel. I built freedomfun_crm, a standalone CRM module with its own lead model, pipeline stages, and sale-order linkage. It receives leads from the Webflow website and hands them off to the rental quoting flow. The Challenge Website inquiries needed to land in a pipeline staff could work, with customer records created automatically. Leads needed to be tied back to the quotes and orders they produced. Slow responses cost bookings, so the team needed SLA handling. Staff needed to contact customers by SMS and email directly from the lead. The rest of the stack needed a CRM that wouldn’t create circular dependencies with the website and rental modules. Old leads from Odoo’s standard CRM needed a path into the new system. The Solution A self-contained lead system with its own data model and workflow. Custom lead model. Freedom Fun’s own lead record, which automatically creates a res.partner when appropriate, so staff aren’t re-entering customer details. Stage-based kanban pipeline. Leads are grouped by stage, with stages loaded from data files for a consistent setup on install. Quotation linkage. Sale orders link back to the lead that produced them. In the rental module, “New Quotation” opens the Rental POS with the lead preloaded. SLA cron. A scheduled job handles lead SLA tracking, so leads don’t go stale. SMS and email outreach. Uses Odoo’s mail and sms apps to contact customers straight from the lead. Legacy migration path. An optional data file imports old crm.lead records when Odoo’s standard CRM is present at runtime. Security. Access rights and record rules control who sees which leads. Key Features Custom lead model with automatic partner creation Kanban pipeline with data-driven stages Lead-to-sale-order linkage for end-to-end traceability Scheduled SLA handling SMS and email outreach from the lead form Optional migration of legacy Odoo CRM leads Security rules for lead access

← 1 of 7 →

Freedom Fun USA: Odoo Field Crew Portal with Live ETA & Customer SMS A mobile-friendly portal where field crews see their assigned rental jobs, tap En Route to send customers a live ETA by text, and managers track everything from one dashboard. Stack: Odoo (Python, QWeb, Portal/Website), Mapbox, Quo SMS Module: freedomfun_coach_portal (v0.7.11) Name options Freedom Fun USA: Odoo Field Crew Portal with Live ETA & SMS (my pick): it names the platform and the two standout features. Freedom Fun USA: Coach Portal & Dispatch Dashboard on Odoo: leads with the dispatch angle, which reads well to operations-minded clients. Odoo Field Service Portal with Mapbox ETA & SMS Alerts: stack-first, good for search and portfolio cards. Freedom Fun USA: Crew Dispatch & Customer Notification System: outcome-focused, with less emphasis on the tech. Overview On event day, a rental business depends on its crew showing up on time, and customers want to know when that will be. I built freedomfun_coach_portal, a portal for Freedom Fun’s field crew (called “coaches”) and an admin dashboard for managers. Coaches log in to see their assigned jobs, mark progress, and go En Route. The system calculates an ETA with Mapbox and texts the customer automatically. The Challenge Crews needed a simple place to see which jobs were theirs, and nobody else’s. Customers needed to know when the crew was on the way, without staff making calls. Managers needed visibility into coach activity and customer messages. Everything had to attach to the same rental orders the office already used, not to a separate system. The Solution Coach assignment on sale orders. Coaches are linked to rental orders, and both the portal and backend views show who owns each job. Portal for coaches. Dashboard, account, and orders views, styled in Freedom Fun’s blue and yellow branding. En Route with live ETA. Mapbox calculates routing and ETA against the order’s event address. Automatic customer SMS. When a coach goes en route, a text goes to the customer through Quo SMS, and each message is recorded in an SMS log. Manager dashboard. A backend admin view for overseeing coach activity. Scheduled jobs. Cron jobs handle cleanup and reminders. Strict access control. Portal record rules ensure coaches only see their own assigned orders. Key Features Coach-to-order assignment visible in portal and backend Branded coach portal with dashboard, account, and orders pages One-tap En Route with Mapbox routing and ETA Automatic customer SMS through Quo, with a searchable SMS log Manager dashboard for coach oversight Record rules limiting each coach to their own jobs Credentials for Mapbox and Quo managed in Odoo settings Technical Highlights Built on the rental order. Event address, schedule, products, and notes all come from the existing rental sale order, so the office and the field crew work from the same record, with no duplicate data entry or sync issues. Portal security done properly. Record rules at the database level, not just hidden menus, keep each coach limited to their assigned jobs. Third-party integrations. Mapbox for geographic routing and ETA, and Quo for outbound SMS, with an audit log of every message sent. Clean module boundaries. The portal depends on sale_renting and standard Odoo portal and website apps, and the rental hub depends on it, so crew features are available wherever rental orders are used.