{"id":16333,"date":"2026-09-28T20:56:56","date_gmt":"2026-09-28T20:56:56","guid":{"rendered":"https:\/\/www.insitusales.com\/?p=16333"},"modified":"2026-09-28T20:56:56","modified_gmt":"2026-09-28T20:56:56","slug":"dsd-truck-inventory-route-settlement","status":"publish","type":"post","link":"https:\/\/www.insitusales.com\/en\/dsd-truck-inventory-route-settlement\/","title":{"rendered":"DSD Truck Inventory and Route Settlement: From Warehouse Load-Out to End-of-Day Reconciliation"},"content":{"rendered":"<p>In a truck-stock DSD operation, the vehicle carries inventory for sales made during customer visits. The warehouse replenishes that vehicle, the representative sells and invoices from onboard stock, and route accounting reconciles the products and money at the end of the route.<\/p>\n<p>The day&#8217;s actual sales determine how the load is used. One store buys more than usual. Another skips its purchase. A third returns damaged goods from a previous visit. Each event changes the inventory or financial records associated with the route.<\/p>\n<p>For direct store delivery (DSD) teams, the objective is straightforward: explain where every unit went, what each customer owes, and which payments were collected. This guide focuses on the sell-from-truck model, also called van sales or autoventa. The warehouse prepares a vehicle load; customer orders are not picked and fulfilled at the warehouse in this workflow.<\/p>\n<h2>How do warehouse inventory and route accounting connect?<\/h2>\n<p>The warehouse holds replenishment stock and records transfers to and from vehicles. Route accounting follows what happens to that stock on the route: sales, invoices, collections, customer returns, and remaining quantities. Their main handoffs are truck loading and receiving stock back from the route.<\/p>\n<p>A WMS can support storage locations, stock counts, and load preparation. The same warehouse may also fulfill pre-sales orders for another part of the business, but that is a separate process from replenishing a DSD truck.<\/p>\n<p>The exact division varies by software and configuration. Use the following table to assign responsibilities during implementation rather than assuming every platform handles them in the same way.<\/p>\n<div class=\"table\">\n<table>\n<tr>\n<th>Activity<\/th>\n<th>Warehouse responsibility<\/th>\n<th>Route responsibility<\/th>\n<th>Shared control<\/th>\n<\/tr>\n<tr>\n<td>Plan truck replenishment<\/td>\n<td>Confirm available stock and applicable lots<\/td>\n<td>Request quantities for expected route demand<\/td>\n<td>Consistent item and unit definitions<\/td>\n<\/tr>\n<tr>\n<td>Load the vehicle<\/td>\n<td>Confirm stock leaving the warehouse<\/td>\n<td>Confirm stock accepted onto the truck<\/td>\n<td>Transfer reference and quantity acknowledgment<\/td>\n<\/tr>\n<tr>\n<td>Sell from truck stock<\/td>\n<td>Maintain warehouse stock separately<\/td>\n<td>Sell, invoice, and hand over goods at the stop<\/td>\n<td>Vehicle, sale, and invoice references<\/td>\n<\/tr>\n<tr>\n<td>Accept a return<\/td>\n<td>Inspect and decide stock disposition<\/td>\n<td>Record quantity, condition, and reason<\/td>\n<td>Return reference and credit status<\/td>\n<\/tr>\n<tr>\n<td>Close the route<\/td>\n<td>Verify stock received back<\/td>\n<td>Reconcile stock and collections<\/td>\n<td>Reviewed exceptions and approvals<\/td>\n<\/tr>\n<tr>\n<td>Synchronize records<\/td>\n<td>Reconcile warehouse movements<\/td>\n<td>Reconcile route transactions<\/td>\n<td>Accepted, rejected, and pending ERP records<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Route optimization addresses a separate question: which stops should a vehicle visit, and in what sequence? A route can be geographically efficient and still have inventory or collection discrepancies. Evaluate both processes.<\/p>\n<h2>The warehouse-to-route workflow<\/h2>\n<p><img decoding=\"async\" alt=\"Six stages connecting truck-stock planning, warehouse-to-truck transfer, sales at customer stops, returns, route settlement, and ERP confirmation.\" src=\"https:\/\/www.insitusales.com\/wp-content\/uploads\/workflow.png\" title=\"\"><\/p>\n<h3>See DSD route accounting in action<\/h3>\n<figure class=\"video-embed\"><iframe src=\"https:\/\/www.youtube-nocookie.com\/embed\/4je1ap2_sY8\" title=\"DSD Route Accounting in Action | From Delivery to Signoff | inSitu Sales\" width=\"800\" height=\"450\" style=\"display:block;width:100%;max-width:800px;aspect-ratio:16\/9;height:auto;border:0\" loading=\"lazy\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" allowfullscreen><\/iframe><figcaption>This short inSitu Sales video shows the customer-stop portion of DSD: using truck inventory, invoicing the items the customer takes, collecting payment, and capturing signoff. The warehouse load-out and end-of-day reconciliation are explained in the steps below.<\/figcaption><\/figure>\n<h3>1. Plan the truck&#8217;s inventory<\/h3>\n<p>Plan the vehicle&#8217;s product mix and quantities using expected demand, sales history, route frequency, available stock, and vehicle capacity. Account for inventory already on the truck so the load request represents the replenishment it needs.<\/p>\n<p>Use consistent item codes and units. A warehouse may load cases while a representative sells individual units; define the conversion before departure. Where products require lot or expiration tracking, preserve those identifiers on the warehouse-to-truck transfer and relevant sales records.<\/p>\n<h3>2. Confirm the warehouse-to-truck transfer<\/h3>\n<p>Loading is a custody handoff. Record the source location, destination vehicle, product, unit, quantity, and applicable lot. The warehouse&#8217;s dispatched quantity and the driver&#8217;s accepted quantity should agree, or the discrepancy should remain visible for resolution.<\/p>\n<p>Avoid treating a transfer to a truck as a completed customer sale. The goods have moved locations, but they may still be distributor inventory. Define the ownership and posting rules with the people responsible for your books.<\/p>\n<h3>3. Sell, invoice, and deliver from the truck<\/h3>\n<p>At the stop, the representative confirms what the customer wants and what is available onboard, applies the customer&#8217;s terms, and completes the sale. Record the quantities handed over, create the invoice, and capture supported collections and the customer&#8217;s acknowledgment.<\/p>\n<p>A case the customer decides not to buy remains onboard. Reduce truck stock by the quantities actually sold and handed over. Keep each sale linked to the correct vehicle and customer so the ending inventory can be explained transaction by transaction.<\/p>\n<h3>4. Separate returns from credits<\/h3>\n<p>A physical return and a financial credit are related events, but they are not interchangeable. Record what came back, why it came back, its condition, and whether a credit was approved.<\/p>\n<p>Goods awaiting inspection should remain distinguishable from stock available for sale. A credit issued without a physical return changes the customer&#8217;s balance without increasing truck inventory. Likewise, collecting an old damaged product adds physical units to the vehicle even if approval of the credit is still pending.<\/p>\n<h3>5. Reconcile stock and collections<\/h3>\n<p>Before unloading, compare the actual truck count with the expected quantity. Then reconcile collections against the route&#8217;s recorded payment activity. Resolve or explicitly assign discrepancies before marking the route complete.<\/p>\n<p>Do not expect invoice totals to equal cash collected. Some customers buy on credit; some payments settle older invoices. Review each collection against the invoice or account balance to which it applies.<\/p>\n<h3>6. Confirm the ERP handoff<\/h3>\n<p>Sending a transaction is only part of the handoff. The receiving system must accept it, and the originating record needs a traceable status or reference.<\/p>\n<p>For supported integrations, confirm the objects exchanged, direction, timing, failure handling, and duplicate prevention. A route may be operationally complete while an invoice or payment is still waiting for synchronization. Make that distinction visible to the office team.<\/p>\n<h2>A brief distinction: DSD truck sales versus pre-sales<\/h2>\n<p><img decoding=\"async\" alt=\"Two workflows: pre-sell starts with an order before picking and loading; van sales starts with a planned load before selling at the customer stop. Both converge on reconciliation and settlement.\" src=\"https:\/\/www.insitusales.com\/wp-content\/uploads\/selling-models.png\" title=\"\"><\/p>\n<p>In truck-stock DSD, inventory is loaded before sales happen at the stops. In pre-sales, the customer places an order first; the warehouse then fulfills it for later delivery. <a href=\"https:\/\/www.insitusales.com\/en\/solutions\/field-sales-app\/dsd\/\">inSitu&#8217;s workflow definitions<\/a> distinguish these processes. Some vendors use \u201croute accounting\u201d for systems supporting both, as illustrated by <a href=\"https:\/\/www.laceupsolutions.com\/solutions\/dsd-route-accounting-software\/\" target=\"_blank\" rel=\"noopener\">LaceUp&#8217;s DSD and pre-sales description<\/a>. Here, the main workflow and reconciliation example concern sales from truck stock.<\/p>\n<h2>A practical truck-inventory reconciliation example<\/h2>\n<p>The following example is illustrative and does not describe a customer result. It tracks one product in cases, before the vehicle is unloaded. All physical units are included; saleable and damaged quantities are classified separately.<\/p>\n<p><strong>Expected closing truck stock = opening stock + loads + physical customer returns + transfers in \u2212 deliveries \u2212 transfers out \u2212 documented physical removals.<\/strong><\/p>\n<div class=\"table\">\n<table>\n<tr>\n<th>Movement<\/th>\n<th>Cases<\/th>\n<th>Running balance<\/th>\n<\/tr>\n<tr>\n<td>Opening stock<\/td>\n<td>0<\/td>\n<td>0<\/td>\n<\/tr>\n<tr>\n<td>Loaded from warehouse<\/td>\n<td>+120<\/td>\n<td>120<\/td>\n<\/tr>\n<tr>\n<td>Delivered to customers<\/td>\n<td>\u221290<\/td>\n<td>30<\/td>\n<\/tr>\n<tr>\n<td>Physical returns collected from customers<\/td>\n<td>+5<\/td>\n<td>35<\/td>\n<\/tr>\n<tr>\n<td>Transferred to another vehicle<\/td>\n<td>\u22123<\/td>\n<td>32<\/td>\n<\/tr>\n<tr>\n<td>Expected stock before unloading<\/td>\n<td><\/td>\n<td><strong>32<\/strong><\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Suppose the physical count is 31 cases. The variance is <strong>31 \u2212 32 = \u22121 case<\/strong>, which needs investigation. If two of those 31 cases are damaged and still onboard, the physical total remains 31: 29 saleable and two held separately. Damage classification alone does not remove a case from the truck.<\/p>\n<p>When the vehicle is unloaded, record the transfer back to the warehouse or the designated inspection location. Do not subtract the same return twice: once as a customer return and again as an assumed stock loss. The movement history should explain both the physical location and the condition of the goods.<\/p>\n<h2>Exceptions to test before rollout<\/h2>\n<p>Build a demonstration around difficult transactions from your own operation. A successful happy-path demo does not establish how the system handles an interrupted sync, a partial delivery, or a return without an invoice reference.<\/p>\n<div class=\"table\">\n<table>\n<tr>\n<th>Test scenario<\/th>\n<th>What the team should demonstrate<\/th>\n<\/tr>\n<tr>\n<td>Customer changes quantity before the sale is finalized<\/td>\n<td>Invoice and stock reflect only the goods sold and handed over<\/td>\n<\/tr>\n<tr>\n<td>Driver collects an old return<\/td>\n<td>Product, condition, reason, and credit decision stay traceable<\/td>\n<\/tr>\n<tr>\n<td>Cases are sold as individual units<\/td>\n<td>Stock movements use a consistent conversion<\/td>\n<\/tr>\n<tr>\n<td>Device loses connectivity<\/td>\n<td>Supported activity is saved and reconciled after reconnection<\/td>\n<\/tr>\n<tr>\n<td>A transaction is retried<\/td>\n<td>The receiving system avoids a duplicate business transaction<\/td>\n<\/tr>\n<tr>\n<td>ERP rejects an invoice<\/td>\n<td>A visible error has an owner and a recovery process<\/td>\n<\/tr>\n<tr>\n<td>Truck count differs from expected<\/td>\n<td>Variance is investigated and any adjustment is authorized<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Offline order entry and invoicing do not automatically mean electronic payment authorization works offline. Confirm the payment provider&#8217;s requirements separately. Also test simultaneous activity if multiple people or devices can transact against the same stock.<\/p>\n<h2>How to measure whether the connection is working<\/h2>\n<p>Measure a baseline before introducing a new workflow. Use the same definitions and comparable routes when reviewing the results.<\/p>\n<ul>\n<li><strong>Settlement time:<\/strong> minutes from the start of route review to approved closure.<\/li>\n<li><strong>Inventory variance:<\/strong> the difference between counted and expected units, tracked by item and unit of measure.<\/li>\n<li><strong>Unresolved exceptions:<\/strong> discrepancies still awaiting a decision at the agreed cutoff.<\/li>\n<li><strong>Manual re-entry:<\/strong> transactions that office staff must enter again after field capture.<\/li>\n<li><strong>Integration acceptance:<\/strong> eligible transactions accepted by the receiving system within the agreed service window.<\/li>\n<\/ul>\n<p>Record the observation period, route count, product mix, and any process changes that might explain a result. Avoid combining positive and negative item variances into one net number that hides discrepancies. Track quantity accuracy and financial reconciliation separately.<\/p>\n<h2>Where inSitu Sales fits<\/h2>\n<p>inSitu Sales publicly documents connected DSD workflows covering truck inventory, mobile invoicing, collections, returns, and route settlement, with eligible transactions synchronized through supported accounting and ERP integrations. Its <a href=\"https:\/\/www.insitusales.com\/en\/solutions\/field-sales-app\/dsd\/\">DSD and van-sales page<\/a> describes supported offline activity and configuration considerations for lot-controlled operations.<\/p>\n<p>Use a demonstration to validate your actual order-taking, loading, return, and settlement process. Bring representative items, units, customer pricing, devices, and exceptions. Review the relevant <a href=\"https:\/\/www.insitusales.com\/en\/integrations\/\">integration options<\/a> and <a href=\"https:\/\/www.insitusales.com\/en\/customer-success\/\">customer success stories<\/a> alongside the workflow requirements.<\/p>\n<p><strong>Want to test your warehouse-to-route handoff? <a href=\"https:\/\/www.insitusales.com\/en\/contact\/\">Talk with inSitu Sales<\/a> and walk through one complete route\u2014from the first load to the final stock count and accepted back-office transaction.<\/strong><\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Does an ERP replace route accounting software?<\/h3>\n<p>Some ERP systems include route capabilities; others rely on connected applications. Evaluate the complete workflow, including vehicle stock, mobile transactions, returns, reconciliation, and supported offline activity. The important question is whether each required event can be recorded and traced through to the books.<\/p>\n<h3>What is route settlement?<\/h3>\n<p>Route settlement is the review of a route&#8217;s inventory and transactions at an agreed cutoff. It compares expected and actual stock, checks deliveries, returns, credits, and collections, and identifies discrepancies that need resolution. Operational closure and completion of ERP synchronization may occur at different times.<\/p>\n<h3>Why does a WMS need truck inventory information?<\/h3>\n<p>Warehouse availability alone does not show what is already on a vehicle or returning from customers. Connected transfers let the warehouse distinguish stock still on a route from goods physically received back. This supports more reliable replenishment, counting, and return handling.<\/p>\n<h3>Can DSD route accounting work offline?<\/h3>\n<p>Supported mobile tasks can work offline when the application stores the necessary data and transactions locally. Test which functions remain available, how stock and pricing are refreshed, and what happens when devices reconnect. Confirm electronic payment requirements separately with the provider.<\/p>\n<h3>What should I ask a software vendor to demonstrate?<\/h3>\n<p>Ask for a complete route using your products and units: loading, a normal delivery, a partial refusal, an additional sale, an old customer return, a stock discrepancy, and an integration failure. Require the team to show the records at each step and explain how exceptions are resolved.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a truck-stock DSD operation, the vehicle carries inventory for sales made during customer visits. The warehouse replenishes that vehicle, the representative sells and invoices from onboard stock, and route accounting reconciles the products and money at the end of the route. The day&#8217;s actual sales determine how the load is used. One store buys&nbsp;&hellip;<\/p>\n","protected":false},"author":1,"featured_media":16330,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[248,9],"tags":[],"class_list":["post-16333","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-insitu-inventory","category-instructional-guide"],"featured_image_src":"https:\/\/www.insitusales.com\/wp-content\/uploads\/cover.png","author_info":{"display_name":"insitu","author_link":"https:\/\/www.insitusales.com\/en\/author\/insitu\/"},"_links":{"self":[{"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/posts\/16333","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/comments?post=16333"}],"version-history":[{"count":3,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/posts\/16333\/revisions"}],"predecessor-version":[{"id":16336,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/posts\/16333\/revisions\/16336"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/media\/16330"}],"wp:attachment":[{"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/media?parent=16333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/categories?post=16333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.insitusales.com\/en\/wp-json\/wp\/v2\/tags?post=16333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}