Workflow build / implementation (Built)

E-commerce Order-to-Delivery Automation

For a small e-commerce operation, the order is easy. It is everything after the order that gets messy: who is packing it, which rider has it, did it arrive, and what happens when it didn’t.

Status
Workflow build / implementation
Area
E-commerce Operations Automation
Workflow
6 steps · 3 failure paths
Stack

01 · Why it mattered

What the manual way was costing

  • Information was split between sheets, chats and people’s memory.
  • Customers had to chase updates, which is bad experience and extra work.
  • Failed deliveries had no clear owner.

02 · System concept

What I set out to build

One record per order, and every step updates that record. The customer gets notified at the moments that matter, and failed delivery is its own path with a person on it.

03 · Before / after

From manual steps to a system

Toggle between the manual process and the system. Click any step to see what it does, what tools it touches, and what happens if it goes wrong.

How it ran manually · depends on whoever is free

  1. 01Order comes in and is copied into a sheet or chatby hand
  2. 02Fulfilment is coordinated over messagesby hand
  3. 03Rider is assigned by whoever remembersby hand
  4. 04Delivery status lives in the rider’s chatby hand
  5. 05Customer asks “where is my order?” and someone has to go and find outby hand
  6. 06Failed deliveries are handled whenever somebody noticesby hand

04 · Decision log

Why I built it this way

D-01Build around the sheet they already use

The team was already living in a spreadsheet, so I used Airtable / Google Sheets as the record instead of introducing a whole new system they’d have to learn.

D-02Failed delivery is not an edge case

In delivery, failed attempts happen all the time. I gave it its own state and owner so it doesn’t just sit there looking like an active order.

05 · Reliability layer

What can go wrong, and who steps in

Where it happens
Step 05 Delivery update
What goes wrong
Delivery fails (customer unavailable, wrong address)
What the system does
Order moves into a failed-delivery state and someone is assigned to sort it out with the customer.
Who handles it
A person: ops team

Human-in-the-loop points

  • Human in the loopDelivery fails (customer unavailable, wrong address) → ops team
  • Human in the loopOrder is missing key details (address, phone) → ops team
  • Human in the loopNo rider assigned in time → dispatcher

06 · Evidence

What exists today

  • Workflow built and implemented around an Airtable / Google Sheets order record.

07 · What this demonstrates

What this demonstrates

Designing an operational workflow where the record is the backbone, status changes are visible, and the failure path is planned from the start.

08 · Stack / integrations

What it’s built with

  • AirtableOrder record and status tracking
  • Google SheetsAlternative record for sheet-based teams
  • EmailCustomer notifications
  • Workflow automationAutomation connecting each step

Architecture · static view · 6 steps · 3 failure paths

    • → ops teamOrder is missing key details (address, phone)
    • → dispatcherNo rider assigned in time
    • → ops teamDelivery fails (customer unavailable, wrong address)

More systems

Keep reading

Production client system

WhatsApp Appointment Booking Automation

Customers book, reschedule and cancel appointments by chatting on WhatsApp, and the calendar stays correct without anyone babysitting it.

  1. WhatsApp message
  2. Understand intent
  3. Check availability
  4. Book the slot
  5. Send confirmation
  6. +2 more
4 failure paths · 3 human handoffs
Workflow build / tested scenarios

E-commerce Return Request Automation

Return requests are checked against the policy, recorded, and walked through to refund or replacement, with invalid ones going to manual review.

  1. Return request
  2. Eligibility check
  3. Return recorded
  4. Instructions sent
  5. Return tracked
  6. +1 more
3 failure paths · 3 human handoffs

Similar workflow?

Got a process that looks something like this?

Tell me how it runs today and where it hurts. If it’s a good fit for automation I’ll tell you how I’d approach it. If it isn’t, I’ll tell you that too.

Tell me what you’re trying to automate