Skip to main content
PUT
Update Order Status

Overview

Update the status of an order and optionally provide tracking information. Customer receives email notification for status changes.
Rate Limit: 20 requests per minute

Endpoint

Path Parameters

string
required
UUID of the order to update

Authentication

string
required
Your TribeMade API key (format: tb-xxxx-xxx-xxxx)

Request Body

string
required
New order status. Must be one of: processing, dispatched, cancelled, delivered
string
Tracking URL for shipment (recommended for dispatched status)

Response

string
Success message: “Order status updated successfully”

Order Status Flow

Status Values

🔵 processing

string
When to use: Start preparing/packing the orderCustomer email: “Your order is being prepared”Tracking URL: Not requiredTiming: Within 24 hours of order placement

🟣 dispatched

string
When to use: Hand over to courier/shipping partnerCustomer email: “Your order has been shipped” with tracking linkTracking URL: Highly recommended
  • Example: https://delhivery.com/track/AWB12345
  • Example: https://bluedart.com/tracking/AWB67890
  • Example: https://indiapost.gov.in/track/REG123456
Customer expects: Delivery in 3-7 days

🟢 delivered

string
When to use: Customer confirms receipt or auto-marked by courierCustomer email: “Your order has been delivered” with rating requestStatus is final: Cannot be changed after thisCustomer action: Can now rate and review the product

🔴 cancelled

string
When to use: Out of stock, payment issue, customer requestCustomer email: “Your order has been cancelled”Status is final: Cannot be changed after thisCan cancel from: Any status (started, processing, dispatched)Important: Handle refunds separately through payment gateway

Examples

Mark as Processing

Mark as Dispatched with Tracking

Customer receives: “Order Shipped” email with tracking link

Mark as Delivered

Customer receives: “Order Delivered” email with rating request

Cancel Order

Customer receives: “Order Cancelled” email

Success Response

Error Responses

400 Bad Request - Missing Status

Cause: The status field was not included in the request body.

400 Bad Request - Invalid Status

Cause: Invalid status value provided. Valid statuses: processing, dispatched, cancelled, delivered

400 Bad Request - Order Already Completed

Cause: Trying to update status of an order that’s already in a final state (delivered or cancelled). Note: Once delivered or cancelled, status is permanent and cannot be changed.

404 Not Found

Cause: Order ID doesn’t exist.

403 Forbidden

Cause: Order exists but belongs to a different store.

401 Unauthorized

or

429 Too Many Requests

Tracking URL Guidelines

When to Provide

  • Required: When status = dispatched
  • Optional: Can be added/updated at any time
  • Best practice: Add immediately when shipping

Format & Examples

Example: https://delhivery.com/track/AWB123456789
Example: https://bluedart.com/tracking/AWB987654321
Example: https://indiapost.gov.in/track/REG123456IN
Any valid tracking URL from your shipping provider:
  • FedEx, DHL, DTDC, etc.
  • Must be a valid HTTPS URL
  • Should provide real-time tracking

What Happens

  • URL is saved to database
  • Included in customer email notifications
  • Customer can click to track their shipment
  • Displayed on order status page

Common Use Cases

Automated Fulfillment Workflow

Webhook-Triggered Status Update

Bulk Status Update

Integration with Shipping Provider

Best Practices

Follow the natural order of statuses:✅ Good flow:
❌ Don’t skip steps:
For dispatched status, always provide tracking URL:✅ Good:
❌ Bad:
Update orders at each stage:
  • Mark processing within 24 hours of order
  • Mark dispatched same day as shipping
  • Mark delivered based on courier confirmation
Timely updates improve customer satisfaction.
Remember that delivered and cancelled are final:
  • Cannot be changed after setting
  • Double-check before marking as delivered
  • Ensure refunds are processed before cancelling
Add retry logic for failed updates:

Typical Order Timeline

  • Day 0: Order placed → started
  • Day 0-1: Preparation begins → processing
  • Day 1-2: Shipped out → dispatched (with tracking)
  • Day 4-7: Customer receives → delivered

Next Steps

Get Order Details

Fetch complete order information

Webhooks

Receive real-time order notifications

Product APIs

Manage your product catalog

Rate Limits

Understand API rate limits