A wholesale portal should capture the buyer's PO at quote accept, not chase it after conversion. Week one on Parcel Build is that first working version: required customer PO field on accept for accounts that need it. You own the code. Flat monthly. See custom software for wholesalers. If attach customer PO when accepting a wholesale quote is the gap, start a free 30-day build.
When should week one require a customer PO on quote accept (and when can it stay optional)?
Week one can cover a PO field on accept, require it for accounts that need it, and pass that number onto the converted order. Blanket PO renewal workflows, punchout cXML PO, and EDI 850 can wait until that accept path earns its keep.
On Parcel Build, week one is a first working version of that path. Flat monthly. You own the code.
Why accepting without a PO and emailing later creates orphan orders and credit risk
The buyer accepts the quote. The PO is still missing. Credit holds the order. Ops emails for the number. The converted order sits without a reference purchasing will recognize.
Requiring the customer PO on accept puts the number on the order at conversion. Chase after the fact drops.
What stays out of month one
Defer blanket PO renewal workflows as primary. Defer punchout cXML PO as primary. Defer EDI 850 as primary. Month one is a required customer PO field on quote accept for accounts that need it.
FAQ
Is PO on quote accept the same as default PO number rules on checkout?
No. Default PO rules apply when the buyer places a portal order at checkout. PO on quote accept captures the number when the buyer accepts a quote. They can sit together later. Week one can prove PO on accept without cloning checkout PO rules as the primary path.
Does week one need PO document file upload before a PO number field on accept is useful?
No. Week one can require a PO number on accept and carry it to the order. File upload of the PO document can wait until the number field earns its keep.
Next step
If attach customer PO when accepting a wholesale quote is what feels hardest, start a free 30-day build. Name that gap on the form. We scope a free 30-day build on that problem: first working version in week one, flat monthly after if you want to continue.