ERP Inventory for Industrial Distribution

ERP Inventory for Industrial Distribution: Landed Cost, Drop Ship, Consignment, and High-SKU Valuation

No ERP replacement. The distributor owns it at completion.

Landed cost allocation at receipt, drop ship transactions that close PO and SO together, consignment inventory tracked at customer sites, and automated valuation across 80,000+ active SKUs, connected to the ERP already running in the operation.

Book a Discovery Call
What It Requires

What Industrial Distribution ERP Inventory Requires That Standard Inventory Modules Miss

An ERP inventory module configured for a manufacturer tracks production orders, WIP, and finished goods. An ERP inventory module configured for an industrial distributor must handle a fundamentally different set of operational and financial requirements, such as high SKU counts, variable sourcing costs, drop ship fulfillment, vendor-owned consignment stock at customer sites, and freight cost allocation across multi-line POs.

For industrial distributors selling to B2B customers in MRO, fluid power, electrical, HVAC/R, and safety supply, generic distribution ERP software rarely accounts for all four of these mechanics at once. Four requirements separate industrial distribution ERP inventory from standard inventory management.

01

Landed Cost Allocation

Every import shipment carries freight, customs duties, insurance, and handling costs that must be allocated to individual inventory items before they can be sold at an accurate margin.

Standard ERP receiving books inventory at the purchase price on the PO. A landed cost module allocates freight and duty to the unit cost of each item received, so gross margin reflects the true cost of sourcing.

02

Drop Ship Accounting

When a distributor takes a customer order and ships directly from the supplier to the customer, never touching the inventory, the ERP must handle a three-way transaction.

Supplier PO, customer sales order, and shipment confirmation that closes both simultaneously without the item entering the distributor's inventory.

03

Consignment at Customer Sites

Industrial distributors frequently place vendor-managed inventory at customer locations, such as toolroom cribs or on-site supply stations. This inventory remains on the distributor's balance sheet until the customer consumes it.

Standard ERP inventory sees this stock as “at customer” with an unknown quantity until consumption is reported.

04

High-SKU Valuation

An MRO distributor carrying 80,000 to 200,000+ active SKUs cannot review inventory valuation manually.

The ERP must calculate ABC velocity classification, identify slow movers, and generate write-down recommendations automatically.

Landed Cost

Landed Cost Calculation in Distribution ERP: How Freight and Duty Reach the Unit Cost

Landed cost is the total cost of acquiring inventory, including purchase price, inbound freight, customs duties, insurance, port fees, and domestic cartage, allocated to each unit or SKU received. Without it, a distributor's gross margin calculation uses only the purchase price and systematically understates the true cost of goods on imported items.

Capture All Cost Components at Receipt in the landed cost calculation
Capture

Capture All Cost Components at Receipt

It captures inbound freight (actual, not estimated), customs duty by tariff code, insurance, port and handling fees, and domestic delivery cost.

Each arrives as a separate line item rather than a single lump freight charge.

Allocate to Items by a Defined Method in the landed cost calculation
Allocate

Allocate to Items by a Defined Method

It is allocated by weight (actual freight per pound applied to each item's weight), by value (freight pro-rated as a percentage of each item's line value), by quantity (freight divided evenly across units), or by volume.

Each method produces a different per-unit cost, so the method should match the actual freight billing basis.

Update the Carrying Value at Receipt in the landed cost calculation
Post

Update the Carrying Value at Receipt

The ERP posts the landed cost allocation at the moment of receipt, not at month-end when the freight invoice arrives.

If the invoice arrives after the items are already sold, the ERP must retroactively adjust the COGS already posted.

Handle Variance in the landed cost calculation
Variance

Handle Variance

When estimated freight differs from the actual invoice, common on international shipments, the ERP must post a landed cost variance.

Silently adjusting inventory that has already been partially sold is not an acceptable alternative.

Landed Unit Cost = (Purchase Price + Freight Allocation + Duty Allocation + Other Costs) / Units Received

FIFO → Lot Precision. Average → Scale.

Landed cost interacts differently with each costing method. Under FIFO, each received lot carries its own landed unit cost, so the first lot received hits COGS first, accurate but computationally intensive at high SKU counts. Under average costing, a landed cost shipment blends into the moving average for the SKU, which is simpler at scale, but it loses lot-level cost precision.

Drop Ship

Drop Ship Accounting in Distribution ERP: The Three-Way Transaction

Drop ship fulfillment, where the supplier ships directly to the customer, is common in industrial distribution for oversized items, specialty items with long lead times, and emergency same-day fulfillment from supplier stock. The ERP must handle the transaction correctly without creating a ghost inventory receipt that never physically occurred.

Where it usually breaks

Most mid-tier ERP systems support drop ship as a workflow but require manual steps to close the linked PO and SO simultaneously. When the close is not automated, the distributor carries open PO and SO records that inflate AP and AR until manually reconciled at period end.

01

Sales order created

A customer orders 50 units of Item X. The ERP flags the item as drop-ship eligible and creates a linked purchase order to the supplier.

The ship-to address is the customer's location, not the distributor's warehouse.

02

The inventory never moves

Unlike a standard order, a drop ship never creates an inventory receipt.

The item goes from supplier to customer without appearing in the distributor's on-hand quantity.

03

Financial posting at shipment confirmation

When the supplier confirms shipment, the ERP posts simultaneously: debit COGS, credit accounts payable (the cost of the goods, as if received and shipped), debit accounts receivable, and credit revenue (the sale to the customer).

The inventory account is never touched.

04

PO receipt closure

The supplier's PO closes at shipment confirmation without a warehouse receipt.

The ERP must support a “drop ship receipt” transaction type that closes the PO financially without creating an inventory movement.

Consignment

Consignment Inventory Accounting in ERP: Who Owns It, Where Is It, and What Does It Cost?

Consignment inventory takes two forms: inventory held on behalf of a supplier (supplier-owned, unpaid until sold) and inventory placed at a customer site (distributor-owned, unbilled until consumed). The ERP accounting treatment differs for each.

Form 1: Supplier consignment
The supplier places inventory at the distributor's facility. The distributor does not own it and does not pay for it until selling it. The ERP tracks it for location and quantity but does not capitalize it to the distributor's inventory account; it stays off-balance-sheet, with a consignment liability account or memo record tracking the supplier's interest.

When sold: debit accounts receivable, credit revenue, and simultaneously debit COGS, credit consignment payable. The payable is settled when remittance is made to the supplier.
Form 2: Distributor consignment at customer site (VMI)
The distributor places inventory at the customer's facility, such as a toolroom crib or bin station, and owns it until the customer consumes it. It stays on the distributor's balance sheet, in a “customer consignment” sub-location, tracked separately from warehouse stock.

When consumed: when the customer reports consumption (scan, portal, EDI, or periodic count), the ERP triggers debit accounts receivable, credit revenue, debit COGS, and credit inventory. Inventory is relieved at the moment consumption is reported, not at physical delivery.

Most ERP systems handle consignment in a warehouse but have limited native support for consignment at external customer locations.

Warehouse Bins → Customer Bins

The ERP must maintain off-site inventory records by customer location and bin, accept consumption reports from multiple channels (EDI 852, portal scan data, and manual count upload), and trigger billing and inventory relief automatically on consumption confirmation.

High-SKU Valuation

High-SKU Inventory Valuation: How Distribution ERP Handles 80,000+ Active Items

High SKU valuation is a volume problem before it is an accounting problem. An industrial distributor carrying 80,000 to 200,000+ active SKUs cannot manage inventory valuation manually. The ERP must automate velocity classification, slow-mover identification, and write-down calculation continuously, not as an annual review.

01

ABC Velocity Classification

It classifies every SKU by movement frequency (A weekly or more, B monthly, C quarterly or less), driving cycle count frequency, minimum stock levels, and write-down priority.

02

Slow-Mover Identification

It flags SKUs with zero movement in 90, 180, or 365 days, configurable by category, generated automatically at period close rather than run manually.

03

Write-Down Calculation

It compares carrying value to net realizable value (last sale price or current market price, whichever is lower). The difference is the write-down, applying GAAP lower-of-cost-or-NRV.

04

Supplier Cost Update Automation

When a price list is uploaded, the ERP must update costs for affected SKUs across all locations, not require manual line-by-line updates across 80,000 items.

At this scale, machine learning models trained on ERP order history can produce SKU-level reorder recommendations for 80,000+ items simultaneously, adjusting for seasonality, customer-specific ordering patterns, and lead time variability, and updating automatically as consumption patterns shift.

What We Build

What GrayCyan Builds for Industrial Distribution ERP Inventory

GrayCyan builds ERP inventory augmentation for industrial distributors, connected to the ERP already running in the operation.

Every system is fully owned by the distributor at completion, with no recurring license fees.

What GrayCyan builds:

  • Landed cost allocation engine: Freight, duty, and handling allocated by configurable method (weight, value, quantity, or volume) at receipt, not as a month-end journal entry.
  • Drop ship transaction automation: Linked PO and SO closed simultaneously at supplier shipment confirmation.
  • Consignment inventory at customer sites: Off-site records by location and bin, consumption processing from EDI, portal, or scan data, with automatic billing and inventory relief.
  • AI demand forecasting: An ML model on order history generating reorder recommendations for every active SKU, updating automatically as consumption patterns change.
  • Slow-mover write-down automation: Identification of SKUs crossing slow-mover thresholds, NRV calculation, and write-down entry at period close.
ERPs GrayCyan has built distribution inventory augmentation on
NetSuiteLanded cost, drop ship, consignment locations
SAP Business OneLanded costs module, goods receipt PO
SAP S/4HANAPurchase order conditions, valuation areas
EpicorLanded cost, drop shipment, ABC analysis
AcumaticaLanded cost, drop-ship orders, inventory valuation
FishbowlInventory transactions, purchase orders, scanning
OdooLanded costs, dropship route, replenishment
Microsoft Dynamics 365Charges, direct delivery, ABC classification

GrayCyan's AI middleware reduced engineering proposal generation from 8 hours to 30 minutes, a 90% reduction, by connecting product data in the ERP to a natural language query interface for the sales team. See RAG AI for manufacturing for how that layer is built.

Frequently Asked Questions: ERP Inventory for Industrial Distribution

What is the landed cost calculation in distribution ERP?−
Landed cost calculation allocates inbound freight, customs duties, insurance, port fees, and handling costs to the unit cost of each item received: Landed Unit Cost = (Purchase Price + Freight Allocation + Duty Allocation + Other Costs) / Units Received. Without it, gross margin calculations use only the purchase price, understating the true cost of imported inventory.
What is drop ship accounting in a distribution ERP?+
Drop ship accounting posts the financial transaction for orders fulfilled directly from supplier to customer, without the item entering the distributor's inventory. The ERP posts debit COGS and credit accounts payable, and debit accounts receivable and credit revenue, simultaneously at shipment confirmation, closing the linked PO and SO together without a warehouse receipt.
What is consignment inventory accounting?+
It covers two scenarios. Supplier consignment: inventory owned by the supplier, held by the distributor, not capitalized until sold; when sold, debit COGS, credit consignment payable. Distributor consignment at a customer site: inventory owned by the distributor, billed on consumption; when consumed, debit accounts receivable, credit revenue, debit COGS, and credit inventory.
How does ERP handle high-SKU inventory valuation for distributors?+
High-SKU distribution ERP automates ABC velocity classification, slow-mover identification (zero movement in 90, 180 or 365 days by category), lower-of-cost-or-NRV write-down calculation, and supplier price list mass updates across all active SKUs. Without automation, a distributor carrying 80,000+ SKUs cannot maintain accurate valuation through manual reviews.
What is the difference between distribution ERP and manufacturing ERP?+
Manufacturing ERP manages production: BOM, work orders, shop floor scheduling, and WIP. Distribution ERP manages the purchase-to-sale cycle: supplier pricing, landed cost, high-SKU inventory, drop ship, consignment, and customer pricing. Many distributors also handle light assembly, adding some manufacturing ERP needs. Mid-market ERPs like NetSuite, Epicor, and Acumatica handle both but require different configuration.
How does AI improve demand forecasting for high-SKU industrial distributors?+
ML demand forecasting on ERP order history produces reorder recommendations for every active SKU, adjusting for seasonality, customer-specific patterns, and lead time variability, and updating automatically as consumption shifts. For distributors with 80,000+ SKUs, this is the only practical way to maintain accurate reorder points across the full catalog.
Let's
Talk

Landed Cost, Drop Ship, or Consignment Not Posting Correctly in Your ERP?

Tell us which ERP you run, which of the four challenges (landed cost, drop ship, consignment, high-SKU valuation) is causing the most reconciliation burden, and how many active SKUs you carry.

GrayCyan will show you what distribution-specific ERP inventory augmentation looks like on your existing infrastructure.

See ERP inventory management or start with an AI Readiness Assessment →