Once again, a bug with B2B sailings, this time related to Ocean Medallion order.
The documents flow is correct and the booking numbers/dates are correct. Go into the Medallion order flow, the date of the first sailing is shown. Make the appropriate selections, go to choose a shipping method. Ship to home is greyed out and marked “not available”.
Call support. They ask me to finalize the order and they’ll cancel it and we can try again. We do so. Same issue. We cancel again.
On examination during the third try, we realize there’s a bug: the voyage displayed at the start of the Medallion order process is (correctly) the first date, but is (incorrectly) displaying the second booking number.
Using the web interface, I can log in, but it forces the Link Booking flow immediately after, which reports that the booking number has already been claimed.
A ticket has been opened. We’re sufficiently far out from departure that a week won’t matter, and the booking briefly blinked into Green Lane between the (malformed) order and its cancellation.
B2B sailings are not a corner case. They represent clients who like the product well
enough to order seconds before they’ve even got the first helping. This is our third set of B2Bs since the restart where something has required a support ticket prior to departure. It’s one thing to have endless trouble supporting the endless permutations and combinations of device hardware and OS and app versions, but this is still underlying data quality issues in the back end, which mystifies me.