Future Delivery/Collection Orders

Orders API - Order Type = 7

Use Cases

• Advance ordering: Orders placed days or weeks ahead

• Custom products: Birthday cakes, catering orders

• Pre-ordering: Collect at future date/time

• Scheduled delivery: Future delivery slots

Example Scenarios:

• Customer orders birthday cake for collection in 2 weeks

• Corporate catering order for next month's event

• Pre-order breakfast for collection tomorrow morning

Technical Requirements

Mandatory Fields (all required):

• ✅ weborderdate (fulfillment date: YYYY-MM-DD)

• ✅ webordertimefrom (start time: HH:mm)

• ✅ webordertimeto (end time: HH:mm)

• ✅ webordername (customer name)

• ✅ customerno (customer identifier)

• ✅ webordertype (1=Delivery, 2=Collection)

• ✅ weborderproductiontype (0=Auto, 1= Manual Epos Manager Production Session)

• ✅ weborderdisplayno (collection reference number)

• ✅ weborderpayoncollectiondelivery (payment timing)

Critical Difference: Single-shot creation only - no UpdateOrder calls supported.

Integration Flow:

Full API details can be found here: API Reference

1. ValidateOrder → Pre-validate complete payload (RECOMMENDED)
   - Submit complete order for validation
   - Check all required fields present
   - Verify PLUs, prices, calculations
   - Confirm payload structure correct

2. AddOrder → Submit complete order
   - Single call with ALL order details
   - Include items, payments, customer info
   - Set isOpen based on payment status:
     * false if pre-paid
     * true if paying on collection
   - Order stored on cloud server

3. POS Retrieval → Automatic at scheduled time
   - POS pulls order at webordertimefrom
   - Order appears in kitchen
   - Staff prepares for scheduled time

Key Characteristics

• ❌ No UpdateOrder calls supported

• ✅ Single-shot complete submission

• ✅ ValidateOrder highly recommended

• ✅ Cloud storage until retrieval

• ✅ Scheduled kitchen preparation

• ✅ Pre-payment or pay-on-collection