ERP inventory management: how stock works across warehouses, 3PLs and channels

An ERP prevents stockouts by keeping one stock record per SKU across every warehouse, 3PL and sales channel, then sending each channel an available-to-sell number from that record. ERP inventory management only works when SKUs, locations, bins and batches are mapped first.

Skip the mapping and the cost shows up fast. IHL Group estimates that inventory distortion, meaning out-of-stocks plus overstocks, reached $1.7 trillion globally in 2026, or 6.2% of retail sales. That figure covers global retail across all channels, including stores. This guide covers setup steps, bins and barcodes, 3PL sync, key features, and how Prim.io handles it.

How does ERP inventory management handle multiple locations?

ERP inventory management handles multiple locations by keeping one master record per SKU, with a separate stock count for each warehouse, store and 3PL. Every sales channel reads its number from that master record.

Your sales channels may not combine those counts for you. Shopify, for example, tracks inventory separately per location, and one location's stock can't be shared or pooled with another. A brand selling on Shopify, WooCommerce, Amazon and a wholesale portal ends up with four partial views of the same stock.

Multi warehouse inventory management fixes that by making the ERP the one place where every count lives. Inside that record, each location tracks more than one number. The table below shows the five stock states a good ERP inventory system keeps apart.

Multiple location inventory management works when channels only ever see the last row. A cloud ERP for ecommerce brands keeps these states per location, so nobody adds them up in a spreadsheet. OhGood, a Prim.io customer, manages three warehouses in one live view. For the wider picture of how channels share one stock view, see multichannel inventory management.

Why doesn't inventory sync happen automatically?

Inventory sync doesn't happen automatically because every channel and 3PL uses its own product codes, locations and update rules. Someone has to map those to the ERP before any number can flow.

Before you switch on a sync, set up four things in your ERP inventory system:

• Match each channel listing and 3PL item code to one ERP SKU.
• Assign each 3PL, store and warehouse to a named location.
• Decide which locations feed each channel's available-to-sell number.
• Set how often stock goes out to channels and when 3PL counts come back.

Even a mapped sync can fail quietly. Amazon's Selling Partner API docs note that its responses don't include issues that occur after a submission is accepted for processing. So an accepted stock update can still fail later, and your team needs a way to catch those errors.

Bad records make every sync worse. A 2020 ECR Retail Loss study of 7 European retailers found that about 60% of SKUs analyzed had inaccurate records. In those stores, correcting the records was associated with about 4% to 8% higher sales.

What role do warehouse bins and barcodes play in fulfillment?

Warehouse bins and barcodes tell your team where each unit sits and confirm the right unit leaves the building. Without them, the ERP knows how many units you have but not where they are.

Barcodes start with the product code. GS1 explains that a GTIN uniquely identifies a product, and many marketplaces such as Amazon require one. Store the GTIN on the ERP SKU, so scans, listings and 3PL records all point to the same item.

Prim.io manages inventory, orders, warehouse bins, barcodes, serial numbers, and expiry dates in one system. That puts every scan and every stock count in the same record.

How do ERP systems handle barcode scanning and warehouse bins?

ERP systems handle barcode scanning and warehouse bins by linking every scan to a SKU and a bin location. Each scan updates the stock record as the work happens.

• Label every bin with its own barcode, using a simple code for aisle, shelf and position.
• Scan supplier deliveries against the purchase order, so counts match before stock goes live.
• Scan the item and then the bin at put-away, so the ERP records where the units went.
• Pick by bin route, with the pick list sorted in bin order so pickers walk one path.
• Scan each item at packing to check it matches the order before the parcel ships.

How do 3PL integrations sync stock levels?

3PL integrations sync stock levels by sending orders from the ERP to the 3PL and pulling the 3PL's stock counts back. The ERP stays the master record, and the 3PL reports what happened on its floor.

What is the best way to sync stock between 3PLs and online stores?

The best way to sync stock between 3PLs and online stores is to route both through the ERP, so stores never read 3PL counts directly. The ERP combines 3PL stock with your own warehouses and sends one available-to-sell number to each store.

Two common ways to connect a 3PL are an API and a scheduled file. An API sends updates as events happen, such as a shipment or a receipt. A scheduled file, such as a CSV on a shared server, sends counts in batches at set times.

Either way, 3PL inventory sync needs regular checks:

• Match units the 3PL received against the purchase order or transfer you sent.
• Move units the 3PL marks as damaged into quarantined stock.
• Hold returns in quarantine until the 3PL confirms they can be resold.
• Compare the 3PL's cycle counts with the ERP and look into any gap.

Prim.io connects with webshops, marketplaces, and couriers through paid add-on connectors. Store, marketplace and courier connectors are priced per connector (€20 to €50 per month); finance connectors are free. A marketplace connector is €50 per month, a webshop connector €30, and a courier or 3PL connector €20. For example, a brand with one webshop, one marketplace and one 3PL would pay €100 per month in connectors.

How do you track batches, serial numbers and expiry dates?

Batches, serial numbers and expiry dates are tracked by recording them at receiving and carrying them through every move until the unit ships. The same bins and barcodes from the steps above carry these details.

First expired, first out (FEFO) picking sends the batch with the nearest expiry date to the next order. That keeps short-dated stock moving instead of aging on the shelf.

Expired batches should drop out of available to sell, so no channel sells stock you can't ship. Serial numbers help with returns. Look up the serial and you see the original order, date and customer.

How do you prevent stockouts using an ecommerce ERP?

An ecommerce ERP prevents stockouts when five habits run every day: SKU mapping, channel buffers, reservations, reorder alerts and reconciliation. The steps below show how to set each one up.

• Map every SKU once, so each channel listing and 3PL code points to a single ERP item.
• Set channel buffers. For example, with 60 units available to sell, show 55 on a marketplace and keep 5 back.
• Reserve stock on order, moving units from available to reserved as soon as an order is paid.
• Add reorder alerts per SKU and location, then adjust them as you learn supplier lead times.
• Reconcile daily by comparing ERP stock with 3PL reports and channel listings each morning.

Buffers protect you from slow channel updates. Reservations stop two channels from selling the same unit.

What features should you expect in an inventory ERP?

An inventory ERP should hold stock by location and state, connect to your channels and 3PLs, and track bins, batches and expiry dates. The table below lists the features to check and a question to ask each vendor.

Why do ecommerce brands need an inventory ERP?

Ecommerce brands need an inventory ERP once stock, orders and finance sit in separate tools that don't agree. An inventory ERP puts them in one record, so a sale updates stock and accounts together.

Spreadsheets break first. Each new channel or warehouse adds another file to reconcile at month-end.

How Prim.io handles inventory across warehouses and channels

Prim.io handles inventory across warehouses and channels by keeping every location, bin and batch in one stock record. Prim.io is a cloud ERP with built-in AI for ecommerce and multi-channel brands, running orders, stock, finance, CRM, production and BI in one system.

Bins, barcodes, serial numbers and expiry dates sit in that same record. Brands with more than one legal entity see stock across every company. Across its customers, Prim.io processes 3.1M+ orders per month.

The Prim.io AI assistant answers stock questions from the company's own sales, stock and finance data. The assistant also reads invoices, corrects addresses and matches payments. Prim.io MCP, a connection for Claude, ChatGPT and Cursor, uses per-user permissions and asks for approval before changes.

Open a free demo accountFree demo account, no credit card needed, cancel anytime.

Why ecommerce brands choose Prim.io

Ecommerce brands choose Prim.io to run inventory, channels and finance in one system that goes live in weeks. The points below cover the main reasons.

• 50+ native integrations connect webshops, marketplaces, couriers and accounting tools.
• BI powered by Qlik turns stock and sales data into dashboards and drill-down reports.
• Multi-company support shows stock and finance for every legal entity in one place.
• Go-live takes about 6 weeks on average, 5 to 8 weeks depending on complexity.
• Plans from €180 per month, billed annually, excluding VAT, listed on Prim.io plans and pricing.

FAQ about ERP inventory management

ERP inventory management questions from multi-channel brands usually come back to locations, sync and cost. The answers below cover the five most common.

How does multi warehouse inventory work?

Multi warehouse inventory works by keeping one stock record per SKU, with a separate count for each warehouse, store and 3PL. The ERP adds up available-to-sell stock from the locations you choose and sends that number to each channel. Transfers between warehouses show as in transit until the receiving site scans them in.

Are marketplace inventory syncs real time?

Marketplace inventory syncs are not always instant, even when your ERP sends updates quickly. Amazon's Selling Partner API docs say responses don't include issues that occur after a submission is accepted. Check for errors after each update, keep a small channel buffer, and confirm sync timing with your vendor for each marketplace.

How do you track batches and serial numbers?

Batches and serial numbers are tracked by scanning them in at receiving and recording them on every move after that. The ERP then knows which batch sits in which bin, which batch expires first, and which serial went to which customer. That record supports FEFO picking, recalls and faster return checks.

Can an ERP replace a 3PL's warehouse system?

An ERP usually doesn't replace a 3PL's warehouse system, because the 3PL runs its own floor with its own tools. The ERP stays your master stock record across all locations. The ERP sends orders to the 3PL, pulls counts back, and checks receipts, damages and returns against your own data.

How much does Prim.io cost?

Prim Plus is €180, Prim Pro €540 and Prim Enterprise €1,710 per month, billed annually, excluding VAT, with 3, 5 and 15 users included. Store, marketplace and courier connectors are priced per connector (€20 to €50 per month); finance connectors are free. Full details are on Prim.io plans and pricing.

Conclusion: your ERP inventory management checklist

ERP inventory management prevents stockouts when every location and channel feeds one stock record. Use this checklist to get your setup ready.

• Map current warehouse bin locations and barcode scanning workflows.
• Integrate sales channels and 3PL partners using reliable cloud ERP connectors.
• Track batch numbers and expiry dates for perishable or serialized stock.
• Monitor multi-company stock levels from a single dashboard.

Open a free demo account

Free demo account, no credit card needed, cancel anytime.