When a hub manager creates a new order for a customer who has credit available, they need to access the Payments tab to apply that credit. However, clicking the Payments tab redirects them to Customer Details with the message:
▎ “Please fill in the customer details before proceeding to payment.”
This is misleading — the customer details ARE already filled in. The screenshot below shows the order number, the cart state confirmed via browser console, the misleading message, and the 302 redirect.
Root cause
The Payments tab guards against orders that haven’t progressed far enough in the checkout flow. The order stays in cart state during admin order entry until it is explicitly advanced. The guard was not designed with the admin order entry workflow in mind.
Workaround
Clicking Update and Recalculate Fees advances the order state and takes the hub manager directly to the Payments tab. However there is no indication in the UI that this step is required.
This came up specifically in the context of hub managers applying customer credit to orders, following on from the Phase 1 customer credit implementation.
Recommended approach
The most practical fix appears to be improving the error message to tell hub managers what they actually need to do - click “Update and Recalculate Fees” rather than pointing them back to customer details they’ve already filled in. A longer-term improvement could auto-advance the order state when customer details and items are complete.
Questions for the community
- Is the “Update and Recalculate Fees” step an expected part of the admin order entry workflow, or is this an oversight?
- Is an improved error message sufficient, or should the order state advance automatically?
- Have hub managers in your instance encountered this issue?
Type of Feedback
Proposal / Discussion (This is something than requests input and encourages active discussion)
Feedback round
Proposal / 1st iteration
Who to ping?
@MyriamBoure @lin_d_hop @Kirsten @tschumilas @dcook @Evonne @bernie_nz @emilythericky @Karla @BethanOFN @nicotentin
Deadline
1 week from date of post (after deadline, no further community feedback accepted)
29 June, 2026.