← All field notes

Automation · CASE NOTE ·

Before I automate ecommerce work, I decide what should stop the workflow.

Validation, exception handling and human review in a product-data workflow across four ecommerce platforms.

When I was preparing product data for Shopify, Shopee, Lazada and TikTok Shop, one question mattered early: what should the workflow do when the data was wrong?

Some fields are easy to clean or standardise. A product ID can be trimmed. A quantity can be checked against an expected format. Other records need someone to check the source before they go any further.

01 / OBSERVATION

The product-data workflow needs somewhere to stop

A missing SKU needs attention. So does a duplicate identifier, an invalid quantity or a required platform field that cannot be mapped confidently. I define those stop conditions before spending too much time on the happy path.

  1. Source
  2. Standardise
  3. Map
  4. Validate

Records that pass move into prepared output and human review. Ambiguous, invalid or conflicting records go to exception review, then return to the appropriate output path after resolution or approval.

In a spreadsheet, someone might notice that a SKU looks strange and check it before continuing. An automated workflow needs an explicit rule or review step to preserve that decision.

02 / OBSERVATION

Human review is part of stock reconciliation too

For stock reconciliation, the calculation is opening stock + deliveries − sales. A negative balance tells me to investigate the inputs; it should not quietly become the master stock figure.

Even a plausible balance still needs source verification. A completed calculation and an approved stock update are separate steps.

03 / OBSERVATION

Preparing product data across four platforms

The work covered 250+ SKUs across Shopify, Shopee, Lazada and TikTok Shop. The workflow included field cleaning and mapping, with exception handling for uncertain records.

I still review the output before publishing. AI can help prepare a mapping or draft a rule, but it does not decide that a record is safe to use.

04 / OBSERVATION

Try the review boundary with a small sample

The stock reconciliation sample in Projects uses fictional quantities and a local balance check. Change the inputs, run the check, and see whether the balance needs review. Editing an input clears its old result, so it has to be checked again.

The workflow handles repeatable preparation steps and keeps human review before publishing.

Try the stock reconciliation sample

TRACE

Capture stopped

Local only · clears on refresh

Earlier records remain until cleared or refreshed.

0 interactions recorded

Capture stopped. Turn TRACE on to record approved interactions.