Skip to main content

Using event procedures to automatically fulfill orders

Did you know that you can link event procedures together like dominoes? Set up a simple chain reaction and automate complex fulfillment processes.

Linking event procedures together (0:54)

The problem with "one big event procedure" (1:49)

Setting off the chain reaction (2:42)


Sometimes it feels like there are a million little tasks that go into shipping orders. And if you’ve ever tried to juggle it all on your own, then you’ll know just how difficult and time-consuming it can be. But don’t worry! Lady event procedure is here to help. In the last video, she showed you how to create event procedures in your system. But did you know that you can also link event procedures together? Just think of them like a row of dominoes, where one event procedure triggers the next, then the next, and so on.

You can use this simple logic to automate complex fulfillment processes. Just spend some time brainstorming how your company ships orders. For example, let’s say that once you’ve finished packing an order, you switch its status to 6 to indicate that it’s ready for shipping. Then you book the items included in the order as outgoing. You generate the invoice. And lastly, you email that invoice to your customer.

Each little step of this fulfillment process can be broken down into an individual event procedure. Let me show you what I mean. So remember, in this example, orders are switched to status 6 when they’re ready to be shipped. So we’ll use this status change as the triggering event that sets off our entire chain reaction. And as soon as the order changes to status 6, we want to book all of the items included in that order as outgoing. And this procedure "Book outgoing items" becomes the triggering event that sets off the next step of our fulfillment process. This time, the event causes the customer’s invoice to be generated. And again in turn, this procedure becomes the next triggering event which then e-mails this invoice to the customer. So here you can really see what I mean by setting up event procedures like dominoes. This first event procedure triggers the second which then triggers the third.

Now at this point, you may be asking yourself, "why don’t I just create one big event procedure" that does everything at the same time? Well, be careful. Even though it seems like a good idea at first glance, things can easily go wrong. The problem here is that procedures aren’t carried out sequentially, one after the other. Rather, they’re all started at the same time, so whichever procedure is the quickest, ends up finishing first. In practice, it usually takes a few milliseconds longer to generate a document than it does to send out an email. So if you put both of these procedures together in one event, then you run the risk of having your email sent out before the invoice has been attached to it. Not worth the risk. It’s much safer to set up event procedures that run one after the other like a long line of dominoes.

And speaking of dominoes, now that we’ve set them up, let’s knock them down! Here I’ve got an order that’s currently in status 5 and is ready for shipping. All I need to do is switch the order status to 6 and this sets off the chain reaction. Suddenly I see that items have been booked as outgoing an invoice has been generated and it’s been sent to my customer. Just like that, event procedures turn even the longest to-do list into a quick chain-reaction!

To top