Decide what each sales record represents
For an FMCG distributor, a number labelled 'sales' can mean several different things: a buyer's request, a confirmed order, dispatched goods or an accepted delivery. If representatives and office staff use different definitions, a dashboard can appear precise while combining incompatible records. Agree on the meaning of each stage before using the figures to discuss performance.
Write the definition in everyday language and show the team an example. A request for ten cartons should not become ten delivered cartons because someone copied the value into a summary. Keep the activity linked to the outlet and relevant product, then record changes through an agreed process. Clear definitions make later reconciliation easier than trying to infer what the original rep intended.
Standardise product names and units
Product data needs enough detail for another person to fulfil the request without a phone call. Include the product variant, pack size and selling unit. 'One carton' is only useful when everyone knows what that carton contains. Different products can have different carton quantities, and a loose piece should not inherit a carton price because the names look similar.
Assign a stable identifier to each saleable item or unit configuration. Keep discontinued lines distinguishable from current ones, and communicate substitutions explicitly. For a distributor supplying shops in Enugu, a buyer may use a local nickname for a product. Record that as a helpful search aid if your process allows, but preserve the unambiguous product identity used by the warehouse.
Capture a minimum set of useful fields
The best record is the smallest one that supports fulfilment, review and follow-up. Capture fields at the point where the information is known. A rep knows what the buyer requested; the dispatch team knows what left the warehouse. Avoid asking one person to guess the other person's stage simply to complete every box before the end of the day.
- Customer identity and branch, activity date and responsible representative.
- Product identifier, variant, pack size, selling unit and quantity.
- Applicable unit price, currency and clearly defined total value.
- Order status, relevant reference and any approved adjustment.
- Exception, next action, owner and the customer communication required.
Reconcile quantities with an illustrative example
Imagine a buyer requests six cartons of one product and twelve individual pieces of another. This is an illustrative example, not an actual customer record. The warehouse supplies five cartons and all twelve pieces. A useful process retains the original request, records what was supplied and identifies the one-carton gap. Replacing the requested quantity with five erases the reason the customer expected more.
Now suppose the buyer declines two damaged pieces at handover. The accepted quantity differs again. Your record should make that exception understandable without counting the same items twice. Decide which stage feeds each management measure. A confirmed-order report and a completed-delivery report can both be correct while showing different totals, provided their labels and cutoff times explain the difference.
Pair commercial totals with outlet coverage
Sales value shows one part of distribution performance. Outlet coverage helps explain whether the team is maintaining the customer base or relying on a small number of larger orders. Compare customers due for a visit with customers actually visited, then examine the outcomes. Separate a customer with no demand from one the team could not serve because a requested product was unavailable.
Be careful when combining units across unlike products. Twelve cartons of one item and twelve pieces of another are not a meaningful total of 24 identical units. Review quantities by compatible unit or product, and use clearly defined monetary values where aggregation is appropriate. Keep returns, corrections and cancellations visible so a manager can explain how the summary was produced.
Make review a shared operational habit
Set a routine for checking missing product references, ambiguous units and unresolved supply gaps. The purpose is to correct the next action while the details are still recoverable. A weekly conversation between sales and dispatch can identify repeated mismatches, but urgent customer exceptions need an owner sooner. Record the resolution once in the relevant business record and make the status understandable to both teams.
Trurep supports capturing sales values or applicable catalog products and quantities, together with customer visit records. Use those capabilities within a clear operating process and verify the available features for your plan. Software can preserve structured inputs; your team still needs to define what counts as an order, a delivery and an adjustment before comparing results across people or territories.
