Orders were split across too many steps

Blomma is a flower and gift shop in Kuwait. The team took orders through Shopify and WhatsApp, kept details in spreadsheets, and tracked dispatch on paper. Staff copied order information by hand. Account reconciliation alone took 44 hours each month. Shopify could not support the custom delivery flow, add-ons, and operations the business needed.

We started by mapping how work moved from an order to delivery. The team needed to see the same order information while preparing a gift, assigning a driver, checking stock, and reconciling accounts. That process map shaped the system. It gave the build a clear center: one order record that could support both the customer journey and the work behind it.

The order had to connect the store and operations

We built a custom commerce site and an operations tool. The store supports delivery choices, custom requests, add-ons, and greeting card previews. Staff can assign orders, plan driver routes, manage inventory and payroll, and review reports from the same platform. Customers can see a preview of the gift before delivery, and staff can check stock before they promise an item.

We could have kept Shopify for sales and added a separate operations tool. That would leave delivery work further from the order and stock details. Instead, we fit the system to Blomma’s delivery process. The team designed screens in Figma, then built the site and operations app with Bubble. The project also used Xano and Shopify. The platform brought six disconnected tools into one place and removed manual data entry.

This is a useful boundary for automation. A delivery action depends on the order, the item, the stock, and the destination. If these details live in separate records, staff must join them by hand. Connecting that information makes the next action easier to define and keeps customer options tied to the work needed to fulfil them.

The build focused on the custom workflow

Bubble let us put working screens and workflows in front of the team within the six-week build. A fully custom codebase would give us more control over every part of the system, with more engineering work to deliver the same first version. The immediate value was in getting the order and delivery process right.

The trade-off is dependence on the platform’s workflow and data features. Changes to delivery options can affect order handling, dispatch, and reporting together. That makes the process map useful after launch too. A new customer option needs a defined path through the operation before it belongs in the storefront.

Reconciliation took less time

Monthly account reconciliation fell from 44 hours to 2 hours. The platform was delivered in six weeks. The new system also reduced manual entry and data errors. It gave the team one place to manage orders, deliveries, inventory, payroll, and reporting.