> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/delivery-events-overview-olo-integration.md). # Delivery Events Overview (Olo Integration) Solink generates an event whenever a delivery transaction occurs, allowing you to review footage and transaction data. Delivery event data updates in real time. If either a **chargeback** or **canceled order** occurs, Solink updates the delivery event with relevant data and renames the event to a "Chargeback" or "Canceled Order" event. **Note**: For information on how to filter and search for your delivery events, see [Filter Delivery Events](/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/filter-delivery-events-olo-integration.md). *** ## Delivery Event Field Definitions Your delivery event receipts in Solink consist of several fields to provide you with as much information as possible. See below for a definition of these fields: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-c513fe7bf824cf284c7cf3e9ff84d7c23dc82b6f%2F5ef0d2ae8a7405d5.png?alt=media) * **Method**: The dining method: * Takeout: Order is packaged and ready to be taken out of the restaurant. * Dine In: Customer dined in at the restaurant. * Delivery: Order delivered to customer. * **Source**: Ordering platform used to generate the order. * **Store**: The store name where the delivery event occurred. * **Customer**: The name of the customer who placed the order through the delivery app. * **Order Placed**: Date and time the customer placed the order through the app. * **Order Handoff**: The date/time when the order is ready to be handed off to the customer. Should be same as "Order Completed" field. * **Order Completed**: The date/time when the order has been completed in the restaurant. * **Duration**: The duration of time between order placed and order completed. * **Service**: The third-party delivery app used to place the order (DoorDash, Uber Eats, etc.). * **Assigned Time**: Time when the order was assigned to pickup the order. * **Driver**: Name of the driver picking up the order. * **Estimated Pickup**: The estimated time the driver will pick up the order in the restaurant, according to the delivery app. * **Actual Pickup**: The actual pickup time. * **Estimated Dropoff**: The estimated time the driver will drop off the order to the customer, according to the delivery app. * **Actual Dropoff**: The actual time the driver drops off the order to the customer. ### Chargeback Event A chargeback event occurs when a customer reverses the transaction for one reason or another. In many cases, this can cause your business to lose money from a delivery order. When a chargeback occurs, Solink adds chargeback data to the event receipt to give you more context: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-d98fca6843e4c86e15eeebd8b5dfec2d73a0d674%2F093ffc7237eefd85.png?alt=media) Unique chargeback fields include: * **Chargeback**: The date and time the chargeback occurred. * **Chargeback Type**: Indicates how the chargeback was processed (Full, Partial - entire order vs. select item(s) from order). * **Chargeback Reason**: Reason for the chargeback, as defined by the ordering service. * **Chargeback Amount**: Amount refunded to the customer. ### Canceled Order Event A canceled order occurs when the store or customer cancels the delivery. Unique canceled order event fields include: * **Reason**: Reason for cancelation (canceled by store, canceled by user, etc.). * **Order Canceled**: Date and time the order was canceled.\ ​ ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-8a501e06cd21669bac146a6f22c16058677fd139%2F087669983ceb2012.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/install-connect-and-integrate/integrations/olo-integration-delivery-orders/delivery-events-overview-olo-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.