Optimized for Desktop, mobile version coming soon :)
Reduced order-to-pay time in a B2B wholesale marketplace
by reframing a mandatory enforcement feature into a buyer-choice experience
Web App (B2B)
Sr. UX / Product Designer
Rapid Prototyping
Usability Testing
A/B Testing
2025
A B2B wholesale marketplace where buyers bid on auctions and pay after winning. Payment has always been buyer-initiated — meaning buyers manually log in and pay after an order is created. This creates a structural delay baked into every transaction.
Reduce order-to-pay time from ~2.2 days → under 24 hours to improve cash flow and fulfillment speed.
As long as payment is buyer-initiated, time-to-pay won't compress meaningfully. The only lever: make payment happen automatically after a bid is won.
Four payment methods in different stages — each with different speeds, risks, and adoption rates:
| Pay Method | Launched | % of Orders | Time-to-Pay | Risk |
|---|---|---|---|---|
| Wire Transfer | 2008 | 25–35% | 50–75 hr | Offline process |
| ACH | 2023 | 50–75% | 20–50 hr | High fraud rate |
| Net Terms | Apr 2025 | 8–10% | 0–12 hr | Application needed for 1st timers |
| Credit Card | Planned Q1 2026 | N/A | N/A | Chargeback risk |
Direction set by Product & Leadership:
Mandatory auto-charge once an order is created
Start with one seller for a controlled pilot rollout
Net Terms only to reduce risk/complexity and ship the MVP sooner
Before designing anything final, I identified three core unknowns to validate:
Unknown 01
Buyer Acceptance
How buyers feel about mandatory auto-charge
Unknown 02
Payment Methods
Which method buyers expect to use if charged automatically
Unknown 03
Buyer Choice
Should buyers ever have a choice? (for later)
Payment was the final manual step — buyers had to actively return and pay after winning an auction.
Two changes to enable auto-charge:
Mention auto-charge before bidding (at the Listing Detail Page) to set expectation
Surface shipping & payment settings in the Bid Confirmation, so everything is set before the auction ends
Setting expectation before bidding — an indication of auto-charge shown on the Listing Detail Page.
Entry Point — Listing Detail Page
Bid Confirmation — Shipping + Payment
During Stage 1 research, a critical finding emerged: wire transfer accounts for ~40% of GMV. These buyers couldn't be auto-charged (offline workflow), so the mandatory direction required exemption logic — thresholds, whitelists, or other workarounds.
This prompted a reframe: instead of exemptions for wire buyers, what if we gave all buyers a choice?
Direction 1
Mandatory
Buyers have no option. System auto-charges after winning. Wire-only buyers need exemptions (threshold / whitelist).
Direction 2
Optional
Buyers can opt in to auto-charge before confirming a bid. No buyers excluded — including wire-only buyers.
Both directions were prototyped for A/B testing. Key screens: entry point on the Listing Detail Page and the Bid Confirmation modal.
Direction 1 — Mandatory
Direction 2 — Optional
Participants were split into two groups to control for order bias. Both groups rated each direction and selected a preference.
Even when given the option to opt out, buyers' expected opt-in rate was ~93.75% — meaning choice didn't sacrifice adoption.
Mental Pattern
Choice Increases Comfort
Participant DD rated Dir. 1 as "Uncomfortable" — but in Dir. 2 gave a 4/5 on willingness to opt in to auto-charge. The act of choosing changed the emotional experience entirely.
Behavioral Pattern
Thresholds Change Bidding Tactics
In Dir. 1, wire-only buyers said they'd wait for an order to exceed the threshold before bidding — to avoid being auto-charged. In Dir. 2, those same buyers said they'd bid immediately.
Rather than betting everything on one direction upfront, I proposed a phased rollout to build evidence before committing.
Phase 1 — Launch
Start with Optional (Dir. 2)
Open to all buyers and sellers. Collect real adoption data early.
Phase 2 — Learn
Test Mandatory with a Pilot Seller
Once buyers are familiar with auto-charge, establish baseline data to compare gain vs. loss.
Future Phases — Iterate
Data-Driven
Iterate based on evidence. Optional/Mandatory could even become premium features for buyers and sellers respectively.
The research supported Optional. The shipped rule: ACH / Net Terms = auto-charge; Wire = manual. Rather than building complex exception logic for wire buyers, the team moved to a cleaner model — payment method itself becomes the opt-in mechanism.
Impact: shifted the team away from exception-heavy enforcement logic toward a more transparent, buyer-respectful design.
In hindsight, I wish I'd run a quick "Optional" test even when the original scope was tightened to mandatory-only. Validating the alternative earlier might have changed the initial direction sooner.
Impact isn't always "my solution shipped." Sometimes it's "the team made a better-informed call."