I was thinking that the one-page checkout might solve for this, so that’s good to hear. Could you add a separate component to the customer info as a checkout UI extension?
Topic summary
Goal: apply an automatic order-level discount based on customer tags as soon as a shopper lands in checkout after email prefill via cart redirect.
Observed behavior: with multi-page checkout, the Order Discount function (using buyerIdentity → customer tags) only shows the discount at the Shipping step. A page refresh on the Information step also reveals the discount, suggesting timing/refresh issues. Switching to one-page checkout shows the discount immediately upon landing.
Suggestions discussed: consider adding a Checkout UI extension component on the customer info step to communicate discount status. No mechanism was identified to control the exact timing of when the order discount function applies within multi-page checkout.
Decision: client accepted one-page checkout, resolving the initial timing concern.
New issue: the discount function later stopped running entirely. It appears registered (IDs match in GraphiQL and the app’s extension page), but no runs/logs occur at the purchase.order-discount.run target. Checkout shows a 401 from a private_access_tokens request. Reinstalling/recreating the app did not help.
Status: unresolved; awaiting guidance on why the function no longer executes despite being registered.