Skip to content

Main content

Random Warehouse Order Fulfillment Dataset Generator

Construct synthetic orders with actual ordered/shipped line quantities and independent on-time draws, then delegate complete-line fill, backorder and delivered-order OTIF metrics. A delivery means any positive shipment; OTIF requires every line complete and on time, zero shipments are not delivered, and no delivered orders yields an explicit undefined OTIF rather than zero.

Loading tool…

Description

Construct synthetic orders with actual ordered/shipped line quantities and independent on-time draws, then delegate complete-line fill, backorder and delivered-order OTIF metrics. A delivery means any positive shipment; OTIF requires every line complete and on time, zero shipments are not delivered, and no delivered orders yields an explicit undefined OTIF rather than zero.

A logistics test dataset combines supplied operating ranges with explicit quantity and unit conventions. Constructed measurements and calculated indicators can exercise reports and calculators without claiming to represent an observed operation or a safe physical plan.

Construct synthetic orders with actual ordered/shipped line quantities and independent on-time draws, then delegate complete-line fill, backorder and delivered-order OTIF metrics. A delivery means any positive shipment; OTIF requires every line complete and on time, zero shipments are not delivered, and no delivered orders yields an explicit undefined OTIF rather than zero.

When to use this tool

Use this generator to create reproducible warehouse order fulfillment dataset cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

  1. Supply orderCount, minimumLines, maximumLines, minimumUnits, maximumUnits, onTimeProbability in the field shapes below. Set seed when you need an explicit replay.
  2. Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
  3. Read orders, totals, metrics. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw order lines and quantities, sample shipped units from zero through ordered units and draw on-time status for positive shipments. Mark any-positive-shipment orders as delivered and require every line complete and timely for OTIF. Delegate line-fill/backorder percentages and delivered-order OTIF.1

Delegated operations used for this result: fill rate line item percent; backorder rate percent. Their calculation or parsing conventions apply to the corresponding result fields.2, 3

Input fieldMeaning and unitsAccepted input
orderCountOrder CountRequired. Safe integer; minimum 1; maximum 128.
minimumLinesMinimum LinesRequired. Safe integer; minimum 1; maximum 16.
maximumLinesMaximum LinesRequired. Safe integer; minimum 1; maximum 16.
minimumUnitsMinimum UnitsRequired. Safe integer; minimum 1; maximum 9007199254740991.
maximumUnitsMaximum UnitsRequired. Safe integer; minimum 1; maximum 9007199254740991.
onTimeProbabilityOn Time ProbabilityRequired. Finite number; minimum 0; maximum 1.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
ordersOrdersRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 128.
orders[].idLiteral identifier used to match records, independently of their display labels.Required. Text.
orders[].linesLinesRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 16.
orders[].lines[].orderedUnitsOrdered UnitsRequired. Safe integer; minimum 1; maximum 9007199254740991.
orders[].lines[].shippedUnitsShipped UnitsRequired. Safe integer; minimum 0; maximum 9007199254740991.
orders[].lines[].onTimeOn TimeRequired. Boolean.
orders[].deliveredDeliveredRequired. Boolean.
orders[].inFullIn FullRequired. Boolean.
orders[].onTimeInFullOn Time In FullRequired. Boolean.
totalsTotalsRequired. Object; no unknown keys.
totals.lineItemsOrderedLine Items OrderedRequired. Safe integer; minimum 1; maximum 9007199254740991.
totals.lineItemsShippedInFullLine Items Shipped In FullRequired. Safe integer; minimum 0; maximum 9007199254740991.
totals.lineItemsBackorderedLine Items BackorderedRequired. Safe integer; minimum 0; maximum 9007199254740991.
totals.unitsOrderedUnits OrderedRequired. Safe integer; minimum 1; maximum 9007199254740991.
totals.unitsShippedUnits ShippedRequired. Safe integer; minimum 0; maximum 9007199254740991.
totals.ordersDeliveredOrders DeliveredRequired. Safe integer; minimum 0; maximum 9007199254740991.
totals.ordersOnTimeInFullOrders On Time In FullRequired. Safe integer; minimum 0; maximum 9007199254740991.
metricsMetricsRequired. Object; no unknown keys.
metrics.fillRatePercentFill Rate PercentRequired. Finite number; minimum 0; maximum 100.
metrics.backorderRatePercentBackorder Rate PercentRequired. Finite number; minimum 0; maximum 100.
metrics.otifPercentOtif PercentRequired. Finite number; minimum 0; maximum 100. or Null.
metrics.otifUndefinedReasonOtif Undefined ReasonRequired. Text; exactly "no-delivered-orders". or Null.
randomnessReplay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source.Required. Object; no unknown keys.
randomness.seedOptional numeric replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json
{
  "input": {
    "orderCount": 3,
    "minimumLines": 1,
    "maximumLines": 3,
    "minimumUnits": 1,
    "maximumUnits": 5,
    "onTimeProbability": 0.7,
    "seed": 42
  },
  "output": {
    "orders": [
      {
        "id": "order-1",
        "lines": [
          {
            "orderedUnits": 3,
            "shippedUnits": 3,
            "onTime": true
          },
          {
            "orderedUnits": 1,
            "shippedUnits": 1,
            "onTime": true
          }
        ],
        "delivered": true,
        "inFull": true,
        "onTimeInFull": true
      },
      {
        "id": "order-2",
        "lines": [
          {
            "orderedUnits": 5,
            "shippedUnits": 2,
            "onTime": true
          },
          {
            "orderedUnits": 5,
            "shippedUnits": 4,
            "onTime": true
          }
        ],
        "delivered": true,
        "inFull": false,
        "onTimeInFull": false
      },
      {
        "id": "order-3",
        "lines": [
          {
            "orderedUnits": 3,
            "shippedUnits": 2,
            "onTime": true
          }
        ],
        "delivered": true,
        "inFull": false,
        "onTimeInFull": false
      }
    ],
    "totals": {
      "lineItemsOrdered": 5,
      "lineItemsShippedInFull": 2,
      "lineItemsBackordered": 3,
      "unitsOrdered": 17,
      "unitsShipped": 12,
      "ordersDelivered": 3,
      "ordersOnTimeInFull": 1
    },
    "metrics": {
      "fillRatePercent": 40,
      "backorderRatePercent": 60,
      "otifPercent": 33.33333333333333,
      "otifUndefinedReason": null
    },
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • No delivered orders yields null OTIF with an explicit reason. Line metrics and unit totals have different denominators; independent synthetic draws do not reproduce real fulfillment or customer-service performance.
  • A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
  • The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

  1. Tool behavior and example: Random Warehouse Order Fulfillment Dataset Generator — tool.io

  2. Calculation or validation: logistics/fill-rate-line-item-percent — tool.io

  3. Calculation or validation: logistics/backorder-rate-percent — tool.io

Similar or alternative tools

  • Random Warehouse Picking Productivity Dataset Generator

    Generate synthetic shift order counts, integer lines per order, and separate positive picker/packing labor minutes; delegate orders/hour and lines/hour per shift and from aggregate work divided by aggregate hours. Totals are not an unweighted average of shift rates, and no real worker profiles, targets or performance judgments are inferred.

  • Random Inventory ABC Classification Dataset Generator

    Generate positive synthetic demand and unit values in one caller-labeled value unit, rank independently by annual usage value and demand throughput, and delegate cumulative-share ABC classifications. Value policy remains the existing fixed 80/95 boundaries, velocity boundaries are explicit, ties retain item order, and classification uses the cumulative share including the current item—not a forced A class for the largest item.