Multi-Channel Commerce Report
Aggregated from 2,944 orders placed between july–september 2026 at Markapia, a multi-brand fashion retailer running on Bulutegra. The aim is to put numbers on what actually happens across a selling day.
Published: September 7, 2026 · Version 1 · Permanent link: https://bulutegra.com/en/report/multi-channel-commerce/
When do orders arrive?
Order flow peaks twice a day: mid-afternoon and late at night. The busiest hour is 22:00 with 208 orders, and the four hours between 22:00 and 01:00 carry 20% of all orders.
Two operational consequences follow. Orders placed overnight can only ship the next morning if the order transfer runs overnight too. And a setup that refreshes stock and prices only during office hours serves a fifth of its orders on stale numbers.
See the data as a table
| Value | Orders |
|---|---|
| 00 | 146 |
| 01 | 73 |
| 02 | 39 |
| 03 | 28 |
| 04 | 17 |
| 05 | 13 |
| 06 | 21 |
| 07 | 38 |
| 08 | 63 |
| 09 | 119 |
| 10 | 128 |
| 11 | 170 |
| 12 | 155 |
| 13 | 200 |
| 14 | 173 |
| 15 | 186 |
| 16 | 158 |
| 17 | 140 |
| 18 | 159 |
| 19 | 133 |
| 20 | 162 |
| 21 | 164 |
| 22 | 208 |
| 23 | 169 |
The week is almost flat
There is less variation between days than most planning assumes. The busiest day is Wed with 473 orders, only 21% above the quietest. There is no weekend dip: Saturday and Sunday sit in the same band as weekdays.
In practice, running a marketplace operation as a weekday job pushes more than a quarter of the volume into the next working day.
See the data as a table
| Value | Orders |
|---|---|
| Mon | 373 |
| Tue | 414 |
| Wed | 473 |
| Thu | 418 |
| Fri | 404 |
| Sat | 378 |
| Sun | 402 |
Basket: eight in ten orders hold a single item
84% of orders contain one item, and the average basket is 1.23 items. The average order value is 741 TRY against a median of 526 TRY, so a small number of large orders pulls the average up.
A single-item basket means shipping cost lands on every order. In that shape, profitability is driven by contribution per item and the return rate, not by volume.
See the data as a table
| Value | Orders |
|---|---|
| 1 | 2,470 |
| 2 | 351 |
| 3 | 63 |
| 4 | 29 |
| 5 | 9 |
| 6 | 6 |
How do orders end?
Within the observation window 75.2% of orders were delivered, 19.6% were still in transit or being prepared, and 3.5% were cancelled.
Return rates cannot be read from this data: a return is opened days after delivery, so orders near the end of the window have not had time to generate one. That is why no return percentage is published here. Cancellations happen close to the order itself and are measurable.
See the data as a table
| Status | Orders | Share |
|---|---|---|
| Delivered | 2,215 | 75.2% |
| In transit / preparing | 577 | 19.6% |
| Cancelled | 104 | 3.5% |
The remaining 1.6% are orders with a return in progress. They have not matured and should not be read as a rate.
How available are the channels?
Channel connections were polled 7,830 times over the same period and 1.1% of those calls returned an error. The average response time was 1,290 milliseconds.
The error share looks small, but a single silent outage means lost sales until somebody notices. A setup that does not watch each channel’s last successful run learns about that slice from customer complaints.
Every number here comes from data already visible in the Bulutegra panel. If you would like to see the same breakdowns for your own operation, we will send you demo access.
Download the report as PDF › · Download every series in this report as CSV ›
See it before we explain it.
We will send you login details for a working copy of the panel; explore it yourself, then let’s talk.