Create New Order

This endpoint allows stores to create new orders directly in the system, bypassing delivery platforms. This is useful for in-store purchases, phone orders, catering orders, or any direct customer transactions.

This endpoint creates orders that are immediately available for fulfillment and can be integrated with your existing POS system or used for direct customer service.

Request Body

store_id

string

required

The unique identifier of the store creating the order

customer

object

required

Customer information for the order

Show Customer Object

customer_name

string

required

Customer’s full name

contact_phone

string

required

Customer’s contact phone number

string

Customer’s email address

delivery_address

object

Delivery address (required if order_type is “delivery”)

Show Address Object

street

string

required

Street address

city

string

required

City

state

string

required

State or province

zip_code

string

required

ZIP or postal code

apartment

string

Apartment or unit number

delivery_instructions

string

Special delivery instructions

order_items

array

required

Array of items to include in the order

Show Order Item Object

item_id

string

required

Unique identifier of the product/item

quantity

integer

required

Quantity of this item to order

special_instructions

string

Special preparation instructions for this item

modifiers

array

Array of modifier IDs and values (e.g., size, extras, customizations)

order_type

string

required

Type of order: “pickup”, “delivery”, “dine_in”

partner

string

default:"LulaDirect"

Source platform (defaults to “LulaDirect” for manual orders)

payment_method

string

required

Payment method: “cash”, “card”, “online”, “corporate_account”

special_instructions

string

General order-level special instructions

scheduled_time

string

Scheduled pickup/delivery time (ISO 8601 format). If not provided, order is for immediate fulfillment

created_by

string

required

Employee ID who created the order

Response

success

boolean

Indicates whether the order was successfully created

message

string

Confirmation message or error details

order

object

Complete order object with all calculated values

Show Created Order Object

string

Unique order identifier

order_number

string

Human-readable order number for customer reference

subtotal

string

Order subtotal before taxes and fees

tax_amount

string

Calculated tax amount

total_price

string

Final total price including all fees and taxes

status

string

Initial order status (typically “pending” or “confirmed”)

estimated_ready_time

string

Estimated time when order will be ready

createdAt

string

Order creation timestamp

fulfillment_id

string

Unique identifier for fulfillment tracking

Request Example

{
  "store_id": "449235c1-3d04-4519-998b-40d2a621e5e0",
  "customer": {
    "customer_name": "John Smith",
    "contact_phone": "+1 555-123-4567",
    "email": "[email protected]",
    "delivery_address": {
      "street": "123 Main Street",
      "city": "Chicago",
      "state": "IL",
      "zip_code": "60601",
      "apartment": "Apt 4B",
      "delivery_instructions": "Ring doorbell twice"
    }
  },
  "order_items": [
    {
      "item_id": "prod_12345",
      "quantity": 2,
      "special_instructions": "Extra hot",
      "modifiers": [
        {
          "modifier_id": "size_large",
          "value": "Large"
        }
      ]
    },
    {
      "item_id": "prod_67890",
      "quantity": 1,
      "special_instructions": "No ice"
    }
  ],
  "order_type": "delivery",
  "partner": "LulaDirect",
  "payment_method": "card",
  "special_instructions": "Please call when arriving",
  "scheduled_time": "2024-01-15T18:30:00Z",
  "created_by": "emp_abc123"
}

Response Example

{
  "success": true,
  "message": "Order successfully created and added to fulfillment queue",
  "order": {
    "id": "ord_new_123456",
    "order_number": "LD-2024-001234",
    "subtotal": "28.50",
    "tax_amount": "2.28",
    "total_price": "30.78",
    "status": "confirmed",
    "estimated_ready_time": "2024-01-15T18:30:00Z",
    "createdAt": "2024-01-15T17:45:00Z",
    "fulfillment_id": "ful_abc789",
    "customer": {
      "customer_name": "John Smith",
      "contact_phone": "+1 555-123-4567",
      "email": "[email protected]"
    },
    "order_items": [
      {
        "id": "oi_item1",
        "item_name": "Large Coffee",
        "quantity": 2,
        "unit_price": "4.50",
        "total_price": "9.00",
        "special_instructions": "Extra hot"
      },
      {
        "id": "oi_item2",
        "item_name": "Iced Tea",
        "quantity": 1,
        "unit_price": "3.25",
        "total_price": "3.25",
        "special_instructions": "No ice"
      }
    ]
  }
}

Order Creation Workflow

Order Numbers: The system generates human-readable order numbers (e.g., “LD-2024-001234”) for customer reference, separate from the internal UUID.

Scheduled Orders: Use the scheduled_time parameter for advance orders. The order will automatically enter the fulfillment queue at the appropriate time.

Error Responses

Common Error Scenarios

Item Not Available

{
  "success": false,
  "message": "One or more items are not available",
  "error_code": "ITEM_UNAVAILABLE",
  "unavailable_items": ["prod_12345"]
}

Invalid Address (for delivery orders)

{
  "success": false,
  "message": "Delivery address is outside service area",
  "error_code": "INVALID_DELIVERY_ADDRESS"
}

Payment Processing Error

{
  "success": false,
  "message": "Payment method could not be processed",
  "error_code": "PAYMENT_FAILED"
}

Payment Processing: For card payments, ensure your payment processor is configured correctly. Failed payment processing will prevent order creation.

Use Cases

Common Use Cases

API Documentation - Legacy

API Documentation - Latest

Request Body

Response

Request Example

Response Example

Error Responses

Use Cases

API Documentation - Legacy

API Documentation - Latest

​Request Body

​Response

​Request Example

​Response Example

​Error Responses

​Use Cases

Request Body

Response

Request Example

Response Example

Error Responses

Use Cases