everjust-appointments

Create an appointment.booking record with the type, partner, and UTC-naive start_datetime, then call action_confirm(). Confirming sets the state, creates the calendar event, optionally creates a CRM lead, and sends the confirmation email — never write state directly.

No slots appear when the appointment type is unpublished, has no slot for the requested weekday, the time falls inside min_schedule_hours or beyond max_schedule_days, or every staff member has a conflicting calendar event or booking.

No. It is a bespoke LGPL reimplementation that shares the appointment.type and appointment.slot model names but has a different schema and API. Odoo's stock methods like _get_appointment_slots do not exist; read fields from the addon itself.

Call action_cancel() to unlink the old calendar event, write the new start_datetime, call action_reset_draft(), then action_confirm() to create the new event. Note that re-confirming a lead-generating type can create a duplicate CRM lead.

Not automatically. The _check_staff_availability() method exists but is never called by create, write, or action_confirm in this version. Call it explicitly before confirming ORM-created bookings to avoid overlapping staff schedules.

Avoid them for stock Odoo Enterprise appointment work, direct calendar.event manipulation, CRM pipeline management beyond lead creation, and bulk email. Also verify the module is installed on the target tenant DB, or env access raises KeyError.