Order Processing

Overview

The Order Processing feature automatically handles orders and abandoned carts through Ecomdrop flow automation. When orders are created in Shopify, the app triggers configured Ecomdrop flows and updates order tags based on processing status.

How It Works

Order Creation

When a customer completes a purchase in your Shopify store, Shopify fires an ORDERS_CREATE webhook.

Webhook Reception

The Ecomdrop IA Connector receives the webhook and extracts order data including:

Order ID, name, and number
Line items with products and variants
Customer information
Shipping and billing addresses
Financial and fulfillment status

Flow Trigger

The app triggers your configured Ecomdrop “Nuevo Pedido” (New Order) flow with the complete order data.

Async Processing

Ecomdrop processes the order asynchronously. When complete, it calls back to the app to update order status.

Tag Assignment

Based on the callback result, the app automatically adds tags to the order in Shopify (e.g., ecomdrop-processed, ecomdrop-error).

Order Webhooks

New Order Webhook

The ORDERS_CREATE webhook triggers when:

A customer completes checkout
Payment is confirmed
The order is created in Shopify

Data sent to Ecomdrop:

Order Details
Line Items
Customer Info
Shipping Address

{
  "orderId": "gid://shopify/Order/123",
  "orderName": "#1001",
  "orderNumber": 1001,
  "createdAt": "2026-03-04T12:00:00Z",
  "totalPrice": "150000.00",
  "currency": "COP",
  "financialStatus": "PAID",
  "fulfillmentStatus": "UNFULFILLED"
}

{
  "lineItems": [
    {
      "id": "gid://shopify/LineItem/456",
      "name": "Product Name",
      "quantity": 2,
      "price": "75000.00",
      "sku": "PROD-123",
      "variantId": "gid://shopify/ProductVariant/789",
      "productId": "gid://shopify/Product/101"
    }
  ]
}

{
  "customer": {
    "id": "gid://shopify/Customer/999",
    "email": "customer@example.com",
    "firstName": "Juan",
    "lastName": "Pérez",
    "phone": "+57300123456"
  }
}

{
  "shippingAddress": {
    "firstName": "Juan",
    "lastName": "Pérez",
    "address1": "Calle 123 #45-67",
    "city": "Bogotá",
    "province": "Cundinamarca",
    "country": "Colombia",
    "zip": "110111",
    "phone": "+57300123456"
  }
}

Abandoned Cart Handling

Draft Order Webhook

The DRAFT_ORDERS_CREATE webhook triggers when:

A customer abandons their cart
A draft order is manually created
Checkout is initiated but not completed

Configure the “Carrito Abandonado” (Abandoned Cart) Flow ID in your settings to enable this feature.

Draft order data includes:

Draft order ID and name
Line items from the abandoned cart
Customer email and contact information
Partial address information (if provided)
Total cart value

Ecomdrop Flow Integration

Triggering Flows

The app uses the Ecomdrop API to trigger automation flows:

// Automatically called by the app
triggerEcomdropFlow(
  apiKey,        // Your Ecomdrop API key
  flowId,        // Flow ID from configuration
  orderData      // Complete order/cart data
)

Callback Mechanism

Ecomdrop can notify the app when processing completes:

Configure Callback URL

The app automatically provides a callback URL to Ecomdrop:

https://your-app.fly.dev/api/ecomdrop/callback

Ecomdrop Calls Back

When flow processing completes, Ecomdrop POSTs to the callback URL with:

{
  "orderName": "#1001",
  "apiKey": "your-ecomdrop-api-key",
  "status": "success",
  "tag": "ecomdrop-processed"
}

App Updates Order

The app searches for the order by name and adds the specified tags.

Order Tag Management

Automatic Tags

The app assigns tags based on processing status:

Tag	When Applied	Meaning
`ecomdrop-processed`	Callback with status “success” or “completed”	Order successfully processed by Ecomdrop
`ecomdrop-pending`	Callback with status “pending”	Processing in progress
`ecomdrop-error`	Callback with status “error” or “failed”, or immediate failure	Processing failed
`ecomdrop-completed`	Callback with status “completed”	Fulfillment completed

Custom Tags

Ecomdrop can send custom tags in the callback:

{
  "orderName": "#1001",
  "tags": ["dropi-fulfilled", "shipped-today"],
  "apiKey": "your-api-key"
}

All tags are added to the order cumulatively (existing tags are preserved).

Order Data Structure

GraphQL vs REST Compatibility

The app handles both GraphQL and REST webhook formats:

GraphQL Format (Default)

Modern Shopify webhooks use GraphQL format:

{
  "order": {
    "id": "gid://shopify/Order/123",
    "name": "#1001",
    "totalPriceSet": {
      "shopMoney": {
        "amount": "150000.00",
        "currencyCode": "COP"
      }
    },
    "lineItems": {
      "edges": [
        {
          "node": {
            "id": "gid://shopify/LineItem/456",
            "quantity": 2
          }
        }
      ]
    }
  }
}

REST Format (Legacy)

The app also supports legacy REST webhooks:

{
  "order": {
    "id": 123,
    "name": "#1001",
    "total_price": "150000.00",
    "currency": "COP",
    "line_items": [
      {
        "id": 456,
        "quantity": 2
      }
    ]
  }
}

Configuration Requirements

Order processing only works when both requirements are met:

Ecomdrop API Key is configured
Flow IDs are configured (Nuevo Pedido and/or Carrito Abandonado)

To configure:

Navigate to Configuration in the app
Add your Ecomdrop API Key
Set the Nuevo Pedido Flow ID for order processing
Set the Carrito Abandonado Flow ID for abandoned cart recovery
Click Save

Callback Authentication

The callback endpoint uses API key authentication:

API Key Validation

Ecomdrop must include the API key in the callback payload:

{
  "apiKey": "your-ecomdrop-api-key"
}

Shop Lookup

The app looks up the shop by API key to ensure the callback is authorized.

Order Search

The app searches for the order by name using GraphQL:

query GetOrderByName($name: String!) {
  orders(first: 1, query: $name) {
    edges {
      node {
        id
        name
      }
    }
  }
}

Tag Update

Tags are applied using the Shopify GraphQL Admin API.

Monitoring and Debugging

Server Logs

The app logs detailed information for debugging:

📦 Received ORDERS_CREATE webhook for shop.myshopify.com
🔍 Looking for configuration with shop: shop.myshopify.com
📋 Processing order #1001 for shop.myshopify.com
🚀 Triggering Ecomdrop flow abc123 for order #1001
✅ Successfully triggered flow for order #1001
⏳ Waiting for Ecomdrop callback to assign tags...

Callback Logs

📥 Received Ecomdrop callback: {"orderName":"#1001","status":"success"}
🔍 Processing callback for shop: shop.myshopify.com
🔍 Searching for order by name: #1001 using GraphQL API
✅ Found order by name: #1001 → gid://shopify/Order/123
🔄 Updating order gid://shopify/Order/123 with tags: ecomdrop-processed
✅ Successfully updated order #1001 with tags

Troubleshooting

Webhooks not triggering flows

Verify Ecomdrop API Key is configured in Settings
Check that Flow IDs are correct
Review server logs for webhook reception
Ensure the app is installed and active

Tags not being added to orders

Verify callback URL is accessible from Ecomdrop
Check that Ecomdrop is sending callbacks with correct format
Ensure API key in callback matches your configuration
Review callback logs for errors

Order not found by name

Ensure order name format matches (e.g., “#1001”)
Check that the order exists in Shopify
Verify app has read access to orders
For new apps, ensure protected data access is approved

Callback authentication fails

Verify the API key in the callback payload is correct
Ensure the API key matches what’s stored in the app
Check that the shop domain is correct

Best Practices

Test Webhooks

Use Shopify’s webhook testing tools to verify your configuration before processing real orders.

Monitor Tags

Regularly review order tags to ensure flows are processing correctly.

Handle Errors

Set up alerts for orders with ecomdrop-error tags to quickly resolve issues.

Async Processing

Remember that flow processing is asynchronous - tags appear after Ecomdrop completes processing.

Product Management - Link products to enable order processing
Configuration - Configure Ecomdrop API and Flow IDs

Overview

Getting Started

Core Features

Integrations

Configuration

Deployment

Overview

How It Works

Order Webhooks

New Order Webhook

Abandoned Cart Handling

Draft Order Webhook

Ecomdrop Flow Integration

Triggering Flows

Callback Mechanism

Order Tag Management

Automatic Tags

Custom Tags

Order Data Structure

GraphQL vs REST Compatibility

Configuration Requirements

Callback Authentication

Monitoring and Debugging

Server Logs

Callback Logs

Troubleshooting

Best Practices

Test Webhooks

Monitor Tags

Handle Errors

Async Processing

Build docs developers (and LLMs) love

Overview

Getting Started

Core Features

Integrations

Configuration

Deployment

Documentation Index

​Overview

​How It Works

​Order Webhooks

​New Order Webhook

​Abandoned Cart Handling

​Draft Order Webhook

​Ecomdrop Flow Integration

​Triggering Flows

​Callback Mechanism

​Order Tag Management

​Automatic Tags

​Custom Tags

​Order Data Structure

​GraphQL vs REST Compatibility

​Configuration Requirements

​Callback Authentication

​Monitoring and Debugging

​Server Logs

​Callback Logs

​Troubleshooting

​Best Practices

Test Webhooks

Monitor Tags

Handle Errors

Async Processing

​Related Features

Build docs developers (and LLMs) love

Overview

How It Works

Order Webhooks

New Order Webhook

Abandoned Cart Handling

Draft Order Webhook

Ecomdrop Flow Integration

Triggering Flows

Callback Mechanism

Order Tag Management

Automatic Tags

Custom Tags

Order Data Structure

GraphQL vs REST Compatibility

Configuration Requirements

Callback Authentication

Monitoring and Debugging

Server Logs

Callback Logs

Troubleshooting

Best Practices

Related Features