Order to fulfilment

An order is placed, and it should actually get fulfilled, not just recorded as paid.

The purpose

"Every order gets fulfilled." Payment succeeding isn't the same as fulfilment happening. An order can be charged perfectly and still never make it into a warehouse or shipping queue if a step in between drops it.

Where the two pings go

Start: the moment an order is placed (a webhook from your store or checkout platform, or the first step of the automation that processes it).
Finish: the moment fulfilment is actually created (an order in your fulfilment or inventory system, a shipping label generated, whatever "handled" means for this business).

Use the order number as the reference, since almost every platform already has one, and it never repeats.

What healthy looks like

An order is placed, a matching fulfilment record appears within the expected window (which might reasonably be longer here than for a lead, since fulfilment often isn't instant, and the window should reflect that).

What a failure looks like

An order is placed and paid, but no fulfilment record ever appears. A sync between the store and the fulfilment system broke, or an automation step silently failed on an edge case (an unusual address format, a product no longer in the catalog). FlowProofs confirms the gap and alerts with the specific order number, instead of a customer finding out first.

Common variant

If the window here is genuinely longer than most flows (same-day fulfilment vs. next-day, for example), confirm and adjust it explicitly during onboarding rather than accepting a default meant for a faster process. See the expected window.