A 3PL scope of work is the contract document that names every service a third-party logistics provider will perform, the rate attached to each one, and the standard that work has to meet.
Key Takeaways
- The rate schedule is the enforceable part of the agreement. Every billable activity needs a named unit, a named rate, and a written cap on annual increases before signature.
- Volume and SKU assumptions set the price. When actuals diverge from the forecast, the provider bills the deviation and the contract gives it cover to do so.
- Four sections go blank most often: dispute windows, inventory shrinkage tolerance, carrier selection authority, and data ownership. Each one has a predictable dispute attached.
- Value-added work that touches more than 20% of outbound volume belongs in the base agreement at a fixed unit rate, not in change orders priced after the fact.
- FreightOptics 3PL Audit validates pick, pack, storage, supplies, rebills, and minimums against the rate agreement and flags charge codes that have no contractual basis.
Procurement teams rarely lose money on the rate they negotiated. They lose it on the work that was never priced. A warehouse agreement gets signed on a clean per-order rate, and eighteen months later the invoice carries storage overages, a monthly minimum nobody modeled, packaging supplies at cost-plus, and three accessorial codes that do not appear anywhere in the contract. Nothing was breached. The document simply did not say.
This article covers what the agreement has to nail down before signature: service definitions, volume assumptions, the responsibility split, performance standards, error handling, data obligations, and the rate schedule that makes all of it auditable.
What the Document Has to Cover Before Signature
The document tells a third-party logistics provider exactly what to do, how performance gets measured, and what happens when it falls short. It defines the boundary between what the provider handles and what the shipper keeps.
Draft it before final negotiations, not after. The scope drives the price. A provider that quotes against a loose description will reprice once operational complexity becomes clear, and repricing happens on the provider’s terms. Locking the scope first gives procurement leverage at the table and gives finance a benchmark for checking invoices later.
The core elements to address:
- Fulfillment activity: inbound receiving, putaway, pick and pack, outbound shipping, and returns processing
- Freight and cargo handling: freight forwarding responsibilities, carrier selection authority, and mode definitions for outbound freight
- Rates and billing terms: unit definitions for every charge, invoice format, backup documentation, dispute windows, and audit rights
- Automation: which workflows run automatically, including order routing, label generation, and invoice coding, and which stay manual
- Performance standards: fulfillment accuracy, on-time ship rate, and receiving cycle time
- Reporting: what data the provider delivers, in what format, and on what schedule
Agreements that hold up over years share one structural trait. They get reviewed on a defined cycle rather than filed and forgotten. Teams that revisit terms quarterly catch billing drift and unauthorized surcharges before they compound into a year of margin.
What Vague Volume and Staffing Assumptions Cost You
The provider prices the deal off numbers you supply: SKU count, daily order volume, average lines per order, seasonal peak. When real volume diverges from those figures, every deviation becomes billable, and the charges land as line items on a warehouse statement months before anyone traces the source.
The exposure is not only financial. Three continuity gaps show up repeatedly in agreements that otherwise look thorough:
- Single point of contact clauses. Most agreements name one account manager and no backup. When that person leaves or goes unreachable during peak, the escalation path inside the provider disappears and decisions stall.
- Warehouse capacity language. A storage footprint stated in square feet, with no seasonal ceiling, lets the provider reallocate space to other clients during high-demand periods. You find out when inbound inventory has nowhere to go.
- Staffing model assumptions. A staffing ratio built on average daily order volume does not survive a promotional spike. Pick rates slow within hours and outbound orders back up.
Providers build capacity and staffing assumptions from the client’s own forecasts, and when those forecasts are thin, they write conservative numbers that protect provider margin. Verified historical volume and charge data is what moves those assumptions. Without it, you negotiate against the provider’s data holding none of your own.
Value-Added Services: Base Rate or Change Order
Kitting, labeling, and custom packaging each consume labor, materials, and coordination inside the warehouse. A provider that does not see these named in the agreement treats every request as a change order and prices it on the spot. You negotiate one cost per order and pay a different one in practice.
| Service | Include in the Base Agreement When | Treat as a Change Order When |
|---|---|---|
| Kitting | SKU bundles are predictable and recurring | Bundle configurations change often or are promotional |
| Labeling | Compliance labels are standardized across all SKUs | Label formats vary by retailer or sales channel |
| Custom packaging | Branded packaging applies to all outbound orders | Custom packaging is limited to select SKU categories |
The practical rule: any value-added service that touches more than 20% of outbound volume on a recurring basis belongs in the base agreement with a fixed unit rate. Work below that threshold can sit outside it, but the change order rate and the approval process still need to be written down. Leave either undefined and the provider holds full pricing discretion.
Rate Schedules and Billing Terms
This is the section finance will live with for the length of the contract, and it is the section most often reduced to a one-page rate sheet stapled to the back. A rate sheet lists prices. A rate schedule defines what triggers each price, how it is measured, and what evidence appears on the invoice.
Every charge type needs a unit, a basis, and a trigger condition.
| Charge Type | What the Schedule Has to Fix | What Happens Without It |
|---|---|---|
| Receiving | Unit basis (pallet, carton, or line) and any per-hour unload rate | Palletized freight billed per carton |
| Storage | Basis (pallet, bin, or cubic foot), measurement date, and proration rules | A full month billed on inventory that shipped on day three |
| Pick and pack | Rate per order, per line, and per unit beyond the first | Multi-line orders repriced into a higher tier |
| Packaging supplies | Named materials at named prices, with a cap on pass-through markup | Cost-plus billing at an undisclosed margin |
| Monthly minimum | The threshold, what activity counts toward it, and how shortfalls bill | A slow month produces a charge nobody forecast |
| Accessorials | Every code named, with its trigger condition and rate | New codes appear mid-term with no contractual basis |
| Carrier rebills | Whether freight passes at cost or with markup, and what backup is required | Marked-up carrier charges with no supporting invoice |
| Rate escalation | The index, the cap, and the notice period | Increases applied without notice or ceiling |
Billing terms matter as much as the rates. Specify invoice frequency, the level of line-item detail required, and the backup documents that accompany each invoice. State the dispute window in days and state when it starts, invoice date or receipt date, because the difference decides who wins a late claim. Reserve the right to audit charges against the schedule, and reserve it in writing, including the right to use a third-party auditor.
An unauthorized charge code is the clearest signal a rate schedule is being tested. FreightOptics 3PL Audit extracts pick, pack, storage, supplies, rebills, and minimums from warehouse invoices into structured records, validates each charge against the rate agreement, and flags codes that appear on the bill but not in the contract.
Who Owns What, and the Gaps That Trigger Disputes
Shared ownership is the same as no ownership. Every operational task needs a named responsible party.
| Task | Typical Owner | Consequence of a Blank Assignment |
|---|---|---|
| Inbound receiving accuracy | Third-party logistics provider | Shipper absorbs shrinkage with no recourse |
| Carrier invoice validation | Shipper, or a delegated auditor | Overbilling goes undetected and accumulates |
| Outbound freight automation setup | Negotiated, and it must be stated | Manual processing delays shipping commitments |
| Warehouse cycle counts | Third-party logistics provider | Inventory discrepancies surface only at year-end |
| Carrier contract negotiation | Shipper | Provider defaults to its own carriers, with no rate leverage for you |
| Cargo damage claims filing | Assigned explicitly | Claims expire unfiled and the shipper absorbs the loss |
Four fields go blank more often than any others, and each has a dispute waiting behind it. Without a written billing dispute window, the provider applies its own policy. Without an inventory shrinkage tolerance, every cycle count becomes a negotiation. Without stated carrier selection authority, the provider picks the carrier that benefits the provider. Without data ownership and reporting terms, you get reports when the provider decides to send them.
The document should also handle the freight forwarding case: who authorizes a carrier change when the primary carrier cannot meet a delivery commitment. In ecommerce fulfillment that decision window often runs under two hours. Leave it blank and the provider makes the call at whatever cost it considers acceptable.
Negotiation is the only moment both parties hold equal leverage on these boundaries. Reassigning a task mid-contract is difficult and usually carries a change order fee. Walk each workflow end to end and put a named owner on every handoff.
Setting Performance Standards Without Writing a Full SLA
Performance language belongs in the agreement itself, not held back for a separate service level agreement. A full SLA adds remedies, penalties, and enforcement obligations that many mid-market teams are not ready to exercise on day one. The space between the two is where most disputes start.
Naming a metric is not enough. A metric with no measurement method, no reporting cadence, and no owner is a wish. Answer four questions for every standard:
- What is measured: order accuracy rate, on-time ship rate, receiving cycle time, or another specific output.
- How it is measured: system-generated data, manual counts, or a shared reporting view.
- Who reports it: the provider, the shipper, or a neutral source.
- What triggers a conversation: the threshold at which both parties agree to meet, not to penalize.
Keeping these terms in the agreement lets both sides calibrate against real volume before consequences attach. When you are ready to add formal remedies, that performance history becomes the baseline that makes them defensible.
Error Handling and Remediation
Most agreements name who handles errors. Few specify the sequence, the response window, or the evidence required to trigger remediation. That gap is where disputes sit for months.
| Error Category | Responsible Party | Response Window | Evidence Required |
|---|---|---|---|
| Mispick or wrong SKU shipped | Third-party logistics provider | 48 hours from customer report | Order record and warehouse scan log |
| Carrier billing discrepancy | Shipper, using provider data | 30 days from invoice date | Carrier invoice and freight audit report |
| Receiving shortage | Both parties jointly | 5 business days from receipt | Inbound manifest and receiving log |
| Damaged goods at fulfillment | Third-party logistics provider | 24 hours from identification | Photo documentation and SKU record |
Automation changes who owns the error. When a warehouse runs automated sortation, label generation, or cartonization, the system log becomes the primary evidence, not the operator. A document written before that automation existed assigns remediation to a person who no longer touches the process. Write error-handling language that references the data source rather than the job title: “the WMS event log will serve as the record of receipt,” not “the warehouse manager will confirm.”
Confirm during diligence that the provider can produce invoice-level data in a format an auditor can consume. That compatibility is not a given, and it decides how fast you can recover a charge.
Technology and Data Obligations
Providers run their own warehouse management systems, carrier integrations, and reporting tools. When the contract does not name the data, the format, and the schedule, the provider defaults to what is convenient internally, and the shipper loses sight of the activity it is paying for.
Split the obligations by party. The provider generates data. The business consumes and validates it. When the agreement leaves that split implicit, both sides assume the other is handling it.
Provider obligations:
- Publish inventory counts at the SKU and location level, at or near real time, accessible by API or direct integration
- Generate discrepancy reports when physical counts diverge from system records beyond a defined threshold
- Deliver invoice data in a structured format that supports downstream audit workflows
- Flag receiving exceptions inside a defined window so the discrepancy can be worked before it ages
Business obligations:
- Maintain a master product catalog with current dimensions and weights so charges compute correctly
- Validate inventory reports against internal records on a set schedule and escalate discrepancies in writing
- Provide advance shipment notices that meet the provider’s inbound processing requirements
Two details decide whether any of this is usable. First, specify update frequency and error tolerance together. A partner that batches inventory updates infrequently forces the business to carry extra safety stock, because availability signals cannot be trusted for live order decisions. Higher-frequency updates sound like a win, but they raise API call volume and can introduce latency errors if the provider’s system was not built for it. Second, assign reporting obligations by business use case, not by output type. A daily inventory report can satisfy the letter of the contract and still omit the lot-level or expiry detail compliance requires.
| Reporting Obligation | Assigned Party | Frequency Needed | Business Use Case |
|---|---|---|---|
| SKU-level inventory count | Third-party logistics provider | Continuous or near real time | Live order fulfillment decisions |
| Carrier invoice line-item detail | Third-party logistics provider | Per shipment | Freight audit and charge validation |
| Receiving discrepancy report | Third-party logistics provider | Within 24 hours of inbound | Inventory accuracy and supplier claims |
| Master product dimension data | Business | Updated at SKU change | Accurate fulfillment charges and carrier billing |
| Inventory validation confirmation | Business | Weekly minimum | Discrepancy escalation and record integrity |
Structured invoice data is also what makes the rate schedule enforceable after signature. FreightOptics ingests warehouse invoices by API, SFTP, or EDI and organizes charges by warehouse and by type, so procurement can compare what each facility bills for the same activity and finance can accrue against real line items.
Conclusion
Ambiguity in a warehouse contract is not neutral. It is a pricing concession you make without knowing it. Define the volume assumptions, the responsibility split, the performance standards, the data obligations, and above all the rate schedule that attaches a unit and a trigger to every charge. Then keep the document alive with a review cycle, because rates drift and charge codes multiply. None of that protects margin on its own: a signed agreement only holds if someone compares it to the invoices that follow.
Check What You Wrote Against What You Are Billed
A scope of work sets the rate for every task. FreightOptics 3PL Audit compares each invoice line back to that agreement and flags charge codes that appear on the bill but not in the contract. Audit your invoices against your SOW
Frequently Asked Questions
What does a 3PL actually do?
A third-party logistics provider handles the physical movement and storage of goods for a shipper: warehousing, pick and pack, carrier management, and freight billing. The agreement defines which of those functions the provider owns. Without it, charges go unchallenged and accruals drift at month-end.
What is the difference between 3PL, 4PL, and 5PL?
A 3PL executes logistics operations, moving and storing freight. A 4PL sits above that layer and manages multiple 3PLs as a single integrator. A 5PL coordinates logistics across many shippers at network scale. Each layer adds oversight and makes invoice auditing harder, because more parties touch the same charge.
Is Amazon a 3PL or a 4PL?
Both, depending on context. For sellers using FBA, Amazon acts as a 3PL by storing inventory and shipping orders. Across its broader network it coordinates carriers and fulfillment nodes the way a 4PL does. Either way, shippers still need to check carrier invoices for dimensional weight overcharges and accessorial fees.
What are 1PL and 2PL logistics?
A 1PL moves its own freight with its own assets. A 2PL is an asset-based carrier that provides transportation only, with no warehousing or management layer above it.
Should performance penalties go in the SOW or a separate SLA?
Start with performance standards, measurement methods, and review thresholds in the main agreement. Add formal remedies once you have several months of real performance data to set them against. Penalties written before you know your provider’s baseline are usually either unenforceable or unrealistic.
Who should own carrier selection for outbound freight?
The shipper, in almost every case, because the shipper holds the carrier contracts and the rate leverage. If the provider selects carriers, the agreement should state which carriers, at which rates, and require the underlying carrier invoice as backup on every rebill. FreightOptics 3PL Audit validates those rebills against the rate agreement so marked-up freight does not pass through unnoticed.
