Fulfillment SLAs Explained: What to Look for When Evaluating a 3PL

By
Freddy Bruce
October 27, 2026
15
Min read

TL;DR

A fulfillment SLA only protects you if it measures the right things, measures them honestly, and attaches a real remedy when the provider misses. This guide covers the commitments a 3PL SLA should contain, how measurement and exclusions can quietly weaken them, how service credits and termination rights work, and what to negotiate before signing. It is not legal advice, so have your own adviser review any contract.

Key Takeaways

Fulfillment SLAs vary far more in substance than in appearance, and the points below summarise what separates a useful one from a decorative one.

  • A useful SLA covers despatch cut-offs, order accuracy, goods-in, returns, stock accuracy, packaging and damage, system uptime and response times, each with a stated formula
  • Exclusions for carrier delays and peak season can remove much of the protection, so read them as closely as the headline numbers
  • Service credits usually equal a small percentage of monthly fees and rarely come close to covering the commercial damage of a missed peak
  • Standard UK warehousing terms can limit a provider's liability for lost or damaged goods to £100 per tonne unless you agree and pay for a higher limit
  • Brands enforce SLAs through relationships and escalation far more often than through the contract itself

The negotiation section lists the clauses worth changing before you sign.

Fulfillment SLAs and What to Look for in a 3PL

An SLA with no remedy is a wish list. Many fulfillment contracts include impressive-sounding commitments, such as 99.9% accuracy or same-day despatch, and then attach nothing that happens when the provider misses them. Others attach a remedy so small, or so hedged with exclusions, that it changes nothing. This guide is for eCommerce brands choosing or renegotiating a 3PL contract who want to know what a fulfillment SLA should contain and how to tell a useful one from a decorative one.

SLAs turn performance metrics into contractual promises, so they build on the measures covered in our guide to the metrics to hold a provider to. Accuracy measurement gets its own Gonini guide, and this one treats accuracy as one commitment among several. The focus here is the contractual layer: what to commit, how to measure it, what happens on a miss, and what to negotiate.

If you are still comparing providers, the SLA belongs in your shortlisting, and our guide to the full provider selection checklist shows where it fits. Asking for a sample SLA early tells you a lot, since providers with strong operations usually have clear, specific agreements ready to share.

A word on our position before going further. Gonini signs these agreements as the provider, so this guide is written from the other side of the table from its readers. We have kept in the points that cut against providers, including how exclusions weaken SLAs and why tight SLAs can mislead. This guide is general information rather than legal advice, so have your own solicitor or adviser review any contract before you sign.

What a 3PL Service Level Agreement Should Cover

A 3PL service level agreement should cover eight commitment areas, each with a reasonable target, a clear measurement method, and wording you can read without a lawyer. The table sets out each area, what a reasonable commitment looks like, how to measure it, and the wording that quietly weakens it. Targets here are indicative and drawn from the sources in our methodology.

Commitment area Reasonable commitment How to measure it Wording to watch for
Despatch cut-off Same-day despatch for orders received by an agreed cut-off, for a stated share of orders, with best-in-class operations at 99.5% or more Orders despatched same day ÷ orders received before cut-off “Received and released” instead of received; monthly averages; excluding missed carrier collections
Order accuracy 99.5% or better, measured by order Error-free orders ÷ total orders, including verified customer reports “Measured on complaints received”; quarterly averages; excluding undefined “data errors”
Goods-in turnaround Stock booked in within 24 to 48 hours of delivery Hours from delivery to stock available for sale Clock starting when paperwork is “complete”; “working days” left undefined, so weekends and holidays stretch the clock
Returns processing Returns inspected and restocked or quarantined within a few working days Days from receipt to final status in the system “Processed” meaning logged rather than inspected; peak carve-outs
Stock accuracy 99% or better by location or SKU Counted stock ÷ system stock on cycle counts Counts chosen solely by the provider; value-based tolerance bands that hide unit losses
Packaging and damage An agreed packaging standard for each product type, with damage defined Orders reported damaged ÷ orders despatched “Damage” left undefined; no reporting on orders that arrive damaged
System uptime Warehouse system and integrations available 99.5% or more of the time, outside agreed maintenance Minutes available ÷ minutes in the month Unlimited “scheduled maintenance”; excluding integration failures
Response times Urgent issues acknowledged within an hour and resolved within an agreed window Time from ticket to first response and to resolution Acknowledgement counted as response; business hours only during peak

‍

To show what this looks like in a real agreement, these are the service levels we commit to at Gonini.

  • Despatch: the order cut-off is 2pm or later in every warehouse, in every country we operate in, and some sites can offer a later cut-off agreed with each brand. We despatch 99.5% of orders on time, meaning the order arrived before the cut-off and we picked it, packed it and handed it to the carrier the same day
  • Pick accuracy: 99.9%, measured across every order, with a barcode scan for every pick
  • Goods-in: inbound stock booked in within 2 working days
  • Returns: returns booked in within 2 working days

Hold any provider, including us, to the same test: ask for the definition behind each number.

The wording column matters most. Most SLAs look similar at headline level, and the real differences sit in how measurement works, which periods get averaged and what falls outside the count. Read each clause asking what a provider could do to report success while your customers experience failure.

How We Set the Reasonable Commitments

The reasonable commitments in the table come from published industry sources and common UK practice, checked on 15 October 2026. Extensiv, a warehouse software company, reports the 2025 best-in-class figures from WERC's DC Measures study as 99.5% or better for on-time shipments and 99.68% or better for order picking accuracy.

The despatch cut-off, goods-in, returns, stock accuracy, packaging, uptime and response-time targets in the table are indicative, based on common practice rather than a single published standard, so adjust them to your order profile.

For contractual terms, we used the UK Warehousing Association's published contract conditions and published guidance on service credits from Bird & Bird, Lighthouse Law, ContractKen and Tacto. Contract law and individual agreements vary, so treat everything here as a starting point for discussion with your adviser.

How Fulfillment SLAs Differ from IT SLAs

Most SLA guidance online comes from IT and cloud services, where SLAs focus on system uptime and support response times. Fulfillment SLAs share the structure, and they differ in what fails and how. A fulfillment failure usually involves a physical order that leaves late, arrives wrong or goes missing, and each failure reaches a customer directly.

Measurement differs too. Monitoring tools can track uptime automatically, while fulfillment performance depends on timestamps, scans and error records that the provider controls. That makes the definition of each measure, and who records it, far more important than in most IT agreements.

Remedies differ in scale. An hour of downtime in a software service costs a fairly predictable amount, while a missed despatch window during Black Friday can cost a brand sales, reviews and repeat customers that no fee reduction recovers. Fulfillment SLAs need remedies designed with that in mind, which the remedies section below covers.

The Core Commitments

Six commitments form the backbone of most fulfillment SLAs: despatch cut-off, order accuracy, goods-in turnaround, returns processing, stock accuracy, and packaging and damage. System uptime and response times usually sit alongside them. The sections below cover the six core commitments in turn.

Despatch Cut-Off Times and Same-Day Thresholds

The despatch cut-off is the latest time an order can arrive and still leave the warehouse that day. A later cut-off gives your customers more time to order for next-day delivery, which can support conversion on your site. The cut-off only matters if the SLA also states what share of orders received before it must actually leave the same day.

Timestamps decide whether an order met the cut-off. CXTMS, a transport management software vendor, recommends defining on-time shipment against the brand's accepted order timestamp and promised cut-off, and naming the system of record for each event in the SLA. Without that clarity, an order placed at 2:58pm against a 3pm cut-off can fall on either side of the line.

Despatch is also distinct from delivery. A provider can meet a same-day despatch target while the carrier delivers late, so measures such as on time in full explained help you track the full journey. Keep despatch in the warehouse SLA and track delivery separately using carrier data.

A cut-off time only works if the warehouse has the people to meet it. At Gonini, every brand works closely with its account manager, so we have regular, up-to-date forecasts and we know when a promotion is coming. That lets the team plan staffing so every order goes out on time. It is a partnership, and it works both ways: the better the forecast, the more reliable the despatch.

Order Accuracy Commitments

Order accuracy measures how many orders ship with the right items and quantities. The SLA should state the target, the formula and the denominator, since accuracy per order, per line and per unit produce different numbers from the same performance. Per-order accuracy usually reflects the customer's experience best.

The SLA should also define where error counts come from. A rate based only on customer complaints undercounts, since many customers never report an error, so the most useful commitment combines internal catches with verified customer reports. Gonini's separate guide to order accuracy covers the measurement detail.

Goods-In and Putaway Turnaround

Goods-in turnaround measures how quickly delivered stock becomes available to sell. Slow goods-in leaves stock sitting in the warehouse while your site shows it as out of stock, which can cost sales during launches and restocks. A common commitment covers booking stock in within 24 to 48 hours of delivery, with faster targets for urgent deliveries.

The clock start matters here too. Some SLAs start the clock only when paperwork is complete or when a delivery was booked in advance, which lets late paperwork or unbooked deliveries fall outside the commitment. Agree what counts as a valid delivery, and what happens when your supplier sends stock without the agreed notice.

Returns Processing Time

Returns processing measures how quickly the provider receives, inspects and restocks or quarantines returned items. Slow returns delay customer refunds and keep sellable stock out of circulation, and our guide to returns handling standards covers the wider process. The SLA should define processed as reaching a final status in the system, rather than simply logged as received.

Returns volumes spike after peak, which is exactly when providers come under the most pressure. Check whether the returns commitment applies in January, and whether the provider plans extra capacity for post-peak returns.

Stock Accuracy and Shrinkage

Stock accuracy compares what the system says with what sits on the shelf. Poor stock accuracy causes oversells, cancelled orders and short shipments, which also show up in measures such as fill rate as a measure. A target of 99% or better, measured through regular cycle counts, is a reasonable starting point.

Shrinkage, meaning stock lost to damage, theft or unexplained loss, deserves its own clause. Agree how the provider reports shrinkage, what tolerance applies, and how it compensates you for losses above that tolerance. Check how that compensation interacts with the liability limits in the provider's standard terms, covered in the negotiation section.

Packaging Standards and Damage in Transit

An order that leaves on time can still fail if it arrives damaged. The SLA should state the packaging standard for your products and what counts as damage, because your customer's standard can be stricter than the warehouse's.

For example, a TV memorabilia brand we work with ships worldwide. A customer returned a coffee table book because of a very small scratch. We designed protective packaging with the brand that keeps each item in perfect condition and still shows the brand.

Agree the packaging standard for each product type, and how the provider reports and handles orders that arrive damaged.

Measurement and Reporting

An SLA is only as good as its measurement. Who records the data, how often you see it and what falls outside the count decide whether the commitments mean anything. The three sections below cover each one.

Who Measures, and Why That Matters

In most fulfillment relationships, the provider measures its own performance from its own systems. That is practical, since the warehouse holds the scans and timestamps, and yet it creates an obvious conflict of interest. Every definition in the SLA should be specific enough that you could rebuild the figure from raw data if needed.

Ask for access to the underlying data as well as monthly summaries. Order-level despatch timestamps, error logs and cycle count results let you check the reported figures against your own records. The principles in logistics KPIs in practice apply here: a measure you cannot audit is a measure you have to take on trust.

As an example of what to ask for, our own software records every order, so we can give each brand a breakdown by order line for any period it chooses. Internally, we review the trends every 6 weeks and every 6 months.

Reporting Frequency and Transparency

Monthly SLA reports are the minimum, with weekly reporting during peak. Each report should show performance against every commitment, the raw counts behind each percentage, and any exclusions applied. A report that shows only percentages makes it hard to tell whether a 99% figure covers 100 orders or 100,000.

Live data reduces the need to wait for reports. Many providers offer live order visibility through a client portal, which lets you spot problems as they happen. Agree that the SLA report reconciles to the live data, so the two sources tell the same story.

Exclusions, and the Ones to Push Back On

Exclusions are where fulfillment SLAs quietly lose their teeth. Carrier delay exclusions are the most common: if the carrier fails to collect on time, the provider may exclude every affected order from the despatch measure. That can be fair when the carrier is genuinely at fault, and it can also hide a provider that hands parcels over too late for the scheduled collection.

Peak-season carve-outs are the other big one. Some SLAs suspend commitments entirely between November and January, which removes protection during the months that matter most. Push for adjusted peak targets instead, such as a slightly later despatch window or a modestly lower accuracy threshold, rather than a full suspension.

Other exclusions to examine include force majeure clauses drawn very widely, orders containing items not yet received at goods-in, and undefined "client-caused delays". Each exclusion should have a clear definition and, where possible, a cap on how many orders it can remove from the count.

Remedies: What Actually Happens When It Is Missed

Remedies decide whether an SLA changes anything. The usual structure combines service credits for individual misses, an escalation path for repeated problems, and termination rights for persistent failure. Each layer needs clear triggers and amounts.

Service Credits and How They Are Usually Calculated

Service credits are fee reductions that apply when the provider misses a commitment. They are usually set as a percentage of the monthly fee, often on a ladder that credits a small percentage for a narrow miss and more for a wider one. As Bird & Bird notes, some agreements also set a maximum amount of credits that can be paid.

Two clauses decide how much credits are actually worth. The first is the cap, which limits total credits in a month however many commitments the provider misses. The second is the exclusive remedy clause. Lighthouse Law warns that when credits are the sole remedy, they become a substitute for a damages claim or a termination right, and the supplier's liability shrinks to the amount of the credit.

Credits also rarely match the real cost of failure. Tacto's procurement glossary notes that service credits often cover only a fraction of the actual damages, and a credit worth a few hundred pounds does little for a brand that lost thousands in sales during a missed peak. Treat credits as a performance signal rather than as compensation.

Escalation Paths and Remediation Periods

An escalation path sets out who you contact when a problem appears and who takes over if it continues. Most start with escalation and named account contacts and move up to operations directors and senior management. The SLA should name roles, response times and meeting cadences for each level.

Remediation periods give the provider time to fix a problem before stronger remedies apply. A reasonable period depends on the cause: a configuration error can be fixed in days, while a staffing or layout issue may take several weeks. The SLA should require a written remediation plan with dates and a way to measure progress.

Termination Rights and Notice

Termination rights protect you when performance stays poor. ContractKen, a contract review platform, describes chronic-failure clauses in customer-friendly agreements that allow termination for cause, with triggers such as two or more months in the lowest credit tier in any rolling twelve-month period. Without such a clause, a brand may have to sit out a long notice period while service stays poor.

Termination also needs a workable exit. The SLA should cover notice periods, stock release, final invoicing and data handover, so a provider cannot hold stock or data back during a dispute. Our guide to exiting and moving provider covers the practical side of a move.

What to Negotiate Before Signing

Most providers start from a standard SLA, and most will negotiate parts of it, especially for brands with meaningful volume. Focus on the clauses that decide whether the SLA works rather than on the headline targets. The list below covers the areas worth negotiating.

  • Measurement basis: the formula, the denominator and the system timestamp behind every commitment
  • Exclusion scope: clear definitions for carrier delay, force majeure and client-caused delays, with limits on their use
  • Peak treatment: adjusted targets during peak rather than full suspension
  • Reporting cadence: monthly reports with raw counts, weekly during peak, and access to order-level data
  • Credit calculation: the ladder, the monthly cap, and whether credits are your only remedy
  • Remediation window: written plans with dates, and the point at which stronger remedies apply
  • Exit terms: notice periods, termination for persistent failure, stock release and data portability
  • Liability limits: the per-tonne or per-unit limit in the provider's standard terms, and the cost of raising it

Raise these points early, ideally alongside questions to put to a provider during selection, since providers negotiate more freely before you commit. This guide is not legal advice, so have your own solicitor review the final wording.

Liability limits deserve special attention. The UK Warehousing Association's contract conditions, which many UK warehouses use, set a default liability limit of £100 per tonne for goods lost or damaged by the warehouse keeper, and the 2024 edition, in use since March 2024, keeps that default. A customer can pay an additional premium for a higher level of cover, and UKWA's own guidance says it is the customer's responsibility to cover losses above £100 per tonne. For lightweight, high-value eCommerce stock, £100 per tonne may cover only a tiny fraction of the value, so check which terms apply and arrange your own stock insurance.

Where SLAs Fall Short

Service credits rarely come close to covering the commercial damage of a missed peak. A credit worth a few percent of monthly fees cannot replace lost Black Friday sales, damaged reviews or customers who never return. The SLA gives you leverage and a record, and it does not make you whole.

Brands also enforce SLAs through relationships and escalation far more often than through the contract. Few brands take a fulfillment provider to court over a missed target, and most problems get resolved in operational meetings, with SLA data as the basis for the conversation. A good working relationship with a capable provider matters more day to day than the wording of any clause.

A tight SLA with a provider who cannot deliver is worse than a looser one with a provider who can. The tight SLA produces credits and disputes while your customers still receive late or wrong orders, while the looser SLA with a strong provider produces good service with less paperwork. Judge providers on their operations first and their contract second.

Smaller providers often cannot offer formal SLAs at all, and some still outperform larger providers that can. A small operation with experienced staff and a hands-on owner may give better service than a large one with a polished agreement. Our guide to fulfillment for smaller brands covers how to judge providers at that end of the market.

No SLA removes operational risk either. Warehouses face staffing shortages, system outages, carrier failures and bad weather, and good contingency planning on both sides matters as much as contractual commitments. Ask providers how they handle disruption, and keep your own plan for what you would do if your main site went down.

FAQ

What is a fulfillment SLA?

A contract schedule setting a 3PL's measurable service commitments. See what third party logistics covers for the wider service.

What should a 3PL SLA include?

Despatch cut-offs, accuracy, goods-in, returns, stock accuracy, packaging, uptime and response times, each with a formula and a remedy. See the metrics to hold a provider to.

Do fulfillment SLAs include penalties?

Usually service credits, capped and often small. Check them against what sits inside a fulfillment bill.

What is a reasonable despatch cut-off time?

There is no single standard. Ours is 2pm or later in every warehouse, with later cut-offs at some sites. Check the share of orders that must leave same day too, and see our pick and pack service.

Can an SLA exclude peak season?

Some do. Push for adjusted peak targets rather than suspension, and see our guide to planning for peak trading.

What happens if a 3PL repeatedly misses its SLA?

Credits apply, then escalation, then termination rights if the SLA includes them. Our guide to moving provider covers the exit.

‍

Freddy Bruce

As a part of the Gonini team, I help e-commerce brands strengthen their fulfilment operations across the UK, Germany, the Netherlands and the US. I work with merchants that want to simplify logistics, reduce costs and expand into new markets. I’m also building my own e-commerce brand, which gives me practical insight into the challenges founders face. In my writing, I share fulfilment strategies, growth lessons and real-world advice drawn from both sides of the industry.

By
Freddy Bruce
|
21/10/2026
17
min read

Switching 3PL Providers: A Step-by-Step Checklist

By
Freddy Bruce
|
9/7/2026
17
min read

Fulfilment Centre USA: What UK eCommerce Brands Need to Know Before Expanding