An event raised whenever an addon subscription is purchased.

Fired when a card verification is approved

Fired when a card verification is declined

An event raised whenever a nutrition consultation event successfuly created through calendly

An event raised whenever a nutrition consultation event is canceled

Fired when we want to ask the payment service to create a Transaction Payment Service will response back with a confirmed event called "TransactionCreated"

A command event that is available to any service that wants to create a Zendesk ticket

An event raised on delivery created to notify others about it.

An event raised on delivery delivered to notify others about it.

This event is fired when the user's delivery preferences are updated. It is listened to by delivery extender service to update the delivery days based on the user preferences. This event can be fired by dashboard service or core service. Dashboard service fires this event when CX updates the user's delivery preferences Core service fires this event when the user updates their delivery preferences Delivery extender will also be updating the delivery-management-service with the delivery preferences.

An event fired whenever a delivery is skipped

An event fired whenever a delivery is unskipped

An event that is raised whenever a driver actions on a delivery based on a customers request during a delivery hand-off.

Event event raised on food replaced (meal swapped).

Event fired when free one day trial coupon created for onboarding dropped user.

This command event is fired when the food team has generated a new menu.

An event raised whenever a customer add a habit to the progress page to track it. In other words when customer initiate a 7 day challenge of one habit.

An event raised whenever a customer compeletes a 7 day challenge of one habit.

Fired when a user's loyalty point is expiring within X days

Fired when the user assigns the spin the wheel reward to a certain delivery

An event that is raised whenever a customer rates a meal, event body changes according to the rating data combination.

An event fired whenever a order menu is generated

Fired when a failed payment is made

Fired when a payment has been successfully refunded.

Fired when a success payment is made

Fired when a payment is made physically at retail (e.g card or cash)

An event raised when a service wants to send a message to consumer app.

An event raised whenever the auto-renew status for a subscriber has been modified.

An event raised whenever new subscription created.

An event raised whenever a subscription deleted.

An event raised whenever subscription's last day changed.

An event raised whenever new subscription ended.

An event fired whenever a subscription is paused

An event raised when a subscription is renewed.

An event raised whenever a subscription resumes.

An event raised whenever the status of the subscription is updated

Fired when a transaction has been successfully created on Payment Service This event comes after firing CreateTransaction Event

This command event is fired when a challenge subscriber logs a tracker data

An event raised whenever user initiate auth flow

An event raised whenever a user logs his weight in weight tracker

Customer facing API service for mobile app

Service to create, validate & extend upcoming deliveries for subscribers.

Internal delivery system. Used to manage deliveries.

Loyalty Service. Responsible for the Calo loyalty program, both online & retail stores.

Internal menu system. Responsible for generating and storing daily menu.

Internal menu system. Responsible for generating and storing daily menu.

Internal Email system. Used to send emails to 1000s of customers. Hosted in AWS

Handles all retail related business processes. Connects our system with our Cafes.

A service that handles anything related to a subscription related business logic from creation to management.

A service that handles the integration between Calo and Zendesk. It creates and manages the zendesk tickets.