Special-price handover

The Lifecycle

Transitions Explained

Migration leaves an audience-based cell and handover context for each former special price. The documented completion belongs to Commerce, which must create the audience and eligibility binding and record realization. The handover schema provides a timestamp for that outcome, but does not establish an implemented consumer.

What Cannot Happen

Accounting offers no command to edit or realize handovers. Deleting a product cascades to its handovers. The examined sources establish no Commerce operation for undoing realization.

Concurrency and Timing

Completion timing, retry behavior and consumer concurrency remain unknown. Once Commerce's register exists, an HTTP edit resubmitting a migrated cell requires an active audience there. The domain function applies different admission checks; Product must settle editing during that transition.