Distribution ERP Consultant, Qatar

Short distances, frequent calls: choosing the sales model

In larger countries a van may leave for a full day on a long route. In Qatar the picture is different. Outlets cluster around Doha and the surrounding towns, drive times between calls are short, and small groceries often prefer frequent small deliveries because their storage space is limited. That favors a high call frequency, and it raises a real design question: should the salesman carry the stock, or should he take the order and let a delivery van follow?

Both models exist in Qatari distribution, sometimes inside the same company. Van selling suits impulse lines and outlets that pay cash. Pre-sell suits larger stores, wider ranges and customers on credit, because the warehouse can pick accurately and the delivery driver only hands over goods and documents. Each model needs different rules in the ERP:

• van selling treats the vehicle as a stock location that is loaded, sold from and settled every evening
• pre-sell creates sales orders on the handheld that the warehouse picks overnight or the same day
• mixed routes need clear rules on which outlets get which treatment

I map your current routes, then agree with sales and finance which model each channel should follow. That decision shapes the handheld app, the picking process and the settlement design, so it comes before any vendor demo. The general route-to-cash cycle is described on my distribution ERP page.

Hotels, caterers and the food service channel

Food service is often a significant channel for Qatari distributors of food and beverage brands. Hotels, restaurants, contract caterers and institutional kitchens behave nothing like a grocery on a van route. They buy against an agreed price list for a period, specify pack sizes and sometimes particular brands, expect deliveries within a receiving window and frequently ask for supporting documents such as batch details or product specifications.

When a distributor runs food service through the same price logic as retail outlets, two problems follow. Contract prices get overridden by hand, and nobody can tell whether a large account is profitable once delivery cost and credit terms are considered.

My requirements for this channel cover contract price lists with validity periods, agreed substitutions when a line is out of stock, delivery slot booking, batch and expiry printed on the delivery note, and separate credit terms from the trade channel. I also look at how purchase orders arrive from larger hotel groups, since some send them by email in a fixed layout and others through a supplier portal, and decide whether those orders should be keyed in, imported or connected through ERP integration.

Chilled and frozen ranges add cold chain discipline: picking by earliest expiry, recording why stock was written off and keeping short-dated stock visible early enough to clear it.

Principal systems, uploads and secondary sales

International principals rarely leave reporting to the distributor's discretion. Some provide their own distributor management system and expect primary and secondary sales to flow into it. Others send a spreadsheet template or an upload specification and ask for it on a fixed cycle. A distributor carrying several brands may be feeding three or four different formats, each with its own outlet classification and item codes.

That work is usually where hidden effort sits. I document every principal's requirement in a single register and turn it into design decisions:

• outlet records carrying the attributes principals ask for, such as channel, outlet type and area
• a mapping table between your item codes and each principal's SKU codes
• a plan for wholesalers and smaller dealers who buy from you and resell, where principals want visibility of that onward sale
• a list of scheme claims you make back to principals, with the evidence each one requires

Once those are in the ERP design, the reports become a by-product of daily transactions rather than a monthly rebuild. If you also import directly and hold agency rights, my trading ERP page for Qatar covers shipment costing and agency structure, which I deliberately leave out here.

No VAT on the invoice, but tax codes in the design

Qatar, as I understand it, is not charging a general VAT at present, which makes a van invoice there simpler than one printed across the Saudi border. Have your tax advisor confirm where things stand before the design is signed off, because this is precisely the sort of fact that can shift.

Even so, I give each invoice and bill line a tax field, currently set to a nil rate. Doing that at setup is cheap. If rules change, or if you sell to customers in other GCC countries, the ledger and the handheld can adapt without reworking every price list and document template. I ask each vendor how quickly their handheld app could add tax lines if that were ever needed.

Documents still need care. Delivery notes, invoices and customer statements in Qatar usually carry Arabic alongside English, and item names on a small handheld printout must remain readable in both scripts. Credit control matters as well: trade customers may pay in cash, on short credit or with post-dated checks, and the handheld should block a sale to an outlet that finance has put on hold.

The migration work I see most often is from a desktop accounting package plus a separate field app that exports a file each evening. Outlet masters, open balances, checks in hand and stock by vehicle are the items that have to be correct when the new system opens.

Evaluating platforms and working together remotely

The choice between platforms in distribution rarely turns on accounting features. It turns on how the field app and the ERP behave together on an ordinary day. I script that day from your own business: a pre-sell order picked overnight, a van sale to a cash outlet with a damaged goods return, a hotel order against a contract price list, a delivery with batch details printed, and a principal upload produced from the results. Each shortlisted vendor runs it on screen with your team scoring.

That exercise usually separates the options quickly. Some ERPs come with a mobile sales app that is adequate for pre-sell but weaker for full van settlement. Others rely on a specialist app connected through an API. Neither route is wrong; it depends on which channels carry the most weight for you. My vendor selection work documents the result so the decision can be explained to owners and principals alike, and the product pages for Zoho Inventory in Qatar and Odoo Inventory in Qatar go deeper on each.

I deliver the engagement remotely, using online workshops held within the Qatari working week and recorded walkthroughs of handhelds and settlement desks. Seeing the loading bay in person can be arranged if that adds something. How engagements are structured is set out on my Qatar ERP consulting page, with market notes in the Qatar hub.