tacitrun.com

Free worksheet · 20 minutes

The Post-Purchase Process Audit

A post-purchase process audit is a 20-minute self-audit in which a retail or ecommerce operator traces one real exchange or return — step by step, in the order it actually happened — and records the system each step is in, who carries it, how long it waits, and whether anything is re-typed. It ends in three numbers: handoffs, systems touched and fields re-typed. If one ordinary exchange takes more than two handoffs, the integration in your stack is a person.

By Dilip Pullela, Founder, tacitrun ·

Get the fill-in worksheet (PDF)

It downloads right here, and we email you the link.

We'll email you the worksheet and occasional notes on governed automation. No spam — reply “unsubscribe” anytime.

A 20-minute self-audit for retail & ecommerce operators: trace one real exchange and find where a request stops, waits, and gets re-keyed.

Run it on one real exchange

  1. Pick the last exchange or return that annoyed a customer. Not the process on the wall — the real one.

  2. Walk it step by step, in the order it actually happened. Every system, every screen, every wait.

  3. Write down who carried it at each step. If the answer is "a person copying," mark it.

The seven steps of an ordinary exchange

For each step, the worksheet asks four things: the system it's in, who carries it, how long it waits, and whether anything is re-typed.

  • Customer writes in — "these don't fit"
  • Agent finds the order
  • Return / exchange started
  • Stock for the new size checked
  • Label + tracking created
  • Refund or store credit issued
  • Status reconciled for the customer

Count the columns honestly. Every name in the "who carries it" column is a handoff. Every wait is a customer wondering. Every re-typed field is a chance to be wrong. The number that matters is the total handoffs on one ordinary exchange — if it is more than two, the integration in your stack is a person.

Read your score: five diagnostic questions

Ask these of the exchange you just traced.

1Where does the request sit still?
A step where nothing moves until a person picks it up — a queue, an inbox, someone's memory.
2Where is the same fact typed twice?
Order number, address, reason code — re-keyed into a second system that never talks to the first.
3Where do two systems disagree?
The portal says received, the warehouse says shipped, the customer hears a third story.
4Where does the customer hear nothing?
The silent gap between steps — no update, because no system owns the whole journey.
5Where do the exceptions pile up?
The cases that fall outside the flow and wait for the one person who can judge them.

Your three numbers

Write down handoffs, systems touched and fields re-typed. Then read where you are:

  • Mostly a human bridge. The work gets done because someone carries it — and stops when they do.
  • Connected in places. The seams still eat the day, and exceptions still wait on one person.
  • Ready to run as a process. Definitions agreed, flow visible end-to-end, people on exceptions — not keystrokes.

What good looks like

  • One agent runs the exchange end-to-end — inside your policies, across the systems you already have.
  • Your people own the exceptions and the decisions, not the copying.
  • Every action leaves a record your team can audit. Nothing lives in one person's head.

Bring your completed audit to a Design Your AI Crew session: we'll map your post-purchase flow onto a Domain Agent blueprint in one working session.

Get the fill-in worksheet

The PDF has the blanks to fill in as you go. One email, and it downloads right here.

Send me the worksheet →