We are in the middle of the process of toying around with meta data having already pushed a trade-in and inbound sales process (buy a repair and ship in your smartphone). We felt a need for a PO-Number field that stores the customer reference in order meta data. Should we bring that to core and starter? The field looks up if the address field is filled out and offers a PO field if company is not empty.

Hi there, Your approach to integrating a PO-Number field based on the address validation logic makes sense, especially for B2B transactions. Regarding whether to bring this to core and starter, I see value in making it a standard feature, particularly if multiple clients have expressed the need for structured customer references in order metadata. If this aligns with broader use cases, we can evaluate incorporating it into the core. Otherwise, keeping it as an optional extension could provide flexibility. Let’s discuss further to ensure it meets your requirements effectively. Looking forward to your thoughts. Best,

Hey Kouki, the idea is to provide a logic through metadata to give an example integration. The logic is already mostly there.

Got it! If the logic is mostly in place, we can focus on refining the metadata structure to serve as a clear integration example. Would you like any adjustments or enhancements to improve usability, or is this mainly about documenting and showcasing the approach?

Man, I don’t know if you know that but we provided that feature upstream two months ago

ok

Given that the starter frontend represents a blueprint for solidus features we should at least provide an example for it