Data reference
Every field, event and segment condition, with how it reaches Nonito and how fresh it is. Kept to what the product does today, so you can check it against your own store before you connect it.
Last checked against the product: October 2026
Order and checkout events arrive by webhook the moment they happen. A sync every 15 minutes reads the full order and catalogue, so nothing depends on a single webhook landing. See the Shopify integration for the flows this data runs.
| Data | How it reaches Nonito | How fresh | Notes |
|---|---|---|---|
| Order and checkout events | Shopify webhooks | As they happen | Start flows such as order confirmation and abandoned checkout. |
| Orders and line items | Shopify Admin API (GraphQL) | Every 15 minutes | Re-reads the last two days of changes, so an edit or a missed webhook is still picked up. |
| Past orders | One-off import when the store connects | Once | So recency, order count and spend start from your real history, not from the day you connected. |
| Customer totals | Recalculated from orders | After every order sync | Spend, order count, average order value, first and last order, cities. |
| Products, variants, collections, locations | Shopify Admin API (GraphQL) | Every 15 minutes | Used for product and collection conditions and for product blocks in messages. |
| Inventory per location | Shopify Admin API (GraphQL) | Every hour | Only for stores that use back-in-stock alerts. |
| Lifecycle stage and value tier | Scored by Nonito from order history | Every night | Eleven stages, from New to Lost, and a High, Mid or Low value tier. |
| Shopify topic | Becomes | Used for |
|---|---|---|
orders/create | order_created | Order confirmation, first-order welcome, post-purchase flows |
orders/updated | order_updated | Keeps the order current |
orders/paid | order_paid | Payment status on the order |
orders/fulfilled | order_fulfilled | Fulfilment status on the order |
fulfillments/update | order_delivered | Review and feedback requests once the courier marks it delivered |
orders/cancelled | order_cancelled | Cancellation follow-up |
refunds/create | order_refunded | Refund messages |
checkouts/create, checkouts/update | checkout_started, checkout_updated | Abandoned checkout recovery, with the link back to the checkout |
customers_email_marketing_consent/update | consent update | Keeps email opt-ins and opt-outs in step with Shopify |
inventory_levels/update | restock check | Back-in-stock alerts when a variant goes from zero to in stock |
Odoo connects through Nitro, Nonito’s enterprise platform. Nitro sends Odoo orders and customers to the Nonito events API as they change. Nothing is written back to Odoo, and it works with any Odoo version. See the Odoo integration for how the connection is set up. Running Shopify and Odoo together? See how both land in one customer profile.
| Data | How it reaches Nonito | How fresh | Notes |
|---|---|---|---|
| Order and customer events | Pushed by Nitro to the events API | As they happen | Each event is validated on the way in. A malformed event is refused with the field that failed. |
| Flow triggers | Read from the event queue | Within about a minute | Six of the eight events start flows today. |
| Order records for reporting | Built from order created and cancelled events | Every 15 minutes | Order value, items, branch and payment method, per order. |
| Event | Fields | Starts a flow today |
|---|---|---|
Order createdorder_created | Order ID, channel (online or store), totals, tax, discounts, currency, payment method, promo codes, branch, customer, items with category, note | Yes |
Order updatedorder_updated | Order ID, status, and any of totals, items, customer or branch that changed | Not yet, stored only |
Order cancelledorder_cancelled | Order ID, reason, refunded amount, refund reference | Yes |
Order packedorder_packed | Order ID, delivery company, tracking number and link, note | Yes |
Order dispatchedorder_dispatched | Order ID, delivery company, tracking number and link, note | Not yet, stored only |
Order deliveredorder_delivered | Order ID, delivery company, tracking number and link, delivery agent, received by | Yes |
Customer createdcustomer_created | First and last name, phone, email, marketing consent | Yes |
Customer updatedcustomer_updated | First and last name, phone, email, marketing consent | Yes |
A segment is a set of conditions on your customers. Conditions are evaluated on Shopify customer data: orders, products, collections and the lifecycle scores built from them. The audience form in the app covers the six most used conditions. Nonito's assistant and the Nonito MCP server accept all twelve.
| Condition | Operators | On the audience form |
|---|---|---|
Days since last orderdays_since_last_order | More than, less than, equals, between | Yes |
Days since first orderdays_since_first_order | More than, less than, equals, between | Assistant and MCP |
Number of ordersorder_count | More than, less than, equals, between | Yes |
Average order valueaov | More than, less than, equals, between | Yes |
Total spendtotal_spend | More than, less than, equals, between | Assistant and MCP |
Citycity | Is one of, is not one of | Yes |
Bought a productpurchased_product | Any of, all of, none of | Yes |
Bought from a collectionpurchased_collection | Any of, all of, none of | Yes |
Lifecycle stagestage | Is one of, is not one of | Assistant and MCP |
Value tier (High, Mid, Low)value_tier | Is one of, is not one of | Assistant and MCP |
Used a discountused_discount | Yes or no | Assistant and MCP |
Reachable byreachable_by | Phone, email, both or either | Assistant and MCP |
Every customer gets one stage, scored nightly from how often they buy against your store's own repeat cycle.
Orders with their line items, customers, products, variants, collections and store locations, plus abandoned checkouts, refunds, fulfilment updates and email marketing consent. Order events arrive by webhook as they happen, and a sync every 15 minutes catches anything a webhook missed.
Order and checkout events arrive as they happen. Orders, products and collections re-sync every 15 minutes, customer totals are recalculated after each sync, inventory updates hourly for back-in-stock stores, and lifecycle stages are scored every night.
Eight: order created, updated, cancelled, packed, dispatched and delivered, and customer created and updated. Nitro, Nonito’s enterprise platform, sends them as they happen. Six of them start flows today; order updated and order dispatched are stored but do not start a flow yet.
Nothing to Odoo. In Shopify, Nonito creates a discount code when a flow step is set to give one. It does not edit orders, customers or products.
Days since last and first order, number of orders, average order value, total spend, city, products and collections bought, lifecycle stage, value tier, whether they used a discount, and whether they can be reached by phone or email.
Not through conditions today. Segment conditions run on Shopify customer data. Odoo customers can be added to a segment by uploading them as a list, and six of the eight Odoo events can start a flow on their own.
No for Shopify: you approve Nonito in your Shopify admin and the sync starts on its own. For Odoo, Nitro is set up with you during onboarding.
Bring your Shopify store or your Odoo setup. We will show you which of these fields your data fills, and the first segment and flow built on it.