Use the stated period
Each figure belongs to the period printed beside it; do not treat a fixed historical window as a live counter.
Operating figures
Operating figures, definitions and limits
Each RyanFulfil figure below has a population, a period and a source. We keep the fixed-window operating measurements, the dated service window and the 15 August 2026 operating declarations apart, so nobody presents them as the same kind of figure.
Use the definitions, periods, populations and exclusions below when comparing these figures with another provider.
Measured operating window
All figures in this table cover orders paid 1 May – 3 October 2026 and use the same order-management dataset. The full breakdown explains the operating mix and the limits behind the headline numbers.
| Metric | Definition and limit | Source | Period |
|---|---|---|---|
| Paid orders recorded 197,000+ |
Paid order records in the two-team order-management exports for orders paid 1 May – 3 October 2026. Population: Paid order records in the stated exports. Exclusions: The order, unit and value totals are conservative undercounts: not every client’s orders run through our order-management system, orders from disconnected stores are lost from its records, and manually fulfilled orders are not included. Client-level and order-level records remain private. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Recorded order value US$11.6M+ |
The combined recorded order value for the same two-team export window, converted at fixed analysis exchange rates and rounded down for public display. Population: Paid orders in the measured export window. Exclusions: Recorded order value is not revenue or profit. The order, unit and value totals are conservative undercounts: not every client’s orders run through our order-management system, orders from disconnected stores are lost from its records, and manually fulfilled orders are not included. No store-level or order-level values are published. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Destination countries 86 |
Distinct destination-country values represented by at least one order in the measured exports. Population: Paid orders in the measured export window. Exclusions: Observed destination coverage for the period, not the list of countries currently eligible for shipping. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Recorded units 420,000+ |
The summed item quantities attached to the paid orders in the measured exports. Population: Units attached to orders in the measured export window. Exclusions: Published as a rounded aggregate; product, store and client-level detail remains private. The order, unit and value totals are conservative undercounts: not every client’s orders run through our order-management system, orders from disconnected stores are lost from its records, and manually fulfilled orders are not included. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Median payment to dispatch 1.6 days |
The median elapsed time between the payment event and the carrier-handover event. Population: Paid orders in the measured export window. Exclusions: A median, not a promise. It is not delivery time and says nothing about any single order. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Orders with no refund status recorded Over 99% |
One minus the share of measured orders carrying the refund status in the analysed export. This is a recorded-status snapshot, not a final outcome rate; newer orders may acquire a refund status later. Population: Paid orders in the measured export window. Exclusions: A refund status is not the same as a defect, reship, partial credit or customer-service complaint. |
Order-management records | Orders paid 1 May – 3 October 2026 |
| Orders held for stock replenishment About 2% |
Orders carrying an out-of-stock or replenishment-hold status divided by measured orders. Population: Paid orders in the measured export window. Exclusions: A stock-wait status is not a general late-dispatch or service-failure rate. |
Order-management records | Orders paid 1 May – 3 October 2026 |
Read the full order-data breakdown →
Dated service window
This is a different dataset: client-request records from both teams. Reply speed measures acknowledgement; it does not claim that the problem was resolved at the same moment.
| Metric | Definition and limit | Source | Period |
|---|---|---|---|
| Median first reply in working hours 23 minutes |
Median elapsed time from request arrival to first relevant acknowledgement, filtered to working-hour arrivals. Population: 704 logged client-request components across both client teams. Exclusions: Overnight arrivals are excluded from the median. Across all arrivals, 95% received a reply within 24 hours; about one in five in-hours requests took more than half a day. |
Client-request records | 17–22 August 2026 |
| Requests without a confirmed service breach 99.7% |
Client-request components not classified with a confirmed breach state, divided by all components in the stated period. Population: 704 logged client-request components across both client teams. Exclusions: Not a parcel-success, defect-free or satisfaction rate. Open items waiting on suppliers, carriers or stated cut-offs are separate. |
Client-request records | 17–22 August 2026 |
Read the operating terms and exception-ownership method →
Operating declarations dated 15 August 2026
These are dated operating declarations, not fixed-window measurements. We list them separately so nobody mistakes the declaration for the measured order window (orders paid 1 May – 3 October 2026).
| Metric | Definition and limit | Source | Period |
|---|---|---|---|
| Active clients 500+ |
Operating count declared by RyanFulfil on 15 August 2026, separate from the measured order window (orders paid 1 May – 3 October 2026). Population: Client accounts treated as active when the declaration was made. Exclusions: Account-level records are private, and the declaration is not part of the measured order dataset. |
RyanFulfil operating declaration dated 15 August 2026 | Operating declaration dated 15 August 2026 |
| Daily orders 4,000+ |
Daily scale declared by RyanFulfil on 15 August 2026, not the arithmetic daily average of the fixed export window. Population: Order flow across the operation when the declaration was made. Exclusions: A dated operating declaration rather than a daily time series for the fixed window. |
RyanFulfil operating declaration dated 15 August 2026 | Operating declaration dated 15 August 2026 |
Route availability
Route availability is maintained separately from the operating declarations and from the measured order window (orders paid 1 May – 3 October 2026). It remains subject to the product, weight, destination and carrier checks in your quote.
| Metric | Definition and limit | Source | Period |
|---|---|---|---|
| Countries eligible for shipping 150+ |
Countries for which a route may be available, subject to current product, weight, destination and carrier checks. Population: Current route-eligibility coverage. Exclusions: Eligibility is not a shipment observed in the fixed window or a guarantee for every product or postcode. |
Public destination table and route availability | Current route claim |
What these figures cannot tell you
Not a route guarantee
An observed median or eligible country does not promise the same result for every product, carrier, postcode or customs event.
Not a client result
Operating volume does not establish profit, conversion, retention or the outcome of a particular store.
Ask for current order terms
Routing, costs and capacity can change. Your quotation sets the terms for your product, destination and order date.
Download the figures and definitions
The same public register is available as metrics JSON. A smaller company facts file points back here for definitions. Use these files to keep the definitions with any figures you compare.