Track record

Roumaan

Built and operated a multi-category online commerce business in Oman.

Founder and operatorOman2014 to 2018
01

Executive overview

Built and operated a multi-category online commerce business in Oman.

Roumaan established Haris's operating base in digital commerce: build the proposition, own the daily decisions and keep growth connected to order economics.

02

Market context

Roumaan was built in Oman between 2014 and 2018, when broad online retail was still early and customers could not assume that a digital catalogue reflected stock that could actually be delivered. The opportunity was larger than putting products on a website. The business needed to make assortment, availability, payment, order handling and fulfilment work as one promise.

The operating history that can be stated publicly is first-party digital commerce. Roumaan traded online, recorded orders and built a customer base. Later marketplace planning explored how third-party supply could extend the proposition, but that work is kept separate from the results of the original retail operation.

03

Role and mandate

Mandate

Create a credible online retail proposition in a market where assortment, stock accuracy and fulfilment still had to be built together.

Operating problem

A multi-category proposition creates an immediate coordination problem. Each category has different product data, replenishment patterns, delivery constraints and return behaviour. A broad catalogue can attract demand, but poor availability or weak order handling quickly turns range into a service liability.

The commercial problem was therefore not traffic alone. Each completed order had to carry enough product margin to absorb payment, picking, delivery, returns, customer care and acquisition. Growth that increased cancellations or service work without improving contribution would have made the business busier without making it stronger.

04

What was built or fixed

Haris shaped the proposition, category choices and operating model, then worked through the daily decisions behind catalogue quality, merchandising, order flow and fulfilment. The business needed a single view of what was sellable, what had been ordered and what could be completed within the service promise shown to the customer.

The model was deliberately practical. Central control over catalogue and order operations reduced ambiguity while the customer proposition was still being proved. Marketplace expansion could only make sense after seller admission, stock truth, commissions, service responsibility and settlement had their own operating design.

05

Commercial contribution

The relevant equation was completed-order contribution: selling price less product cost, payment cost, fulfilment, delivery, returns, service recovery and attributable acquisition. Revenue and order count were useful signals, but neither could answer whether a category or customer cohort earned cash.

Working capital sat beside the order P&L. Inventory bought too early could make the digital range look stronger while locking cash into slow stock. The commercial review therefore needed category margin, stock age, sell-through and fulfilment quality in the same conversation.

06

Operating model

How the work ran

Category and merchandising decisions sat close to stock and demand. Order operations coordinated availability, customer communication and fulfilment. Service issues fed back into catalogue and supplier decisions rather than remaining isolated in customer care.

A modern version would preserve those accountabilities while using catalogue automation, live inventory APIs and exception queues to reduce manual work. People would still own price, supplier commitments, refunds and any decision that changes the customer promise.

Decision discipline

Roumaan established Haris's operating base in digital commerce: build the proposition, own the daily decisions and keep growth connected to order economics.

07

Technology and operations

The original operation used a commerce content layer, product catalogue, customer records and order reporting. The technology supported the retail model; it did not replace the work required to maintain product information, confirm stock and complete orders.

The current architecture would separate product, inventory, price, order and customer-service records behind APIs. AI could identify missing attributes, classify enquiries and summarize exceptions, but the source systems would remain authoritative for stock, money and order status.

08

Results and evidence

Verified record

Roumaan operated as a live online retailer with recorded orders and customer registrations. That is the public evidence used on this site. No unpublished revenue, profit, market-share or third-party marketplace result is presented.

The lasting operating lesson was direct: digital commerce is a trading and fulfilment business before it is a traffic business. The catalogue is credible only when the operation can fulfil the promise attached to it.

What is not claimed

No unpublished revenue, profit, market-share or broad transformation percentage is added to the record.

09

Business relevance and lessons

  • Build stock truth before catalogue scale.
  • Measure completed-order contribution, not checkout activity alone.
  • Treat service failures as commercial data.
  • Keep first-party and marketplace economics separate.
  • Let automation prepare work, while operators retain consequential decisions.

Related use cases