Event-driven architecture: handling eventual consistency in the UI

Our backend team is heavily invested in an event-driven architecture, which works great for scalability and decoupling. However, our frontend team is really struggling with the implications of eventual consistency. For example, a user creates an order, and the UI immediately reflects it, but the backend processes it asynchronously. If they refresh too quickly, the order might not appear, or its status might be incorrect. How do other teams bridge this gap between an async, eventually consistent backend and a synchronous, immediate-feedback user experience? Are there common patterns for handling this on the frontend? We've considered things like optimistic UI updates and polling, but I'm looking for more robust strategies that don't involve a huge amount of custom state management on the client side.