Home - Documentation - Integration flow (Event Order)

Event Order API (POS)

Event Go API (POD)

Integration flow

Our Point-Of-Order (Event Connect) integrations put your customers and order management processes front and centre, pushing incoming orders directly from your Point-Of-Sales system to Event TMS.

This means for our integration an order flow of:

A NEW, an order that has stock allocated is preferred
An UPDATE, to the order if it needs to be amended
A CANCEL, if the order is cancelled
A COMPLETE, once despatched

Event is trying to deliver all your orders the more efficient, cost effective say possible, so some rules help acheive this:

Event is at Orderline level
- Imagine a shopping basket, all different products but going to the same destination. Each product is a line number. An order can have multiple products shipping, each one would be a line. For example. 1.001, 1.002, 1.003
An order number must be unique
Once cancelled an order number cannot be reused. Date change if any uncertainity on the orders status.
You need to tell us where, when and what to deliver
- The better the address, the more chance it will be delivered correctly. We validate on Google addresses
- The delivery date is required, we can calculate a collection date.
- The quantity, weight and dimensions or we dont know what to pack on a truck

Event Go Documention

Event Order sync flow

Basic NEW order

A customer can place an order at anytime. The 1st point to clarify is 'when' to tigger the NEW order through the Event Order API? This is usually when it has a stock allocation and the order is a confirmed.
This can be 3, 4 or more days before due collection date. It can be 1 or 2 days.
The planning cycle would expect to generally receive the orders the day before collection is due for optimisation, carrier allocation and notification.

A basic order flow would be an order, with multiple orderlines, triggered to Event through Event Order. Event will validate the order, plan the order and trigger back a route informing you how and when the order will be collected.

Event.

NEW order

Order accepted

Plan result

TMS

Planning optimisation

Event Connect

Updating an order

An order can be updated many times before it is despatched.

To trigger these updates through Event Order, you can use the UPDATE prefix.

Event uses this prefix to simply update the existing order rather than create a duplicate order.

An UPDATE can be for many reasons BUT should always only be for actual changes to the order that affect its delivery. For example these are primary Update types:

Quantity, weights
Delivery Date
Order instructions
Product components

We don't expect to receive updates that are triggered through your POS because the order is viewed and no primary update is made. Unneccessary messaging generates unlooked for cost.

Are UPDATEs the same for parcels and pallets?

An UPDATE can also be considered to be a 'pack confirmation'. So for a parcel, packing the orders and generating the actual weight and dimensions of the package. The enables Event TMS to calculate the correct mode and carrier to make the delivery, in the same way for palletised goods, the last UPDATE is always the last instruction for delivery at that moment in time.