A third-party logistics agreement can be legally complete and still be operationally defective. It may contain an MSA, a statement of work, a rate card and an SLA exhibit, yet fail to describe the business the 3PL will actually operate.
When the operating data, SOW, pricing, service requirements and exit provisions do not align, the contract often creates the disputes it was supposed to prevent.
This checklist is for companies selecting a new 3PL as well as companies renewing, renegotiating or evaluating an incumbent relationship. The objective is not to transfer every risk to the vendor.
It is to make the work, charges, performance obligations and consequences sufficiently clear that both parties know what they are agreeing to.
A useful 3PL contract must connect six aspects: the client's historical operating data, a documented SOW, the rate card and billing definitions, measurable SLAs and remedies, auditable invoices and governance, and an executable termination and wind-down process. If any link is missing, the agreement may be legally complete but operationally defective.
FCBCO approaches these agreements from an operational and commercial perspective. Your attorney should review and negotiate the legal language. The operating team must make sure the documents describe how orders, inventory, information and money will move in practice.
Most 3PL relationships are governed by several documents: a master services agreement, SOW, rate card, SLA exhibit, implementation plan, technology specifications and operating procedures.
The first task is to confirm that all of them are incorporated into the agreement, have effective dates and use consistent definitions.
The hierarchy matters. If the MSA limits liability, the SLA exhibit promises credits and the rate card defines a different transaction than the SOW, the commercial protection may disappear when it is needed.
The contract should say which document controls when provisions conflict, how exhibits are amended and who may approve a change. It should also prevent informal emails or operational workarounds from silently changing the commercial agreement.
The practical test is simple: can the operating team trace every required activity from the SOW to a price, an SLA where appropriate, an invoice record and an owner? Legal counsel should draft the hierarchy and conflict language, but operations must validate that the assembled agreement works as a system.
The SOW is where the vendor recites back what the business does and how it will support it. It should describe outbound orders, lines and units; inbound receipts and their relative size; returns; storage; kitting; value-added services; channel requirements; integrations; reporting; and expected peaks and valleys. A generic promise to provide fulfillment services is not a workable operating specification.
For every activity the 3PL will invoice, provide at least 12 months of history. That normally includes order-level and line-level outbound data, receipt activity, returns, inventory balances, VAS volumes and storage at peak. Include the details that drive labor: single-line order share, units per line, product cube, case and pallet configuration, oversized items, channel mix and seasonal spikes.
Averages alone are dangerous. Two companies may each ship 1,000 orders per day and average 2.2 units per order, while one ships mostly small single-line parcels and the other ships mixed large-cube orders with retail labeling.
Their labor, equipment, space and compliance requirements are not comparable. If the vendor prices a simplified average and discovers the real profile after launch, either the client will face repricing or the vendor will struggle to perform profitably.
This operating profile should become the foundation of the broader 3PL selection and evaluation process.
An implementation date is not an implementation plan. The agreement should identify milestones, owners, required inputs and acceptance criteria for integrations, master-data conversion, testing, facility preparation, initial receiving, inventory validation, training, first orders and go-live support.
Dependencies must be explicit. If the client delivers incomplete item data, the current provider releases inventory late or the incoming pallets arrive mixed when the assumption was SKU-pure, the schedule will change.
Mixed inventory can take 1.5 to 2 times longer to receive than planned. Conversely, if the client meets its obligations and the vendor has not staffed, configured or tested the operation, the contract should not excuse the delay as a general implementation problem.
Use a responsibility matrix that names the client owner, vendor owner, due date, input, completion evidence and consequence of delay. This does more than manage the project. It creates a factual record for deciding whether additional cost or schedule relief is justified.
Companies should never sign without understanding total onboarding cost, timing and responsibilities. Vendor charges may include integration development, hourly IT support, WMS configuration, item and vendor conversions, pick location setup, slotting, business rule configuration, testing, initial receiving and special materials.
Field level integration documentation should be provided in advance so the client knows exactly what data must be sent and received.
The client's cost is broader than the vendor's implementation invoice. Budget internal IT and operating labor, travel and lodging to train 3PL staff on products, customers and order requirements, and onsite support during go-live.
Similar training may be necessary for major item refreshes. Some vendors may cover some or all transfer freight from the current facility as a commercial incentive, which can materially reduce transition cost.
Many agreements suspend SLA remedies for the first 30 to 90 days while the operation stabilizes. If there is a ramp period, spell out its length and what remains measured.
A remedy holiday should not become a measurement holiday. Initial receiving should use contracted rates unless a known exception was disclosed and priced before signature.
For a broader roadmap, review these critical tasks for implementing a new 3PL.
The initial term should be long enough to support a stable implementation and any legitimate vendor investment, but not so long that the client is trapped in an unsuitable relationship. Identify the initial term, automatic renewals, renewal length, price review timing and the notice required to prevent renewal.
Calendar the notice date immediately after signing. A missed 60- or 90-day nonrenewal deadline can add another year before alternatives can be considered. Renewal mechanics should also align with annual rate reviews, freight reviews and any CAPEX amortization.
Term and renewal are different from termination and wind-down: a contract can permit nonrenewal yet still provide too little time to move the operation safely.
Every invoiceable line needs a precise billing definition. Define what constitutes an order, line, unit, receipt, pallet, case, return, kit, storage location, project hour, integration charge and account-management fee. State when the charge occurs, what is included, what is excluded and which system record supports it.
For example, “pick fee” is incomplete. Is the first unit included in an order fee? Is each additional unit charged? Is a case pick priced differently from an each pick?
Does a multi-SKU kit create component picks plus a completed-kit charge? Are voided orders billable? Ambiguity makes a mathematically accurate invoice impossible to reproduce.
The rate card should mirror the SOW. If the SOW describes an activity without a price, the parties may argue over special-project rates. If the rate card contains charges for activities not described in the SOW, the client may receive fees it never understood.
Each major invoice line should map to a transaction field or an approved work authorization.
State which rates can increase, when they can increase, and how the change is calculated. Separate labor and service rates from true pass through costs such as postage, carrier surcharges, packaging or government fees.
Require documentation for pass through changes and avoid wording that permits the vendor to raise any rate whenever its costs rise.
An index-based increase should identify the index, reference period, effective date, floor or cap, and treatment of negative movement. A fixed annual percentage should identify which rate-card lines it affects.
Most importantly, an annual escalator should not substitute for validating whether the existing base rates still fit the current business. Applying 4% to a rate that was already misaligned simply compounds the problem.
For additional guidance, review how to control rate increases in 3PL contracts.
Future growth projections help a vendor plan, but no prudent 3PL will guarantee favorable pricing solely because a client expects to grow. Pricing should be grounded in actual historical volumes and operating characteristics.
Tiered concessions can apply when sustained volume reaches agreed thresholds, and rates may revert if volume later falls.
The agreement should define the metric, threshold, measurement period, number of periods required, affected rates, effective date and reversion rule. A vendor might have the right to reprice an affected service if average daily orders fall more than 15% below the SOW assumption for two consecutive periods.
That should not automatically permit repricing the entire rate card unless the whole operating profile has materially changed.
Growth does not always create meaningful scale. Moving from 500 to 750 orders per day is a 50% increase, but it may not reduce unit cost enough to justify a new tier.
Clients should ask for concessions when sustained volume truly changes the vendor's economics and should accept reasonable downside protections. For larger relationships, the parties can also discuss shared prosperity when growth materializes and the vendor exceeds SLAs through the peak.
Minimum monthly charges, management fees and reserved-capacity commitments shift demand risk to the client. They can be reasonable when the vendor dedicates labor, equipment or space, but the agreement must explain what the client receives and whether transactional charges count toward the minimum.
Model the minimum against seasonal lows, launch delays and plausible downside cases. Confirm whether minimums apply during implementation, force majeure, a vendor caused outage or a wind-down.
If the minimum is justified by dedicated resources, determine whether it declines when those resources are released. A minimum should not become a second invoice layered on top of the revenue it was intended to protect.
Storage is often one of the largest invoice lines. A 3PL wants to operate a distribution center, not become a low-cost warehouse for slow-moving goods.
A client using substantial space with relatively few transactions may face higher storage rates or surcharges for inventory with no movement for six months.
There are three common methods for calculating 3PL storage costs: location-based, square-foot and cubic-foot pricing. Location-based pricing charges by pallet, case, bin or pick face. Square foot pricing allocates a footprint and usually includes the picking footprint plus an allocation for receiving, packing and shipping areas.
Cubic foot pricing, which is less common, measures occupied cube and also typically includes the picking footprint. Larger or highly seasonal accounts may pay year-round for the square footage required at peak because the capacity is reserved for them.
Define inventory aging surcharges, measurement dates, replenishment and pick face charges, and whether slow-moving fees replace or supplement ordinary storage. Physical assumptions matter.
If the facility's maximum pallet height is 55 inches and the client tenders 84-inch pallets, the 3PL may down stack each into two positions and charge two storage locations, labor and another wood pallet. That single assumption can nearly double the expected cost before normal handling begins.
For many small and mid-sized accounts, use of the 3PL's carrier contracts is required because freight is an important revenue source. Aggregated volume can also give smaller clients better carrier rates than they could negotiate independently.
The problem is that clients often receive little visibility into the underlying rate, discount or markup.
Some 3PLs permit client carrier accounts but charge roughly $0.50 to $1.00 per shipment processed outside the 3PL's freight program. Compare the complete landed freight economics: transportation charges, accessorials, fuel, the per-shipment fee, administrative effort and service performance.
Do not assume the 3PL option is worse simply because its markup is opaque, or better simply because it aggregates volume.
The contract should define how often freight rates are reviewed, what data the client receives, how increases are communicated and whether the client may switch to its own contracts.
If switching is allowed only after a volume threshold or notice period, state both in advance.
Hourly charges are difficult to forecast and reconcile, and they give the vendor less incentive to remove labor from a process. Recurring work such as kitting, relabeling or routine VAS should move to a per-transaction rate when the work is sufficiently consistent.
One practical approach is to permit hourly billing for three months, measure units and hours, then convert the activity to a unit rate.
Audit hourly fees by comparing output with billed hours over several periods. If a vendor builds kits at $40 per hour, compare kits completed and hours billed each month.
A wide unexplained productivity spread may indicate inconsistent work, weak process control or billing problems. Sporadic projects may never generate enough history for a reliable unit rate, so require a written estimate, scope and approval instead.
Overtime needs separate treatment. If the client stayed within the agreed forecast tolerance, it should not automatically pay premium labor because the vendor did not staff adequately.
Define who can authorize overtime, when it is chargeable, what evidence is required and how client-caused exceptions differ from vendor staffing failures.
An SLA percentage is meaningful only when the contract defines its numerator, denominator, cutoffs, exclusions, source system and reporting period. Order accuracy is commonly measured monthly, not daily or weekly.
The KPI may be visible every day, but contractual failure is determined by aggregating all eligible orders in the fiscal period.
The major operating SLAs normally cover order turnaround, order accuracy, inventory accuracy, dock-to-stock time and returns-processing turnaround.
Consumer ecommerce, wholesale distribution and Amazon or marketplace orders may need different cutoffs, thresholds and remedies. A same-day ecommerce promise cannot be applied blindly to scheduled wholesale routing-guide orders.
Specify which orders are excluded, how client holds and carrier failures are treated, when the clock begins, and how late arriving data is corrected.
Otherwise, the vendor can meet a strong looking percentage by excluding the most difficult work or measuring a denominator the client did not expect.
Only a handful of vendors openly offer full credits for transactions that miss an SLA. Many provide a partial credit equal to 5% to 15% of the charge for the affected transaction, and only for failures beyond the allowed threshold. That remedy can be almost symbolic.
Suppose order accuracy is 99.9% monthly and the vendor ships 6,000 orders. Six errors are within the allowance. If each order costs $2.50 to process, a 5% to 15% credit equals only $0.125 to $0.375 for each qualifying error beyond the sixth.
Even if six additional orders qualified, total recovery would be only $0.75 to $2.25. By contrast, a remedy equal to 3% to 5% of all monthly order-processing fees would produce $450 to $750 on $15,000 of fees.
Credits are not the only tool. Larger accounts may use a 30-day cure period, corrective-action requirements, executive escalation and then enhanced credits or termination rights if performance continues to fail.
Termination for cause is important but is not a substitute for intermittent accountability; most clients cannot move inventory overnight, and the vendor knows the switching cost is high.
Retailer and marketplace chargebacks should be addressed separately. Contracts may impose very short notice periods, proof-of-payment requirements, per-incident caps or annual caps.
Ordinary SLA credits rarely reimburse the business impact of retailer noncompliance. The agreement should use a balanced ladder: measurement, investigation, corrective action, meaningful credits, cure and a workable right to terminate persistent failure.
Inventory accuracy is both an operating KPI and a financial risk-allocation mechanism, and the two are not always calculated the same way. Vendors generally manage accuracy through cycle counts and/or physical inventory.
Shortages, and sometimes damages, are reconciled over a 12-month period. A common loss allowance is around 0.5%, but both the percentage and denominator vary substantially.
Most agreements reviewed by FCBCO measured the allowance against throughput rather than ending inventory. Throughput may mean units handled, dollar value handled, inbound plus outbound divided by two, or receipts only.
Some contracts allow shortages and overages to offset one another; many are silent. Silence should not be treated as permission to net unrelated inventory.
The denominator can change the exposure by an order of magnitude. If average inventory is $2 million but annual throughput is $20 million, a 0.5% allowance equals $10,000 under the first method and $100,000 under the second.
Recovery above the allowance is generally based on actual, original or landed cost, not retail value, and remains subject to claim procedures and liability caps.
A client protective approach reconciles discrepancies by SKU and facility. An overage should offset a shortage only for the same SKU at the same facility when the evidence shows a timing or location error.
A surplus of low-value product should not mask a shortage of expensive product. The contract must also define the period, valuation method, treatment of damage, count process and timing of settlement.
Shortages, shrink and ordinary damage belong in the inventory accuracy SLA and its claim process. Define notice, investigation, supporting evidence, valuation, deductible or allowance, payment timing and the interaction with the general liability cap.
A generous sounding shrinkage formula can be neutralized by an impractical notice period or a cap that is lower than the likely loss.
Also define when inventory becomes the vendor's responsibility and when that responsibility ends. Receiving discrepancies, concealed inbound damage, customer returns and goods awaiting destruction may require different rules.
The client should be able to trace an unexplained variance from the WMS record through the count, investigation and financial resolution.
Catastrophic events such as fire, flood or a major facility loss are different. They belong in the insurance, force-majeure and business-continuity framework rather than being treated as routine shrink.
Never assume the 3PL's property or liability insurance covers the client's goods. In an anonymous review of 12 contracts, six expressly required the client to insure its inventory, three stated that the vendor did not insure the goods, and three contained no affirmative client insurance requirement despite significant vendor liability limitations. In practical terms, every client should confirm coverage with its broker.
The agreement should allocate responsibility for warehouse legal liability, cargo coverage, deductibles, certificates, subrogation and claims cooperation. It should also address business continuity: backup power and systems, alternate processing options, data recovery, communication obligations and priority when a shared facility is disrupted.
Insurance does not replace operating accountability. Routine inventory losses remain subject to the inventory SLA; catastrophic losses follow the applicable insurance and liability provisions. Keeping the two frameworks separate prevents gaps and double counting.
An invoice should contain enough detail to reproduce each major charge using the rate card and source transactions. Require transaction dates, identifiers, quantities, units of measure, rates, extended amounts, credits, pass through support and taxes. Summary invoices without supporting files force the client to trust numbers it cannot validate.
Payment terms should identify the due date, deposits or freight funding, late charges, the treatment of disputed amounts and any right to suspend service or withhold inventory.
The client should pay undisputed amounts on time while preserving documented disputes. Where the vendor requires freight prefunding or a security deposit, define reconciliation and return mechanics.
The client must reconcile every invoice against monthly transactions within the contract's dispute period, which is commonly only 5 to 15 days after receipt. That routine control asks whether the current invoice is valid and whether a dispute must be filed before rights expire.
A broader audit answers a different question: is there a systemic pricing, productivity or billing problem? For predominantly transactional pricing, review at least six months of invoices and the corresponding six months of orders, receipts, returns and inventory activity.
Include the contracted rate card and billing definitions, transaction detail sufficient to reproduce each major line, and approved hourly work orders, overtime requests and special project authorizations.
Transaction based overbilling is often caused by definitions or data mapping rather than a vendor inventing orders or receipts. Hourly lines create more uncertainty because output and effort vary.
The audit should quantify effective cost per order, line, unit, receipt, return and storage unit, then explain the drivers of month-to-month change. Audit rights should preserve access to the required data even after a disagreement or termination.
An independent 3PL contract and pricing review can determine whether the SOW, rate card, invoices and service requirements align with the business.
Forecasts should define cadence, horizon, level of detail, permitted variance and the vendor response. Identify ordinary peak capacity, surge limits, lead time for extraordinary events and which party pays for incremental labor or space.
The contract should distinguish three situations: the client operated within forecast tolerance; the client materially exceeded the forecast; or the vendor failed despite receiving reasonable notice.
If the client was within tolerance, vendor staffing problems should not automatically become overtime charges. If the client exceeded the agreed range, the vendor may reasonably require best-efforts treatment, premium labor or schedule relief.
Forecasting obligations must also connect to repricing. A short spike does not necessarily justify permanent rates, and a sustained decline may affect only the services whose economics changed. The agreement should specify the evidence and duration required for either response.
Technology provisions should identify each interface, data owner, field-level specification, testing responsibility, error process, support rate and change-control method. Most clients have limited IT resources, so expected vendor hours and client participation should be estimated before signature.
Specify the operational reports and raw data the client receives: orders, lines, units, receipts, inventory adjustments, cycle counts, returns, SLA results, labor projects, freight and invoice detail. Dashboards are useful, but downloadable transaction records are essential for audit and transition.
The contract should state who owns client data, how long it remains accessible after the last day of service, when it will be archived and destroyed, and whether the vendor will certify destruction. Data portability is an exit requirement, not merely an IT preference.
The SOW and operating procedures should describe how consumer ecommerce, wholesale, Amazon or marketplace orders differ. Include routing guides, labels, carton content, EDI, appointment scheduling, lot or serial number serial controls, returns disposition and any VAS required by a specific customer.
Customer chargebacks need separate notice and recovery rules. Examples in actual contracts include requiring notice and proof of payment within two weeks, limiting an incident to the service fee that caused it, imposing a $10,000 annual cap per SOW, or capping routing guide and EDI claims at small, fixedl fixed amounts. Those restrictions can make recovery far smaller than the client loss.
The vendor must receive current customer guidelines before it can fairly be held responsible. The client, in turn, needs timely reporting of exceptions so it can meet claim deadlines and correct the underlying process.
Daily operational contact is not a governance system. Define weekly or monthly operating reviews, KPI reporting, open issue logs, corrective action ownership, executive escalation and periodic commercial reviews.
Name the account manager and the senior sponsor and and clarify whether account management time is included or billed.
The client should have reasonable site access for audits, inventory counts and operating reviews, subject to safety and confidentiality rules. Governance should examine trends, not just the last failure: SLA performance, invoice variance, forecast accuracy, capacity, chargebacks, aging inventory and unresolved technology issues.
For more detail, review the 3PL KPIs and service-level metrics that should be monitored.
Confirm that confidentiality covers operating data, customer information, rates, methods and credentials, with appropriate survival after termination. Define ownership of client data, custom integrations, work product and preexisting vendor technology.
The vendor should not use the client's name, logo or performance information publicly without approval.
Employee non-solicitation and access restrictions should be reasonable and should not prevent the client from obtaining necessary expertise during a transition. Counsel should draft these provisions, while operations identifies the information, systems and relationships that need protection.
Legal risk provisions must not contradict the operating bargain. Counsel should examine warranties, indemnification, liability exclusions and caps, assignment, subcontracting, governing law, venue and dispute escalation. Operations should test whether those provisions preserve the remedies described elsewhere.
For example, an SLA credit, inventory claim or chargeback recovery may be limited by a general cap or labeled the exclusive remedy. A vendor may also be permitted to assign or subcontract performance without preserving facility, security or service assumptions. The legal documents and operating exhibits must be read together.
Both parties should have balanced no-fault and for-cause termination rights. No-fault termination by the client may carry early termination or unamortized investment costs, but those amounts and formulas must be known before signing. If the vendor is at fault, the agreement should state which client obligations are reduced or eliminated.
A 90-day notice period is common, but selecting and transitioning a material 3PL operation can take six to nine months. FCBCO generally prefers 180 days' notice or at least 90 days' notice plus a guaranteed 90-day wind-down period. The protection should work in both directions so a vendor cannot abruptly stop serving the client.
For-cause termination should connect to persistent SLA failure, cure periods and documented corrective action. A theoretical termination right is not enough if the operational timeline makes it impossible to use safely.
The contract should require continued, cooperative service during migration. Wind-down work should use current transactional rates such as the contracted cost to pick a carton or pallet rather than new special pricing imposed after notice.
Define responsibilities for counts, inventory preparation, outbound transfers, systems, carrier coordination and the sequence for releasing goods.
If the vendor funds equipment or other CAPEX and recovers it from the client, attach a clear amortization schedule showing what is owed at every point in the term. State how termination for vendor cause affects that balance. All exit costs should be knowable before execution.
Address data availability after the final service date, archival and destruction timing, and proof of destruction. Vendors sometimes state that invoices must be current before releasing inventory; the agreement should distinguish undisputed past due amounts from documented disputes so inventory does not become leverage over a good-faith billing issue.
Finally, allow a reasonable settlement period - often about 30 days after final services - to reconcile invoices, claims and chargebacks from the last shipments. Continued service, inventory release, data transfer and final settlement are what make the termination right operationally real.
Before signing or renewing, the executive team should be able to answer five questions:
Do the historical operating data, SOW and implementation plan describe the business the 3PL will actually run?
Can every material charge be traced to a defined unit, source transaction and agreed rate?
Are service levels measured by the correct channel, period and denominator, with remedies that create accountability?
Are routine inventory losses, catastrophic events, insurance and liability treated as separate but connected risks?
Could the company exit without losing control of inventory, customer service, data or final costs?
If the answer to any question is no, the next step is not simply to negotiate harder. It is to identify which operating assumption is missing, quantify the exposure and make the documents agree.
A balanced contract should protect the client while giving the 3PL accurate data, reasonable forecasting and a fair opportunity to perform profitably.
Companies still evaluating whether or how to outsource fulfillment may also benefit from FCBCO’s complete guide to 3PL fulfillment and logistics.
Your 3PL agreement should connect the operating profile, SOW, pricing, SLAs and exit requirements. FCBCO can independently review those documents, identify commercial and operational gaps, and help your attorney understand where the agreement may not support the business as intended. Request a 3PL Contract and Pricing Review.
This article provides operational and commercial guidance and is not legal advice. Engage qualified counsel to review and negotiate contract language.