Catch damage and shortage notes on signed delivery receipts

Fields

• Where the remark came from (e-POD note, OCR of a paper POD, WMS receiving note)
• Exception remark as written

Questions

1. Does the delivery remark record a problem with the goods delivered? Yes / No

   Read the remark. Count any shortage, overage, damage, refusal, wrong goods, temperature or seal problem, and a blanket reservation. A name, signature, time, "OK" or "received in good order" on its own is not a problem. Read negations carefully: "no dmg" is not damage. Yes: The remark records a problem or a blanket reservation. No: The remark records a clean delivery.

2. What is the main problem the delivery remark records? Choice

   Use the OS&D terms in the context. When the remark records more than one problem, pick the one that affects the most goods; pick a specific problem over a blanket reservation.

   • No problem The remark records a clean delivery.
   • Blanket reservation only The only note is a general reservation such as "subject to inspection" or "STC".
   • Shortage Fewer units, cartons or pallets delivered than shipped.
   • Overage More delivered than shipped.
   • Visible damage Damage to the packaging or goods seen at delivery.
   • Concealed damage Packaging looked fine or was not checked, and damage is found or expected inside.
   • Wrong or mislabelled goods Items or labels do not match the order or the paperwork.
   • Refused in full The consignee refused the whole delivery.
   • Refused in part The consignee refused some of the items and accepted the rest.
   • Temperature or seal problem A reefer temperature out of range, or a seal broken, missing or with a number that does not match.

3. Does the delivery remark name a specific problem, beyond a blanket reservation? Yes / No

   A blanket reservation is defined in the context. A specific problem names what is short, damaged, refused or wrong. Yes: The remark names at least one specific problem, with or without a blanket reservation. No: The remark records a clean delivery or a blanket reservation only.

4. Does the delivery remark say how many units, cartons or pallets are affected? Choice

   Read the remark for a number of affected units, cartons, cases or pallets, written as digits or words. Do not count the total delivered as the number affected.

   • Quantity stated The remark names a problem and says how many items it affects.
   • Quantity not stated The remark names a problem but not how many items it affects.
   • No specific problem The remark records a clean delivery or a blanket reservation only.

5. What does the delivery remark say is damaged: the packaging, the product, or both? Choice

   Read the remark for what the damage affects. Wet, crushed or broken goods are product damage; torn wrap, crushed cartons or broken pallets are packaging damage.

   • Packaging only Wrap, cartons or pallets are damaged, and the product is not said to be damaged, or is said to be fine.
   • Product only The goods are damaged, and no packaging damage is mentioned.
   • Packaging and product Both the packaging and the goods inside are damaged.
   • Damage not described Damage is recorded without saying what is damaged.
   • No damage recorded The remark records no damage.

6. Does the delivery remark say photos were taken? Yes / No

   Count "pics taken", "photos", "img attached" and similar. Yes: The remark says photos were taken or attached. No: The remark does not mention photos.

7. How much of the delivery does the remark suggest is unusable? Scale

   Judge from what the remark says about the goods, not about the packaging alone. Do not calculate a share from the numbers; judge the words.

   • None Nothing is said to be unusable: a clean delivery, packaging damage only, or a reservation.
   • Cosmetic Marks, scuffs or dents; the goods are still sellable.
   • Some Some of the goods are unsellable, short or refused.
   • Most or all Most or all of the delivery is unsellable, short or refused.

8. Is the delivery remark readable enough to judge? Yes / No

   Shorthand, abbreviations and poor spelling are normal and still readable. Judge whether the text makes enough sense to tell what was recorded. Yes: The remark can be read and understood. No: The remark is garbled by OCR, cut off, or too short to make sense of.

Lens columns

has_exception, has_exception_probability, exception_type, exception_type_probability, specific_problem_named, specific_problem_named_probability, quantity_stated, quantity_stated_probability, what_is_damaged, what_is_damaged_probability, photos_taken, photos_taken_probability, severity, severity_average, text_judgeable, text_judgeable_probability