Logistics vocabulary for executives: the terms that change decisions (SLA, ASN, SOP, AQL, FIFO/FEFO)
Logistics Vocabulary for Executives: The Terms That Change Decisions
The terms below aren’t jargon to learn for its own sake. Each one names a concept that, when misunderstood, produces a different — and usually worse — operational or contractual outcome. This glossary defines them in plain language and connects each to the decision it shapes.
This is not a comprehensive list of logistics terminology. It is the short list of terms that consistently appear in 3PL agreements, onboarding conversations, and operational reviews — the ones where a misreading creates a gap between what was agreed and what actually runs.
Terms That Define the Agreement and the Process
These are the terms that appear in contracts, SOPs, and service reviews. Misreading them usually means agreeing to something different from what was expected.
SLA — Service Level Agreement
The tension most brands feel after signing with a 3PL often traces to SLA language that seemed clear at signing and proved ambiguous in practice. An SLA is not a performance guarantee — it is a definition of what is measured, how it is measured, and what happens when measurement shows underperformance.
SLA (Service Level Agreement): A contractual definition of a specific performance standard — what is being measured, the data source that determines compliance, the calculation method, and the remedy if the standard is not met. An SLA without a defined measurement methodology is an aspiration, not a commitment.
The most common SLA failure mode is a target without a calculation. “99% order accuracy” means nothing without knowing: what counts as an error, how errors are detected, who reports them, and over what time period the percentage is calculated. An SLA that measures errors based on customer complaints will show higher accuracy than one that measures against an internal audit of pick records. Neither is wrong — but they produce different numbers from the same operation. Before accepting any SLA, confirm the measurement definition and the data source.
SOP — Standard Operating Procedure
The difference between a fulfillment operation that performs consistently and one that varies by day or shift is usually not capability — it is whether the process is written down and trained against.
SOP (Standard Operating Procedure): A documented, step-by-step instruction for a specific task that defines how it should be performed, in what sequence, by whom, and under what conditions. SOPs exist at every stage of the fulfillment flow: inbound verification, putaway, pick, pack, dispatch, returns triage.
Why this matters for executives: if a 3PL cannot show you written SOPs for inbound, pick and pack, and returns, the process isn’t systematized — it depends on individual knowledge and habit. That means performance varies based on who happens to be on shift. When you ask for SOPs during due diligence and receive a verbal description instead of a document, you are observing the operational reality, not a documentation gap.
SLA Breach Protocol
Connected to SLA but worth naming separately: the breach protocol is what actually governs what happens when an SLA threshold is missed. Without a defined protocol — who is notified, what investigation is triggered, what remedy applies — an SLA threshold is a number without consequence. Review this explicitly, not as a legal formality but as an operational design question.
Terms That Govern How Inventory Moves
These terms describe how stock is tracked, sequenced, and documented as it moves through the warehouse. Misunderstanding them typically surfaces as inventory accuracy problems or compliance failures.
FIFO and FEFO
When a warehouse runs multiple lots of the same SKU received at different times, the order in which units are picked determines shelf life, compliance, and returns risk. Getting this wrong is invisible until a customer receives a near-expiry product or an audit reveals non-compliant stock rotation.
FIFO (First In, First Out): A stock rotation method in which the earliest-received units of a SKU are picked and shipped before units received later. Relevant for any product with a shelf life, a seasonality risk, or a lot-number traceability requirement.
FEFO (First Expired, First Out): A rotation method in which the units with the earliest expiry date are picked first, regardless of when they were received. Used when different lots of the same SKU may have different expiry dates — common in food, cosmetics, supplements, and healthcare products.
If your product has an expiry date or a lot traceability requirement, FEFO is the relevant operating standard. If a 3PL proposes FIFO for expiry-sensitive SKUs without confirming the lot structure, that is a process gap worth addressing before onboarding.
Lots and Batches
The scenario where lot tracking becomes critical is not when everything is running smoothly — it’s when a compliance issue, an expiry question, or a potential recall requires you to identify exactly which production run is affected and where those units currently are.
A lot (or batch) is a group of units produced under the same conditions at the same time, identified by a shared code. Lot tracking means the warehouse can identify not just “we have 500 units of SKU X” but “we have 200 units from lot A and 300 from lot B, with different expiry dates.”
Lot-level tracking is necessary for any FEFO operation, any product subject to a potential recall, and any B2B channel that requires lot documentation in shipping paperwork. If your product fits any of these categories and lot tracking is not confirmed in the 3PL’s operating setup, it is worth raising explicitly rather than assuming it is standard practice.
ASN — Advanced Shipping Notification
The time gap between a 3PL receiving a shipment and that shipment appearing in live inventory is directly influenced by whether an ASN was provided and whether it was accurate.
ASN (Advanced Shipping Notification): A structured document sent by the supplier or shipper to the receiving warehouse before a shipment arrives, listing the contents of the shipment — SKUs, quantities, lot numbers if applicable, and packaging configuration. An accurate ASN allows the receiving team to prepare for the inbound, verify against a known expectation, and move confirmed stock into live inventory faster.
The operational consequence of a missing or inaccurate ASN is a slower, more error-prone receiving process: the warehouse team must create the receipt from scratch, which takes longer and introduces more potential for discrepancy. For operations with multiple active SKUs or high inbound frequency, ASN compliance from suppliers is a meaningful variable in inbound cycle time.
Terms That Govern Timing, Quality, and Proof
These terms appear in operating discussions around cut-offs, quality inspections, and delivery confirmation. Each one governs a decision point that, if undefined, creates a dispute.
Cut-Off
Cut-offs are one of the most common sources of misalignment between a brand and a 3PL in the first weeks of operation. The brand assumes orders placed before a certain time ship the same day. The 3PL has a specific internal cut-off that may not match.
Cut-off: The daily deadline by which an order must be received by the 3PL’s fulfillment system to be processed and dispatched on that day. Orders received after the cut-off are queued for the following business day. Cut-offs are set by the 3PL’s internal operating rhythm and may vary by carrier, order type (B2C vs B2B), or channel.
For customer-promise management, confirm the cut-off before committing to any delivery windows. A Shopify store promising same-day dispatch until 3pm, with a 3PL whose cut-off is 1pm, will generate systematic misses without anyone making an error.
AQL — Acceptable Quality Level
When a brand outsources quality inspection to a 3PL or requires inspection on inbound goods, AQL defines how many units get inspected and what defect rate determines pass or fail for the entire lot.
AQL (Acceptable Quality Level): A statistical sampling standard that defines: how many units from a lot are inspected, how inspected units are classified by defect type (critical, major, minor), and what defect counts in the sample trigger acceptance or rejection of the full lot. Common AQL standards referenced in B2B contracts are AQL 1.0, 2.5, and 4.0 — lower numbers mean stricter inspection.
Why it matters for executives: agreeing to “quality inspection” without specifying AQL level and defect classification produces unpredictable results. Two 3PLs can both claim to “do QC” while one samples 5% of units with no defined failure threshold and the other runs AQL 2.5 with documented defect logs. If inspection has commercial implications — accepting or rejecting a supplier shipment, clearing goods for a retail channel — define AQL explicitly.
POD — Proof of Delivery
The final link in the outbound chain is confirmation that the order reached its destination. For B2C, this is typically a carrier tracking event showing delivered status. For B2B, it may include a signed receipt, a delivery note, or a formal acknowledgment from the buyer.
POD (Proof of Delivery): A documented record confirming that a shipment was received at the delivery address at a specific date and time. For B2C, a carrier scan event serves as POD. For B2B and retail deliveries, a signed delivery note or formal receipt may be required.
POD is relevant for dispute resolution and for triggering payment in B2B transactions with delivery-conditional payment terms. A 3PL that ships without generating or capturing POD creates a chain that cannot be audited when a delivery dispute arises.
Frequently Asked Questions
Q: What is the difference between an SLA and a KPI in a 3PL agreement? A: A KPI (Key Performance Indicator) is a metric used to track operational performance — order accuracy rate, on-time dispatch rate. An SLA is a contractual commitment: it defines a specific performance threshold, the measurement methodology, and the consequences if the threshold is not met. A KPI without SLA terms is a monitoring tool. An SLA without a defined measurement method is a target without enforcement. Both are only useful when they are specific enough to be verifiable.
Q: Does every product require FEFO stock rotation? A: No. FEFO is relevant for products with expiry dates, recommended use-by dates, lot traceability requirements, or perishability risk. Products without any of these constraints can operate under FIFO. The question to confirm with a 3PL is whether lot-level tracking is active for your specific SKUs — not whether FEFO is listed as a capability, but whether it is applied to your product’s inventory at the operational level.
Q: What happens when an ASN is not provided before a shipment arrives? A: The receiving team creates the inbound record from scratch at the time of receipt, which takes longer and introduces more risk of discrepancy. Without an expected quantity to verify against, short receives may go undetected. The time from dock to live inventory is typically longer without an ASN, which affects how quickly newly arrived stock is available for order fulfillment.
Q: What AQL level is standard for ecommerce fulfillment? A: There is no universal standard. AQL level depends on the product category, the channel, and the commercial implications of a defect. AQL 2.5 is common in consumer goods for major defects. Retail channels often specify their own inspection requirements that must be met on delivery. If you’re outsourcing inspection to a 3PL, confirm the defect classification categories and the sampling plan before the first inspection run — not after a lot has been accepted or rejected.
Q: How does cut-off affect customer promise management? A: Directly. The customer-facing delivery promise depends on the dispatch date, which depends on the cut-off. If a brand promises next-day delivery for orders placed before 2pm, the 3PL’s cut-off must be later than 2pm — accounting for the time to process, pick, pack, and tender to the carrier. If the cut-off doesn’t support the promise, the promise will fail systematically. Confirming cut-offs before setting customer-facing delivery windows is a setup requirement, not an afterthought.
Q: Why is POD relevant for B2B fulfillment but less discussed in B2C? A: In B2C, carrier tracking events serve as de facto POD — a delivered scan at the customer’s address is the standard record. In B2B, deliveries often go to loading docks, buyers require signed delivery notes for their own records, and payment terms may be conditional on confirmed receipt. For retail supplier deliveries, a missing or incomplete POD can result in a deduction or chargeback from the retailer. The operational requirement for B2B POD is stricter and needs to be defined in the 3PL setup, not assumed.
If you’re setting up a 3PL relationship and want to confirm that the operating terms reflect these definitions clearly — or if any of these terms appeared in a proposal and need clarification — share the document and we’ll review it with you.