Cosmetics & Personal Care Distributor Management Cloud Software for Saudi Arabia

Every carton keeps its tier history. Primary movement (distributor to sub-distributor) and secondary movement (wholesaler to baqala, mini-market, or beauty retailer) sit on separate ledgers. Each tier holds its own SAR price list, credit window, and scheme, so loading a wholesaler ahead of a promotion shows up early rather than at month-end. The same tracking applies whether the destination outlet sits in Riyadh, Jeddah, or a smaller town further along the route.

Every carton of cream, lotion, haircare product, fragrance, or soap picks up its batch, manufacture date, and expiry the moment it is received, aligned to SFDA/RSD and GS1 batch and expiry standards. FEFO dispatch pushes the nearest-expiry lot out first, and near-expiry alerts fire weeks ahead so brand teams can move stock to fast-selling outlets before it goes short-dated. Lot searches run instantly if a recall or complaint arises.

Each SKU carries its shade or variant code, batch, pack size, and SAR price, with fields structured to SFDA/RSD and GS1 batch and expiry tracking. Dispatch rules can flag any beauty or personal-care SKU missing a required tracking field, so short-dated or incomplete lines do not leave the warehouse unnoticed. Audit reports show batch and expiry status across the active catalogue at depots in Riyadh, Jeddah, and Dammam.

SAR price trees are built per channel: lead distributor, sub-distributor, baqala, mini-market, salon and spa, beauty retail, and modern trade such as Panda or Othaim. Trade discounts (off-invoice, on-invoice, and post-invoice) attach to each channel. The order screen applies the correct combination on every line with no manual edits.

Schemes sit on top of the base SAR pricing as slab-based bonuses, buy-X-get-Y offers, or free-goods deals. Ramadan and Hajj-Umrah season pushes, and new-shade launches, run only inside their date windows, timed to the sharp, predictable demand spikes those seasons bring. Eligibility is checked at the point of order and scheme ROI updates live against the month-to-date target.

mada card receipts, STC Pay wallet payments, SADAD structured bill payments, and direct bank transfers all post to the customer ledger with a reference. Auto-allocation matches each payment to open invoices oldest-first or by remittance note. Field reps confirm collection on the app even mid-route between stops, and the collection dashboard refreshes as sync completes.

Credit terms are set per account and applied as orders are booked. Ageing dashboards flag wholesalers and baqala operators approaching their ceiling, and bookings are blocked automatically once the limit is breached. Larger distributors may run longer windows while smaller baqala outlets settle on shorter cycles, and the DMS supports both.

Yes. The field app is offline-first, built for a country where a single route can cover long distances between stops and extreme summer heat affects delivery windows. Reps capture orders, stock counts, and collections at any outlet along the route with no signal, and everything syncs when connectivity returns. Outlets are mapped by GPS so route planning holds up across sprawling city grids and inter-city stretches alike.

A return captures reason code, batch number, original invoice, and a photo. Sources include near-expiry pulls, damaged or leaking creams, chain consumer returns, and de-listed shades. Once approved, a credit note is raised and linked to the original sale, and the batch ledger updates so short-dated beauty stock is not re-dispatched.

Yes. REST APIs link to SAP, Oracle, Microsoft Dynamics, Sage, and locally built distributor ERPs. Orders, invoices, GRN, returns, batches, and mada, STC Pay, or SADAD payment records move both ways. Modern-trade B2B portal feeds for chains such as Panda and Othaim ingest purchase orders and return dispatch advice, and SFTP handles nightly master sync.