Preparing for lift-off

in 3, 2, 1..

Launch sequence active
14ms
Light Speed Technologies

Ecomness: One Order Flow for Sellers, Suppliers, and Operations

A cash-on-delivery marketplace connecting suppliers, sellers, five carriers, stock, returns, and payments in one order flow.

Ecomness: One Order Flow for Sellers, Suppliers, and Operations

Ecomness is a Tunisian dropshipping marketplace built for cash on delivery. Suppliers provide the products, sellers generate customer orders, carriers deliver them, and the Ecomness team controls the operation. The platform had to keep every party on the same order record.

The problem

Cash-on-delivery orders do not end at checkout. An order can be confirmed, prepared, collected, delivered, refused, returned, or exchanged. Every status changes stock, carrier responsibility, seller fees, and the amount each party is owed.

Before building, we mapped those real states and the decisions attached to each one. The platform could not assume every parcel would be delivered successfully.

What we built

We delivered three connected workspaces:

  • Suppliers publish products, set available quantities, and see how their stock is moving.
  • Sellers choose products, add them to their stores, submit customer orders, and follow delivery and payment status.
  • Ecomness operations manage products, sellers, suppliers, orders, pickups, carrier updates, fees, returns, exchanges, stock, and payouts.

Five delivery companies feed status updates into the same order history, so the team does not need to reconcile separate carrier dashboards before helping a seller or customer.

The order flow

  1. A supplier publishes a product and available stock.
  2. A seller selects it and submits a customer order.
  3. Ecomness confirms the order and sends it into preparation.
  4. The assigned carrier collects the parcel and reports each delivery state.
  5. Delivery, refusal, return, or exchange updates stock, fees, and the payment ledger.

Every participant sees the part of that history relevant to their role.

Exceptions are part of the product

Returns, refusals, failed delivery attempts, and exchanges are normal in cash-on-delivery commerce. We treated them as first-class workflows with timestamps, ownership, stock movements, and financial effects. The operations team can see what happened and what action is still required without rebuilding the story from messages and spreadsheets.

The result

Ecomness now operates product sourcing, seller orders, carrier delivery, stock, returns, fees, and payouts from one platform. Sellers receive a clear order status. Suppliers can follow demand and inventory. The operations team can resolve exceptions from a complete history instead of checking several disconnected tools.

// Discuss your project

Have a product problem to solve?