Struklio Update 1.0.4

Update 1.0.4 is the fourth update to Struklio.

This release focuses on the interactions that happen after someone places an order, books a service, completes a payment, or starts a conversation. These flows may appear simple on the surface, but they require several parts of the application to remain synchronized.

With this update, we fixed six issues across payments, bookings, restaurant orders, notifications, and messaging.

A Clearer Experience After Payment

After a successful payment in Review Mode, the project previously returned to Builder Mode immediately. This could make it unclear whether the payment had actually been completed or whether something had gone wrong.

The payment flow now behaves as intended and gives the user a clearer continuation after payment confirmation.

Improved Restaurant Notifications

Restaurant providers now receive an in-app notification when something requires their attention, such as a new chat message or an order status change.

The notification modal is triggered, and the notification count is displayed beside the bell icon with a colored background. The implementation still has some smaller edge cases that we will continue improving, but the core notification flow is now available.

Restaurant Order Statuses Now Stay Synchronized

When a restaurant changed the status of an order, the new status was not always delivered to the customer who placed it.

This connection is essential: customers need to know their order has been received and that something is actively happening. Update 1.0.4 restores this synchronization, allowing status changes made by the restaurant to appear correctly for the customer.

Service-Provider Chat Delivery Fixed

Customers who booked a service could attempt to contact the provider, but their messages were not delivered correctly.

The messaging flow has now been fixed, and messages are sent to the correct service provider.

Bookings Now Appear on the Admin Dashboard

Service bookings were generating notifications, but the customer and booking data were not synchronized correctly with the provider’s admin dashboard. This meant that the booking itself might not appear, even though a notification had been received.

Bookings and their associated customer data now render correctly on the admin dashboard.

Time Slots Are Reserved During Payment

Previously, a time slot was only checked after payment had been completed. If another customer booked the same slot during that process, the payment could finish before the user received a 409 — This time slot is already taken error.

Update 1.0.4 reserves the selected time slot while payment is in progress. Already-booked slots are also shown as unavailable instead of being presented as valid options.

The current reservation logic operates per service. Expanding this further to account for provider-specific availability is one of the next improvements we will make.

Building the Connections Behind the Interface

Update 1.0.4 is primarily about reliability.

A booking needs to reach the provider. A message needs to reach the right conversation. An order-status change needs to appear for the customer. A payment needs to produce a clear result.

These improvements make Struklio’s restaurant and service-business templates feel more connected, predictable, and ready for real-world testing.

This is the fourth update to Struklio—and we keep building.