Distributor Order Management: The Order-to-Cash Flow From Field Visit to SAP Invoice

Quick answer: A distributor order management system captures primary orders (distributor to company) and secondary orders (retailer to distributor) in one place. It prices orders, applies schemes, checks credit, routes approvals and tracks dispatch, delivery, invoicing and collection. Each order is keyed in once and flows on to the ERP, stock ledger and receivables.

Key takeaways

• Most order errors come from re-keying: WhatsApp to Excel, Excel to ERP, ERP back to the distributor.

• Prices, units of measure, schemes and credit limits should be enforced when the order is taken, not corrected after.

• A clear order lifecycle with fixed states removes "where is my order?" calls.

• Partial dispatch with batch selection and ERP-driven delivery keeps stock and receivables accurate.

What is the difference between primary and secondary orders?

• Primary order: placed by the distributor on the company. It is billed by the company, usually through the ERP (for example SAP Business One).

• Secondary order: placed by a retailer or channel partner on the distributor, often captured by a sales representative at the outlet. It is fulfilled from the distributor's stock.

Both need the same discipline, but they are approved and fulfilled by different people. For a fuller explanation, read primary vs secondary sales explained.

Where orders come from

A distributor order management system should accept orders from every channel your business actually uses, and treat them all the same way afterwards:

• the dealer portal on the web, with cart-based ordering;

• the Distributor App on Android and iOS;

• the field Sales App, where reps capture retailer demand during a visit;

• automatic replenishment orders raised from stock phasing (see DRR min–max replenishment);

• orders created by company users on behalf of a distributor.

What are the stages of a distributor order?

Every order in SalesPort moves through a fixed set of states:

1. Draft: being built, not yet sent.

2. Initiated: submitted by the distributor or rep.

3. Forwarded: sent on for approval.

4. Approved: accepted by the company (for primary) or the distributor (for secondary).

5. Partially delivered: some lines or quantities dispatched.

6. Delivered: fully dispatched.

7. Closed: complete.

An order can also be cancelled. Different users can make different moves. A distributor can cancel only until the order is forwarded, for example. Every status change is kept in the order's history and audit trail, so anyone can see who moved it and when.

Which checks should run when an order is taken?

1. The right price, every time

Rates are resolved on the server in a fixed order: the party's special price, then the party's price group, then the parent distributor's price group, then the product MRP. Price lists are uploaded from Excel with effective dates, and SAP per-carton rates are converted to per-unit rates automatically. No rep or distributor types a price by hand.

2. The right unit of measure

Products carry three packaging levels (for example piece, inner and carton) with conversions. Ordering rules per position set which levels are allowed, minimum order quantities and whether loose units are accepted, so a distributor cannot place a primary order in loose pieces when the plant ships cartons.

3. Schemes applied automatically

Every active scheme is evaluated when the order is created, edited or changes status: free goods, discounts, slabs, combos and value schemes, within their caps and budgets. In the Sales App the rep sees a live preview in the cart, with prompts like "add 2 more cartons to unlock" the next slab. See our scheme management guide.

4. Credit limit checked against the ERP

Primary orders are checked against the distributor's credit limit and the outstanding balance synced from SAP. The outstanding balance updates as soon as the order is created, so two large orders placed in an afternoon can't both slip through.

5. Proof of visit for retailer orders

Retailer orders in the Sales App can only be placed during an open check-in at that outlet, inside a geofence. There are no phone orders, so every secondary order is also proof that the rep was there.

See it on your own price lists: book a 30-minute walkthrough and we'll run a sample of your orders through pricing, schemes and credit checks live.

Approval and dispatch

For primary orders, the company approves orders individually or in bulk, previews the stock-phasing split, and syncs the order to SAP, with a sync history and error details if anything fails. One SAP order is created per production unit.

For secondary orders, the distributor approves, rejects or dispatches from the Channel Orders tab on the web or the Distributor App:

• Partial dispatch with batch selection, so near-expiry batches go first.

• Bulk dispatch of many channel orders at once.

• Delivery challan PDF for every dispatched channel order.

• Stock moves automatically from the distributor to the channel partner on delivery, first in, first out, including fractional cartons.

Ready Stock: van sales in one step

For reps who carry stock on a van, a Ready Stock order creates and delivers the order in a single step from the dealer's van stock, choosing earliest-expiry batches first. If there isn't enough stock, the rep is told immediately, before the retailer is promised anything.

From SAP back to the distributor

Order management doesn't end at approval. With SAP Business One integration, documents flow back automatically:

• Delivery orders from SAP move the order to delivered or partially delivered and create the distributor's stock-in automatically.

• A/R invoices from SAP are recorded against the order, create the distributor's bill and can be downloaded.

• Free-goods deliveries earned under customer agreements are stocked in at the distributor.

Where there are no ERP delivery documents, distributors receive stock themselves with a GRN: invoice number, dates and batch rows with quantities and expiry dates. If you're deciding how SAP and a DMS should split the work, read SAP B1 vs DMS: layer or replace.

Collection closes the loop

A rep can record a cash collection against an order in the app, which also applies any cash-discount scheme that was waiting on payment. Distributors report payments with proof against open bills, and only payments verified by the company reduce the outstanding balance. The order-to-cash cycle ends with a verified payment, not a promise.

Distributor order management reports to review every week

• Sales Order Summary: orders, value, average order value, processing time and cancellation rate.

• Order Fulfilment & Dispatch: approved vs delivered, shortfall and dispatch turnaround time.

• Fill Rate (distributor-wise): ordered vs delivered vs pending, as a percentage.

• Outlet Sales Orders: orders captured in the field, with visit context.

Implementation checklist

1. Clean up price groups and special prices, then upload them from Excel with effective dates.

2. Set packaging levels and ordering rules per position.

3. Agree who approves which orders, and set the approval workflow.

4. Connect the ERP for order push, delivery orders and invoices, and test with a handful of distributors.

5. Move one region off WhatsApp ordering first, then roll out region by region. Our WhatsApp-to-DMS playbook covers the 60-day switch.

Run every order through one system

SalesPort handles primary and secondary orders, pricing, schemes, credit, dispatch and SAP sync in one distributor management system, with apps for field reps and distributors. Schedule a walkthrough to see an order go from outlet visit to SAP invoice.