Person paying at a counter with a card terminal

When ‘purchase’ means three different things

Open three dashboards in a mid-size Malaysian commerce app and you may find three “purchase” rates for the same week. Marketing counts the moment a checkout ID is minted. Finance waits for settlement. Ops watches the first successful courier handoff.

None of those people is wrong. The conversion conversation breaks when the same word is used without saying which moment it marks.

A quick alignment ritual

Before arguing about a dip, write the three timestamps on a whiteboard:

  1. Order record created
  2. Payment captured (or COD confirmed)
  3. Fulfilment started

Then ask which one the current OKR actually needs. If the board cannot answer in one sentence, pause the debate and fix the labels in the export.

Why festival weeks expose the gap

During peak sales, payment providers and COD confirmation queues stretch. Orders appear quickly; captures lag. A chart keyed to order creation looks triumphant while customer care fields “I paid but…” tickets. Teams that aligned definitions before the festival waste fewer hours blaming seasonality.

What we do in audits

Our measurement check always begins with the purchase family of events. If names disagree with the live confirmation screen, we stop trusting drop-off percentages until the dictionary is honest.