3PL service levels: define the promise before judging performance

Define dispatch in observable terms

Ask whether the reported event is label creation, packing completion, manifest closure, or carrier collection. Those events answer different questions. Use a timestamp both sides can access. If an order arrives near the cutoff, specify the time zone and which system timestamp decides eligibility. Keep delivery performance separate from warehouse dispatch performance so the report points to the team able to act.

Document exclusions before they become arguments

Write down how address holds, inventory shortages, payment review, customer changes, and late inbound stock affect the calculation. An exclusion should have a reason code and a reviewable history. Otherwise, a changing denominator can make a chart look better while customers wait. Ask for the count of excluded orders alongside the percentage rather than treating exclusions as invisible.

Use a worked example in the proposal review

Illustrative example: 1,000 orders arrive in a reporting period. Forty are documented as ineligible under the agreed rules. Of the remaining 960, 942 reach the agreed dispatch event on time. That is 98.125%, or 98.1% rounded to one decimal. Dividing by all 1,000 gives 94.2%. Neither figure should appear without its definition. Ask the provider to reproduce the calculation with a redacted sample.

Assign an operating response to a missed commitment

Request a routine for reviewing misses, identifying causes, assigning corrective actions, and checking whether the fix worked. A daily exception list and a monthly trend report serve different purposes. Specify the reporting cadence that fits your operation. Before signing contractual wording or remedies, have the appropriate commercial and legal reviewers assess the proposed terms; this guide is an operating checklist, not a contract template.