Store API events and revenue recognition

Event boundary

Cart and checkout events describe funnel behavior. Order creation states commercial intent. Payment, fulfillment, cancellation, and refund revisions determine whether and when revenue is recognized under the configured accounting policy. Contribution = recognized net sales minus qualified variable channel costs; accepted events alone never satisfy this formula.

Integrity requirements

A batch is scoped to one credential and workspace, signed, size-limited, schema-versioned, replay-safe, and ordered by stable event, order, line, revision, and idempotency identifiers. Receipt status separates accepted, sandbox_validated, processed, rejected, and published outcomes.

Unavailable state and example

A missing payment, unsupported currency, stale revision, failed signature, replay, or unreconciled source keeps revenue and profit unpublished.

Example: a sandbox order and payment batch can pass signatures and schema with sandbox_validated status while producing zero financial rows. A later approved live source must still reconcile order count, status, amounts, refunds, and costs against an independent report.