Otherwise Solutions built one connected commerce system for Hurricane, a premium perfume brand: an online store, native-feeling iOS and Android apps, CRM integration, and a cashback loyalty program. Storefront, customer accounts, orders, and loyalty live in one dataset — one system instead of five disconnected tools.

Who is Hurricane

Hurricane is a premium fragrance brand selling its own product lines — perfumes and shower gels — direct to consumers online. The catalog is presented the way a perfume house presents itself: named scent lines described by top, heart, and base notes, not marketplace listings. For a premium brand, the buying experience is part of the product, which set the bar for both design and engineering.

The starting point

A direct-to-consumer brand quickly outgrows a plain storefront. Repeat buyers want accounts, order history, favorites, and a reason to come back; the brand wants loyalty mechanics, a CRM view of its customers, and a place on the customer's phone. Bolted together from separate services, that becomes the classic disconnected stack — where customers, orders, and data get lost between tools and nobody owns the full picture.

What we built

The online store

The public shop runs on WordPress: catalog, product pages with fragrance notes, special offers, and checkout with online payments. The team manages products and content themselves on a platform their staff already knows — adding a product does not require a developer.

A customer dashboard with loyalty built in

Signed-in customers get a fast, app-like dashboard built in Svelte: the catalog with favorites, order history and status, a support channel, notifications, and a personal profile. Signing in takes one tap with Google. The loyalty program lives right there: purchases earn cashback, the balance is visible in the account, and it spends on future orders — a reason to return that the brand owns, instead of renting from a third-party loyalty service.

iOS and Android apps from the same codebase

The dashboard ships as real iOS and Android apps through Capacitor — same code, same data, no separate app project to maintain. The brand gets an icon on the customer's home screen and push-ready infrastructure for a fraction of a native-app budget, and every feature ships to web and mobile at once.

CRM integration and one API underneath

A custom PHP API connects the storefront, the dashboard, the apps, and payments — and feeds the CRM, so every customer, order, and cashback balance is visible to the team in one place. Follow-ups, support, and repeat-purchase work run on real data instead of inbox archaeology. This is the layer where commerce automation starts paying for itself: the system keeps the records so people can do the selling.

What the system does now

  • Customers browse, buy, track orders, and spend cashback in one place — web or mobile.
  • The team manages the catalog in WordPress and sees every customer and order in the CRM.
  • Loyalty runs automatically: purchases accrue cashback, balances update in the account.
  • Web, iOS, and Android run from one codebase, so features ship everywhere at once.

This architecture — a familiar CMS for the team, a custom app layer for customers, CRM and one API underneath — fits most product brands that have outgrown a basic store. It is the scope conversation we start every development project with.