When a terminal loads a truck or rail car, it is handing over a product whose quality it may later have to prove. A retained sample loop is the small in-line system that captures a representative bit of every load into a sealed container so that if the customer disputes the quality weeks later, the terminal has kept physical evidence of what actually shipped. It is a quiet piece of the loading rack that most drivers never notice, but it can settle an argument that would otherwise come down to one party's word against another. This page explains how the loop draws its sample, how the automation system ties that retain to the bill of lading, and why a sampler fault has to stop the load.
Retained Sample Loop in one line: A retained sample loop is an in-line sampling system on a loading rack that draws a small representative aliquot from the flowing product during each load and collects it into a sealed sample can that the terminal keeps as a quality retain. If a customer later disputes what was delivered, the terminal can pull the tagged retain, tied to that load's bill of lading, and test the exact product that shipped. The load automation system logs the retain and treats a sampler fault as a condition that can hold or stop the load.
The core idea of a retained sample loop is to divert a tiny, controlled fraction of the product stream out of the main loading line, through a small sampler, and into a collection can, then return the rest to the line or let the sampled drops accumulate in the retain container. On a loading rack the goal is usually a spot or accumulated grab that represents the whole load rather than a continuously proportioned composite, because each truck or rail load is a discrete transaction and the terminal wants one retain per bill of lading. A small pump or a probe that dips into the moving stream extracts fixed-volume shots on a timer or on pulses from the load meter, so the can ends up holding a blend drawn across the duration of the load rather than a single instant.
The volume per load is deliberately modest, typically enough to fill a standard sample can that can later be split for laboratory testing and re-tested if needed, without wasting product or creating a disposal burden. What matters is that the drops come from a point in the line where the product is well mixed and moving, so the retain genuinely reflects what went onto the vehicle. A grab taken from a dead leg or from the very first slug of a load would not be representative, so the sample take-off is placed downstream of the meter in flowing product, and the sampler only fires while the load is actually running.
Once the load finishes, the can is capped, sealed, and labeled so its chain of custody is intact. The seal and the tag are what give the retain its evidentiary value: a customer or a laboratory can see that the container was closed at the terminal, was not opened or topped up afterward, and corresponds to a specific load. Terminals store these retains for a defined period so that a claim raised after the product has been delivered, blended, or consumed can still be checked against the physical evidence the terminal kept.
A retained sample loop on a loading rack is not the same thing as a flow-proportional composite sampler on a pipeline, even though both pull product off a moving stream into a container. A pipeline composite sampler is built to represent a continuous, long-duration custody transfer where the flow rate varies over hours or days, so it must inject a shot of sample in strict proportion to the volume that has passed, adding more grabs when flow is high and fewer when it is low, so the accumulated composite matches the overall delivered quality. That proportionality is essential when the transaction quantity and quality both feed a settlement.
A loading-rack retain, by contrast, covers a single vehicle load that lasts minutes, and its purpose is primarily to preserve evidence rather than to compute a settlement quality. Terminals often accept a simpler grab regime, taking fixed shots on a timer or on meter pulses across the load, because the product feeding the rack has usually already been certified from tank, and the retain exists to defend against a later dispute rather than to define the invoice. The distinction matters when specifying the system, because a rack retain can be a much smaller and simpler loop than the flow-proportional sampler a fiscal pipeline transfer would demand.
That said, the boundary is not absolute. Some rack samplers do pace their grabs off the load meter to approximate flow proportionality within a single load, which is sensible when the flow ramps up and down during loading. The practical design question is whether the retain has to stand up as a representative composite for quality settlement, in which case flow-paced grabs and proper mixing matter a great deal, or whether it is a defensive retain of already-certified product, in which case a robust, reliably captured grab per load is the priority.
The retain only has value if it can be tied unambiguously to the load it came from, which is where the terminal automation and load-rack control tie in. When a driver authorizes a load, the system already knows the order, the product, the destination, and the bill of lading number it will produce. As the load runs and the sampler fires, the controller records that a retain was taken, the can or position it went into, and the associated transaction, so the printed bill of lading and the physical sample can be cross-referenced later. A retain sitting on a shelf with a can number that maps back to a BOL in the system is far more defensible than an unlabeled bottle.
Because the retain is evidence, a sampler that is not working is a real problem, and the load logic treats it as one. The automation system typically monitors the sampler for the conditions that would mean no valid retain is being captured, such as the sampler not firing, the collection container being full, or a fault reported by the sampler controller. Depending on the terminal's policy, one of those conditions can raise an alarm, hold the permissive so a new load cannot start, or stop an in-progress load until the operator addresses it. The point is that shipping product with no retain undermines the whole reason the loop exists.
Terminals keep retains because the alternative, having no physical evidence of shipped quality, exposes them to claims they cannot rebut. If a customer reports off-spec product, contamination, or the wrong grade, the terminal can pull the sealed retain for that BOL and have it tested, which either confirms the terminal shipped on-spec product or reveals a genuine problem at the rack. Keeping the retain, tying it to the BOL in the automation records, and interlocking the load on the sampler together turn a subjective dispute into something that can be resolved against a sealed, dated, traceable sample.
They keep retains so they can defend product quality after the fact. If a customer later claims the product was off-spec, contaminated, or the wrong grade, the terminal can pull the sealed, dated retain for that load and have it tested, which either clears the terminal or reveals a genuine problem. Without a retain, a quality dispute comes down to unverifiable claims, so the physical sample is the terminal's evidence of what it actually shipped.
A pipeline composite sampler injects sample shots in proportion to the volume flowing over a long, variable-rate transfer so the accumulated composite represents the whole delivery for settlement. A loading-rack retain usually covers one short vehicle load and exists to preserve evidence, so it often takes fixed grabs on a timer or on meter pulses rather than strict flow proportionality. The rack retain is generally a smaller, simpler loop unless the terminal needs it to represent a settlement quality.
The automation system treats a sampler fault as a condition that can hold or stop the load, because shipping without capturing a valid retain defeats the purpose of the loop. Depending on terminal policy, a sampler not firing, a full collection can, or a controller fault can raise an alarm, block a new load from starting, or halt an in-progress load until an operator intervenes. The exact response is configured so the terminal does not unknowingly release product with no retain.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.