Hi there, Paul! Thanks for reaching out and I’m sorry you’re bumping into this issue.
It’s definitely a bug on our end and we’re working to fix it. There’s a ticket in our system to have it cleaned up in the next release, which is coming up next week.
In the meantime, you can try out the suggestion in this thread to hide the incorrect cost from displaying using CSS.
Sorry again for the trouble–I’ve noted this thread so we can try to follow up with you directly here when it’s released. Until then, please keep your eyes open for the release.
Cheers,
Geoff