SabNode
    ProductsFeaturesEnterpriseCustomersPartnersResourcesPricing
    AllConversationsAutomationCustomer DataGrowthAnalyticsCommerceDeveloperExplore products
    1. Home
    2. Features
    3. Commerce
    4. Orders Timeline
    Commerce · Orders Timeline

    Every order, one customer record, zero CSV gymnastics.

    SabNode pulls orders from Shopify, WooCommerce, Magento and in-chat checkout into a single timeline on the contact. Agents see lifetime value, last item bought, shipment status and RTO history before they hit reply — no tab switching, no stale data.

    • Shopify, Woo, Magento and chat orders
    • Lifetime value and order count live
    • RTO risk score and COD history
    • Shipping status from Shiprocket / Delhivery
    Feature signature
    SabNode . Commerce
    Orders Timeline

    Every order becomes a timeline event on the contact record.

    Live
    38%
    WISMO tickets deflected by timeline-aware bot
    <5s
    Sync latency from store webhook to timeline
    6×
    Faster segment builds vs CSV-export workflow
    The problem

    Your agents are flying blind

    When a customer messages "where is my order?", the agent typically opens four tabs: Shopify admin to find the order, Shiprocket to check the AWB, the gateway dashboard to verify payment, and a Google Sheet to remember if this person was a problem returner. By the time the agent has the answer, the customer has bounced or escalated. Multiply that by 3,000 tickets a month and you have a serious support cost.

    The second issue is segmentation. Marketing wants to broadcast a "frequent buyer" coupon to anyone with three orders in 90 days. To do that today, ops exports CSVs from Shopify, joins them in Sheets, dedupes by phone, then uploads to the broadcast tool. By the time the campaign runs, the data is two days stale and half the contacts have churned.

    The third is RTO. India's D2C economy bleeds working capital on cash-on-delivery returns. Knowing that a phone number has three RTOs in the last six months — at the point of the next chat — saves real money. Orders Timeline puts that signal exactly where the agent or the bot is making a decision.

    What it is

    Orders Timeline, in depth.

    Orders Timeline turns SabNode into a commerce-aware CRM. Every order from your connected stores, plus every in-chat checkout, lands as a timeline event on the matching contact. The match is done by phone first, then email, then any custom field, so you do not lose orders to formatting differences. The timeline is sorted chronologically with payment, shipment, delivery, return and refund nested as sub-events under the parent order.

    On the contact panel, agents see live aggregates: total orders, lifetime value, average order value, last item bought, last shipped date, RTO count, refund count, and a computed RTO risk score from 0-100. Hover any number to drill into the underlying orders. The same fields are exposed to the flow builder, broadcasts and segments — so you can build a "VIP buyers in Bengaluru with no RTO" segment in seconds.

    Shipping is woven into the timeline natively. SabNode integrates with Shiprocket, Delhivery, Bluedart and ShipStation, ingests AWB and status updates, and surfaces "Out for delivery", "Delivered", "RTO initiated" as discrete events. Status-change webhooks can trigger flows: WhatsApp shipment notifications, "rate your delivery" CSAT, or auto-refund on confirmed RTO.

    Returns and refunds get the same treatment. A Shopify refund posts as a sub-event with reason, amount and gateway ID. The contact's LTV automatically nets out, so your "high-value customers" segment never includes someone who returned half of what they bought.

    Capabilities

    Everything you get with Orders Timeline.

    7 capabilities
    01

    Multi-store ingestion

    Connect Shopify, WooCommerce, Magento or BigCommerce by OAuth. SabNode reads existing orders via the bulk API on first connect, then keeps current state via webhooks plus a safety-net poll.

    02

    Smart contact matching

    Phone-first matching with E.164 normalisation, then email, then custom field. Conflicting matches are surfaced as a merge candidate in the contact merge queue rather than silently dropped.

    03

    Live LTV and AOV

    Lifetime value, order count, last order date and average order value are materialised columns on the contact, not computed on the fly. Segments filter by them in milliseconds even at 10M-contact scale.

    04

    RTO risk score

    A model trained on your store's RTO history scores each open COD order 0-100 at creation. Agents and bots can ask for prepaid conversion on high-risk orders before they ship.

    05

    Shipping events

    Shiprocket, Delhivery and Bluedart status updates land as discrete timeline events. Out-for-delivery, attempted, delivered, RTO and disposed each have their own webhook your flows can branch on.

    06

    Refunds and returns

    Shopify and Razorpay refund events post as sub-events. LTV nets out automatically, and "frequent returner" tags can be auto-applied to power do-not-broadcast lists.

    07

    Timeline filters

    Filter the timeline by event type, channel, store or date. Search "all RTO orders in last 30 days" or "orders with refund reason damaged" from one panel without writing SQL.

    Use cases

    Built for the way teams actually work.

    E-commerceCase 01

    WISMO support deflection

    "Where is my order" tickets get auto-answered by a bot that reads the latest shipment event, replies with status and AWB, and only escalates if the shipment is delayed by more than 48 hours. Saves 30-40% of support volume.

    D2CCase 02

    COD risk gating

    New COD orders with an RTO risk score above 70 trigger a WhatsApp flow that offers a 5% prepaid discount before the order is dispatched. Confirmed prepaid orders ship the same day, risky COD orders are held.

    D2CCase 03

    VIP cohort broadcast

    Marketing builds a segment "LTV > 5000, no RTO in 6 months" and runs a private collection drop on WhatsApp. The segment is live, so a customer who returns later is dropped from the next send automatically.

    D2CCase 04

    Replenishment reminders

    A nutrition brand watches "last consumable order date" and triggers a reorder flow 28 days after delivery. The flow knows the SKU, the size and the discount tier and pre-fills the cart for one-tap UPI checkout.

    SaaSCase 05

    Subscription health

    A SaaS sees Stripe invoice failed events on the contact timeline and routes them to dunning. The CSM gets a card in their inbox with MRR, failure reason and retry schedule before they reach out.

    How it works

    From signup to first send in minutes.

    Orders Timeline is included on every SabNode workspace. No separate billing, no extra setup, flip it on from your workspace settings.

    1. 01

      Connect stores

      OAuth into Shopify, WooCommerce or Magento. Choose phone or email as the primary match key. Test in sandbox.

    2. 02

      Historical backfill

      SabNode pulls existing orders via the bulk API, matches them to contacts, and computes LTV and AOV in the background.

    3. 03

      Live event stream

      Webhooks for created, paid, fulfilled, shipped, delivered, refunded land as timeline events with full payload.

    4. 04

      Shipping enrichment

      Carrier webhooks add discrete shipping events. The bot can answer WISMO without an agent ever opening Shiprocket.

    5. 05

      Drive flows

      Use timeline events as triggers. Replenishment, RTO risk, refund recovery — all built in the flow builder.

    Plays well with

    Works with the tools you already ship on.

    Connect directly with your existing stack or leverage the Platform Core tools to extend capabilities natively.

    ShopifyWooCommerceMagentoShiprocketDelhiveryBluedartRazorpayStripe

    Platform Core Tools

    Enhance this feature with deep integrations into our core infrastructure. Connect via API, utilize webhooks, or embed directly using our SDKs.

    • Unified Dashboard Apps

      Manage all settings seamlessly within the core UI.

    • Developer APIs and Webhooks

      Extend functionality with custom automated workflows.

    Frequently asked

    Questions about Orders Timeline.

    Can't find what you're looking for? Talk to our team.

    How are duplicate contacts handled?
    SabNode normalises phone numbers to E.164 before matching, so the same Indian customer with +91, 91 or 0-prefix is one record. When ingestion finds a conflicting match (same email, different phone), the case is added to a merge queue with side-by-side context for an admin to resolve.
    Will the timeline slow down for large stores?
    No. Orders are stored on a partitioned event log and the contact panel pulls only the most recent 100 events by default. Aggregates like LTV and AOV are materialised columns, so loading a contact with 1,000 orders is the same speed as loading one with 3.
    Can I write back to Shopify from SabNode?
    Yes. The flow builder ships nodes to update order metadata, add a tag, cancel an order or create a draft order. Common patterns include tagging risky COD orders with "verify-before-ship" and creating draft orders from in-chat cart payloads.
    How is the RTO risk score computed?
    Per-workspace gradient-boosted model trained on your store's last 12 months of COD orders. Features include pincode RTO rate, contact RTO history, order value, time of day, product category and channel. The score is recomputed at order creation and exposed as a contact field.
    Do you support multi-currency stores?
    Yes. Each order is stored in its presentment currency plus a normalised workspace currency at the exchange rate at order time. LTV, AOV and analytics dashboards default to the workspace currency, with per-store breakdowns available in reports.
    Can returns trigger an automatic refund?
    Yes. A flow can listen to the "return delivered to warehouse" event from Shiprocket and call the Razorpay or Stripe refund API. The refund posts back as a sub-event on the order with a closing message to the customer on WhatsApp.
    How does this differ from a CDP?
    A CDP describes who the customer is. Orders Timeline describes what they bought, paid, returned and received — and exposes those signals to the flow builder, broadcasts and segments inside the same product. There is no ETL hop, so the data is fresh and the operator is empowered.
    Related features

    Stronger when stacked.

    Browse every feature
    In-chat Payments
    Collect payments inside the chat via Stripe, Razorpay and UPI.
    Read more
    Product Catalog
    WhatsApp Business catalog manager with live stock and price sync.
    Read more
    Cart Recovery
    Template flow that messages abandoners 20 minutes after drop-off.
    Read more
    Contacts
    Every conversation becomes a contact record — auto-deduplicated.
    Read more
    Commerce · Orders Timeline

    Ship orders timeline into production this week.

    No credit card. No sales call required. Spin up a workspace, plug in a number, and your team is live in under an hour.

    Start free Book a demoSee pricing
    SabNode

    SabNode is the operating layer for customer conversations. Chat, automation, CRM, broadcasts, commerce and AI in one workspace.

    Talk to sales
    Conversations
    Browse
    Automation
    Browse
    Customer Data
    Browse
    Growth
    Browse
    © 2026 SabNode. All rights reserved.
    PrivacyTermsStatusContact