Order Delivery Feedback Comments

This dataset contains customer delivery feedback comments, each labeled with a satisfaction score and linked to order and delivery details. It is optimized for training NLP sentiment models and analyzing logistics service performance, with fields for feedback text, delivery context, and resolution tracking. The dataset enables actionable insights for improving customer experience and operational efficiency.

  • last updated 12 Jul 2025
  • by GoMask
The brief that made it

Training sentiment analysis and NLP models on delivery feedback

Sample rows

preview · 8 of 200 rows · all 11 columns
feedback_idstringdelivery_typestringsatisfaction_scoreintegerresolvedbooleanlanguagestringorder_idstringcustomer_idstringdelivery_datedatefeedback_datetimedatetimefeedback_textstringdelivery_regionstring
FEE-A1B2C3D4express5trueenORD100101CUST4012024-03-182024-03-19T09:12:41ZDelivery was fast and the package arrived in perfect condition.Los Angeles
fee-1ee2-99ab-xyz7standard2falseenORD100102CUST4022024-03-172024-03-19T15:30:23ZReceived my parcel two days late. Not happy with the delay.Chicago
FEED-000003same-day5trueenORD100103CUST4032024-03-182024-03-18T18:45:20ZSame-day delivery worked well. Thank you!New York
FEEDBACK-004standard3trueenORD100104blank2024-03-162024-03-17T11:06:32ZWrong item delivered. Customer service fixed it quickly.Houston
FEE54DC8001standard4trueenORD100105CUST4042024-03-122024-03-13T14:21:08ZArrived on time. Good service.Phoenix
FEE-X9Z8W7V6standard1falseenORD100106CUST4052024-03-202024-03-21T08:09:59ZHorrible experience. My package was lost.Philadelphia
FEE-2024-XYZ-01express5trueenORD100107CUST4062024-03-192024-03-19T17:56:44ZThe courier was polite and efficient.San Francisco
FEE-ALPHA102standard3trueenORD100108CUST4072024-03-152024-03-16T10:34:52ZPackaging was damaged but contents were safe.Dallas

What the 200 rows show

from the 200-row sample

Standard (delivery type) stands out: mean satisfaction_score is 2.3, against 4.3 for the rest.

  • 67%resolved = true
  • 4median satisfaction_score
  • 60delivery regions
Mean satisfaction_score by delivery_type200 rows
0482.3standard82 rows4.5express62 rows4.8same-day37 rows2.4other19 rows
satisfaction_score200 rows, in bands of 0.5
040802803802204171135satisfaction_score →

Median 4, from 1 to 5.

language200 rows · 7 values
  1. en151
  2. ru12
  3. de10
  4. es10
  5. fr9
  6. ja7
  7. pl1
11 columns by typefrom the column list below
  • string 7
  • integer 1
  • date 1
  • datetime 1
  • boolean 1

Columns

11 columns in four groups
blueprint · 11 columns
columntypedescriptionexample
Text 7 columns
feedback_idstringA unique identifier for each feedback comment.uniqueFEE-A1B2C3D4
order_idstringUnique identifier for the order associated with the feedback.ORD100101
customer_idstringUnique identifier for the customer providing the feedback.optionalCUST401
feedback_textstringThe full textual comment provided by the customer regarding the delivery experience.1 or moreLate delivery.
languagestringLanguage code (ISO 639-1) of the feedback text.7 languages · optionalen
delivery_regionstringGeographical region or city where the order was delivered.optionalLos Angeles
delivery_typestringType of delivery service used (e.g., standard, express, same-day).standard · express · same-day · other · optionalexpress
Numbers 1 column
satisfaction_scoreintegerNumerical satisfaction score assigned to the feedback (e.g., 1-5 scale).1 to 55
Dates and times 2 columns
delivery_datedateThe date the order was delivered to the customer.optional2024-03-18
feedback_datetimedatetimeTimestamp when the feedback was submitted.2024-03-19T09:12:41Z
True or false 1 column
resolvedbooleanIndicates if the feedback led to a resolution or follow-up action.optionaltrue

Use it for

  • resolved67%133 of 200 rowsmean satisfaction sco…2.3stan…4.5expr…4.8same…2.4other

    A logistics dashboard

    The resolved rate, satisfaction_score by delivery_type and a breakdown of language. Excel, Power BI or Tableau.

  • Why do the 82 standard rows have a mean satisfaction_score of 2.3?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable feedbacks with order_id, customer_id and delivery_date to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 11 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows11 columns
Yours1,000 rows11 columnsdelivery_region: UK only

blueprint · order-delivery-feedback-comments

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 11 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each comment linked to order ID
  • Include satisfaction score (1-5)
  • No customer PII or addresses
  • Comments cover multiple delivery scenarios
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
order-delivery-feedback-comments

What should your data show?

Preview 20 rows free
No signup. No card.