Events → Master calendar is a unified operating view. It does not merge unrelated resource records or replace their authoritative workflows: event capacity stays with offerings, delivery status stays with fulfillment, and service status stays with Service Center.
Step by step
- Open Events → Master calendar and confirm the selected business. The calendar is tenant-bound; switching businesses changes every visible commitment.
- Use the previous-month and next-month arrows to move one month at a time. Choose Today to return the calendar to the current month. Read the displayed month and the business timezone before interpreting dates near midnight or daylight-saving changes.
- Choose Month for the grid or Agenda for a chronological list. On smaller screens, the month view presents the visible commitments as a list rather than compressing an unreadable seven-column grid.
- Under Show, toggle Events, Deliveries, Service, and Other. The commitments-this-month count follows the visible source kinds. A hidden kind is filtered from the view; it is not deleted or cancelled.
- Read each entry's title, start and end, source badge, supporting subtitle, and status. Choose or open the source record through the supported product workflow when a schedule, address, assignee, capacity, or lifecycle value needs to change.
- For an event occurrence, edit the normal schedule through its offering. Use Manage exceptions for one-date cancellation, reschedule, or modification. Use staged reconcile-series for a broad recurrence rewrite so concrete instances, attendee calendars, capacity, publication, and webhooks preserve stable identity.
- For a delivery, change the promised schedule and status through Sales → Fulfillment Center. For service work, use the Service Center visit or appointment. Do not create a custom calendar entry to mask an incorrect source record.
- Use custom or external calendar entries only for dated commitments that do not already have an authoritative CentriPOS source. Choose the correct source type, visibility, timezone, status, organizer, attendee notification, and sync state.
- Treat visibility separately from source access. Public, Attendees, Staff, Internal, and Private describe calendar exposure, but a viewer still needs authorization to reach the underlying customer, participant, delivery, service, or event record.
- Choose Export .ics to download the entries currently included by the source-kind filters. The file includes safe calendar fields and stable identifiers; verify it before sharing because an internal company export can contain operational titles and timing.
- After a reschedule or cancellation, confirm the source version and calendar entry version advance and the new status is visible. External calendar sync can report Local, Pending, Synced, Failed, or Conflict; an exported file is not proof a connected calendar accepted an update.
- For a reporting or audit question, use the resource-specific report and source record. The calendar proves scheduled placement and current displayed state, not payment, delivery completion, service completion, participant consent, or attendance by itself.
- Calendar projections are maintained from authoritative event occurrences and instances, receipt-level deliveries, service visits and tickets, work and projects, plus deliberate custom/external entries. Large historical projection backfills run as bounded resumable batches rather than one unbounded request.
- Each delivery receipt contributes one customer-facing delivery calendar row. Internal route execution may add distinct delivery_operational_stop rows, which must not be counted as additional customer deliveries or emitted through the ordinary delivery webhook vocabulary.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Previous / next | Moves the displayed calendar one month backward or forward. |
| Today | Returns the displayed month to the current date. |
| Month | Seven-day grid on larger screens and a readable list adaptation on smaller screens. |
| Agenda | Chronological list of visible commitments. |
| Show: Events | Includes event occurrence calendar entries. |
| Show: Deliveries | Includes delivery commitments projected from fulfillment. |
| Show: Service | Includes service visit or service-appointment commitments. |
| Show: Other | Includes supported work, project, staff, external, or custom entries. |
| Commitments this month | Count of entries in the displayed month after source-kind filtering. |
| Source record | Authoritative event, delivery, service, work, project, staff, external, or custom record behind the entry. |
| Visibility | Public, attendees, staff, internal, or private calendar exposure classification. |
| Sync status | Local, pending, synced, failed, or conflict state for external calendar coordination. |
| Export .ics | Downloads the currently visible calendar set; it does not create a live subscription or prove external import. |
| delivery | One receipt-level customer delivery commitment on the master calendar. |
| delivery_operational_stop | Separate internal route-stop projection; never a second sale or customer delivery. |
Expected result
The intended event, delivery, service, and other commitments appear once at the correct date, time, timezone, source, visibility, and status; filters affect only the view; the .ics export matches those visible entries; and authoritative changes remain in each source workflow.
Troubleshooting
- Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
- Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
- Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.
CentriPOS API explorer · API Center administration