The merchant requires a PO number for all orders, so I’m trying to figure out if we can require the PO number to be populated during checkout.
I’m not seeing PO number as one of the available fields in the checkout validation function:
It would be possible to use Checkout Blocks to add a required field, populate it as a metafield and then use flow on the backend to populate the PO Number field from that metafield.
But the problem there is that there’s no way to disable the native PO Number field in checkout, so you’d have duplicate PO Number fields.
Given that the Payment Customization API enables you to rename, reorder, and sort the payment methods available to buyers during checkout, it doesn’t seem relevant to @kalen’s question.
Apologies for the misunderstanding regarding the ticket. You are correct that with payment customization, we can rename and sort options. Additionally, we can hide payment option as needed.
The way we’ve achieved this is to use Checkout Blocks to add a required field called ‘PO Number Confirmation’. So there’s two fields, one is the native PO Number field, the second is a confirmation field - where the customer can enter the number in again.
Far from ideal but it does make PO numbers compulsory within the limitations of the checkout.
That’s actually a pretty solid idea given the constraints. That one simple label change on the field makes the double fields feel intentional vs super weird and buggy.