ERP for Distributors: Multi-Warehouse Stock, Van Sales and Collections

An ERP for a distribution company has to solve problems that a normal accounting program ignores: stock spread across several warehouses and vans, sales reps who take orders and cash in the field, routes that cover hundreds of shops, credit limits, returns and daily settlement of each rep's collections. When these are managed in one system, a distributor in the Delta, Upper Egypt or Greater Cairo knows exactly what stock is where, what each rep sold and collected today, and which customers are overdue.

Many Egyptian distributors still run on paper order books, WhatsApp photos of invoices and an evening reconciliation in Excel. It works while the company is small. As routes, reps and SKUs grow, the gaps become expensive: stock that disappears between the warehouse and the van, cash collected but not deposited, and customers who keep buying on credit long after they should have been stopped.

This guide explains what an ERP for distributors must do, module by module, with the Egyptian details that matter, including e-invoicing, digital collections and offline mobile apps.

Key takeaways

• Treat every van as a warehouse. Loading, sales, returns and unloading must all be stock movements with a clear owner.
• Van sales need a mobile app that works offline, prints or shares invoices and syncs when the connection returns.
• Credit control, including limits, ageing and blocking overdue customers, must be enforced on the rep's device, not only in the office.
• Daily rep settlement compares what was loaded, sold, returned and collected. It is the single most effective control against leakage.
• Sales to businesses need ETA e-invoices. Plan how invoices issued in the field are signed and submitted.

Distribution models and what they need

Model	How it works	What the ERP must support
Pre-sales (order taking)	Rep visits, takes an order; delivery follows from the warehouse	Mobile orders, stock availability, delivery planning, invoice on delivery
Van sales	Rep sells and delivers from stock on the van	Van as a warehouse, invoicing in the field, collections, end-of-day settlement
Key accounts	Large retailers and chains with contracts	Special price lists, rebates, purchase-order matching, delivery windows
Wholesale counter	Customers buy at your warehouse	Fast counter invoicing, credit checks, cash and digital payments

Most Egyptian distributors combine at least two of these models. The ERP should handle them in one database so that stock and customer balances are always consistent.

Multi-warehouse stock

Structure

Define every place where stock can be: the main warehouse, branch warehouses (for example in Tanta, Mansoura or Assiut), each van, a returns area and a damaged-goods area. Each is a separate stock location with its own balance.

Transfers and loading

• Transfers between warehouses are documented, with "in transit" stock while goods are on the road.
• Van loading is a transfer from the warehouse to the van, confirmed by the rep on the device.
• Unloading at the end of the day returns unsold stock and records damaged or expired items separately.

Batches and expiry

For food, beverages, cosmetics and pharmaceuticals, track batch numbers and expiry dates. The system should suggest first-expiry-first-out loading and warn reps before expired goods reach a shop.

Van sales and the rep's mobile app

What the app must do

• Show the day's route, customers and visit history.
• Show van stock, customer-specific price lists, promotions and credit balance.
• Create orders, invoices, returns and collection receipts.
• Capture the customer's signature or a photo of proof of delivery, and GPS location of the visit.
• Print on a mobile printer or share the invoice as a PDF on WhatsApp.
• Work fully offline and sync without creating duplicates.

Build for Android first

In Egypt, Android accounts for about 88% of mobile operating system usage, according to StatCounter (August 2026). Rep devices are typically mid-range Android phones or rugged tablets, so the app must be light, fast and reliable on them.

Offline is not optional

Coverage on rural routes and inside large markets is not always reliable. An app that stops working without data will push reps back to paper. Offline mode, with numbered documents reserved per device to avoid duplicates, is a requirement, not a feature.

Collections and credit control

Credit limits and ageing

Every customer should have a credit limit and payment terms. The system blocks new credit sales when the limit is exceeded or invoices are overdue beyond an agreed number of days, and shows the rep the reason. Exceptions should need a manager's approval, recorded in the system.

Cash, cheques and digital payments

Distributors still collect a lot of cash and post-dated cheques, but digital payments are growing fast. The Central Bank of Egypt reported that InstaPay had more than 16 million users and mobile wallets numbered 55.5 million as of June 2025 (Daily News Egypt, November 2025). Your ERP should record each payment method separately, track cheques until they clear, and match transfers to invoices.

Daily rep settlement

At the end of each day, the system should produce a settlement for each rep:

Item	Source
Opening van stock + loaded quantities	Loading transfers
Sold quantities and values	Invoices issued on the app
Returns from customers	Return documents
Closing van stock	Unloading count
Cash, cheques and transfers collected	Collection receipts
Differences to explain	Calculated by the system

Differences found the same day are easy to explain. Differences found at month-end are usually lost.

Pricing, promotions and returns

• Price lists by customer type (supermarket, grocery, pharmacy, wholesaler) and by region.
• Promotions such as "buy 10 cartons, get 1 free" or tiered discounts, calculated automatically on the device.
• Returns with reasons (expired, damaged, wrong item), linked to the original invoice and to supplier claims where applicable.
• Principal reporting: if you distribute for manufacturers, sell-out reports by product, region and customer type.

E-invoicing for distributors

Sales to businesses must be issued as ETA e-invoices, signed and submitted with registered item codes, as described in the ETA's official e-invoicing SDK. For distributors, the practical challenge is invoices created in the field. A common design is for the app to create the invoice and share it with the customer, while the ERP server signs and submits it to the ETA once the device syncs. Your customer master must hold each shop's correct tax registration details, and your item codes must be registered before the product is sold.

KPIs every distribution manager should track

• Visits completed vs planned, and strike rate (visits that produced an order).
• Sales per route and per rep, by product line.
• Collection rate and overdue receivables by rep and region.
• Returns as a percentage of sales, by reason.
• Stock days and expiry risk by warehouse.
• Settlement differences per rep over time.

Rolling out the system to your reps

1. Clean customer and route data first. Merge duplicate shops, confirm addresses and tax details, and assign every customer to one route and one rep.
2. Pilot with two reps on two different routes, one urban and one rural, for two to four weeks. Fix what they struggle with before scaling.
3. Start settlement on day one. Even if other features come later, the daily settlement changes behaviour immediately.
4. Train reps on their phones, in Arabic, with real customers and real products. Short sessions work better than one long day.
5. Retire the paper books route by route, so nobody records in two places.
6. Review KPIs weekly with supervisors for the first three months, and adjust credit limits, promotions and routes based on what the data shows.

Reps accept a new system when it makes their day easier: fewer calls to the office about prices, no manual totals at night and faster approval of their settlement. Design for that, and adoption follows.

How Nilex helps

Nilex Digital Systems builds custom ERP systems for distributors, with multiple branches and warehouses, stock transfers between locations, customer balances, role-based permissions so each rep sees only their own customers, and a full audit log of every action. Because we build around your workflow, route structure, promotions and settlement rules follow the way your company already works. Multi-branch and multi-warehouse needs are covered in the Growth package, and the system is built on Node.js and PostgreSQL.

Frequently asked questions

What is van sales in ERP?

Van sales is a model where the rep sells and delivers directly from stock on the vehicle. In the ERP, each van is a stock location, and the rep's app issues invoices, returns and collection receipts that update stock and customer balances.

Can the sales rep app work without internet?

It should. A well-designed app stores data on the device, reserves document numbers to avoid duplicates and syncs automatically when coverage returns.

How are e-invoices issued for sales made in the field?

Typically the app creates the invoice, and the ERP server signs and submits it to the ETA when the device syncs. The customer's tax details and item codes must be correct in the system beforehand.

How does an ERP reduce stock and cash leakage?

By making every movement a recorded transaction with an owner, and by producing a daily settlement per rep that compares loaded, sold, returned and collected amounts. Differences are visible the same day.

Can the ERP produce reports for the manufacturers we distribute for?

Yes. With product, customer type and region recorded on every sale, sell-out and stock reports for each principal become standard reports rather than monthly manual work.

If you run a distribution company and want clear control over stock, reps and collections, book a free consultation. We will map your routes, settlement and credit process and show what a system built around them would look like. You may also find our article on signs you have outgrown Excel useful.