VegaDelivery charge allocation asks a small but important question: which agreed charge belongs to which customer order or trip? A fictional shop sells goods worth KSh 8,000 with an agreed KSh 500 delivery charge. The order later leaves in two loads. Printing two dispatch notes should not automatically turn the customer’s KSh 500 agreement into KSh 1,000.
Use fictional order D73 and confirm the business’s pricing, approval and settlement rules. The examples are operational arithmetic, not tax or accounting advice. Keep the charge agreed with the customer separate from the actual cost paid to a transport provider. One may change without changing the other, and staff need clear authority before telling the customer that another amount is payable.
Delivery charge allocation in four decisions
Use the four decisions below as a tabletop exercise. The case is fictional. Each decision pairs a new scenario with field notes drawn from a linked guide in our library. Read the scenario aloud first, and ask the next person to explain the result before consulting the notes.
1. Record the basis of the charge
Write whether the agreed KSh 500 covers the whole order, one trip or a defined delivery area and service. Attach that basis to D73 so the dispatcher does not have to reconstruct it from a conversation. The sample amount due is KSh 8,500 before any other approved adjustments.
A separate transport invoice to the business is not evidence that the customer agreed to the same amount. Delivery charge allocation should start with the actual promise and the person allowed to amend it, rather than a convenient default copied from the last transaction. For delivery charge allocation, keep this starting assumption visible beside the result.
Field notes from our retail quotation review guide:
Match every line to a clear product identity
Use the correct product reference and a description the buyer can recognise. Similar names do not necessarily mean interchangeable goods. Confirm the variant, packaging and relevant specification against the catalogue. Avoid copying an old quotation merely because its description looks close enough. The previous customer may have purchased a different model or pack configuration.
Separate quotation approval from payment confirmation
A customer’s approval of the offer and confirmation of payment are different events. Record each through the appropriate process. An email accepting a quotation does not prove that money has arrived, and a payment reference needs verification against the business’s payment records. Staff should follow the agreed controls before releasing goods or recording settlement.
Learn from quotation changes and lost enquiries
Review a small sample of completed, amended and declined offers. Look for recurring uncertainty about units, product descriptions, availability or delivery. These patterns can reveal which part of the process needs clearer instructions. Avoid interpreting every declined quotation as a pricing problem when the customer may have needed a different product or timetable.
Choose one improvement and test it. You might revise a description, add an approval checkpoint or make delivery conditions more visible. Retail quotation review should improve the quality of the offer and the handover, not simply create a longer checklist. Check whether the change helps employees answer the next customer’s question more clearly.
2. Split the delivery without duplicating the fee
Create D73-A and D73-B for the two loads. If the agreed KSh 500 is an order-level fee, show where it is collected or allocated once. A second dispatch document may refer to the fee without adding another charge.
Test the final customer statement as well as each individual receipt; two plausible receipts can still overstate the combined balance. If splitting was requested by the customer and changes the agreed service, obtain the appropriate amendment before collection. Keep the original agreement and revised approval traceable so support can explain the difference later. This stage of delivery charge allocation tests a different question from the final total.
Field notes from our partial delivery tracking guide:
Use consistent units in partial delivery tracking
Choose a clear quantity basis for comparisons. If the order uses cartons and the shelf record uses individual units, confirm the relationship and record it consistently. Packaging changes may alter the relationship, so do not assume that every carton contains the same quantity across suppliers or dates.
Resolve unclear product references before posting a receipt. The supplier catalogue cleanup guide helps with unit descriptions and supplier mappings. Partial delivery tracking works best when everyone can explain how the counted goods become the quantity shown against the order.
Check documents separately from physical completion
A fully delivered order may still have an invoice question, return or missing supporting document. Conversely, a document may arrive before all goods do. Keep the physical receiving position and the related document follow-up distinguishable, with appropriate owners for each.
Close the order with a final review
Before closing, confirm that each line has a supported final position. All goods may have arrived, an outstanding quantity may have been cancelled, or another authorised outcome may apply. Check the evidence rather than relying only on the order age or the supplier’s statement that delivery is complete.
Keep the completed history available for later questions. Partial delivery tracking should end with a record that explains the whole journey. Review repeated split deliveries separately to understand whether order sizes, supplier communication or receiving instructions need improvement.
3. Distinguish payment from fulfilment
Suppose the customer pays the full KSh 8,500 before dispatch. The payment record should show one confirmed receipt and its agreed application. It does not prove that either load arrived.
Conversely, a signed delivery acknowledgement does not prove the fee was paid. Delivery charge allocation should let a cashier and dispatcher answer different questions without changing each other’s evidence. Use a sample payment reference and check that a second employee cannot collect the same fee again because the second load has a new dispatch number. Use delivery charge allocation to expose this exception before relying on the ordinary successful path.
Field notes from our cash float handover guide:
Define cash float handover responsibilities clearly
An opening float gives the cashier change for ordinary transactions. It is not the same thing as sales revenue for the shift. Record the agreed starting amount separately so the closing review can explain which money was present before trading began. The correct amount and denomination mix depend on the business and should follow its own approved procedures.
Record the expected and observed amounts
Keep the expected float and the counted amount distinguishable. A form that permits only one number can hide whether the employee entered the authorised amount or the amount actually found. If your system uses a different supported method, ask how it preserves the same distinction and how the reviewer sees an exception.
Make acceptance of responsibility clear
Agree how the outgoing and incoming employees acknowledge the handover. The record should indicate what was counted, which exceptions remain open and who accepted the next shift’s starting position. Do not use a generic acknowledgement that could be interpreted as agreeing to an amount the employee never checked.
Test the closing calculation separately
Opening the shift correctly is only one part of the routine. Ask the team to demonstrate how the closing review uses the starting float, recorded cash activity and authorised movements. Use a fictional example whose expected result can be checked independently. Avoid assuming that a familiar total means every underlying entry is correct.
4. Explain changes and cancellations clearly
The customer cancels the second load before it leaves. Apply the business’s agreed cancellation terms and approval route rather than assuming the whole delivery fee must disappear or remain unchanged. Record the authorised outcome, any customer balance adjustment and the actual refund or extra payment separately.
If the transport provider already charged the business, that cost still needs its own review. Delivery charge allocation is complete when the customer’s agreed charge can be explained from the order and amendments, with no extra fee created merely by another print, trip or status update. The final delivery charge allocation record should explain the outcome to someone who was not present.
Field notes from our customer backorder tracking guide:
Connect the request to a supply action
Identify whether the item is being purchased, transferred from another outlet or sourced through another approved route. Record the relevant reference when available. One supplier order may support several customer requests, so avoid assuming that the arrival of any quantity satisfies every waiting customer.
Confirm changes with the customer
If the product, quantity or expected timing changes, explain the difference and record the customer’s response through the approved channel. Do not assume that a similar item is acceptable because its price is close. A replacement colour, size or pack may matter to the customer even if staff consider it minor.
Keep price decisions separate and authorised. The price change approval guide supports that control. Customer backorder tracking should preserve the original request, the proposed change and the accepted outcome so another employee can explain the agreement later.
Verify readiness before sending a collection message
Check that the goods have arrived, passed the normal receiving checks and been assigned to the request where required. Confirm the collection location and any remaining action. A message should not say ready for pickup merely because a supplier changed the delivery status.
Connect customer backorder tracking with the customer order pickup guide. The handover to collection should identify the actual goods and the agreed quantity. A clear readiness check prevents an avoidable journey for a customer who was told to collect something still unavailable.
Delivery charge allocation test sheet
Before running the example, cover the expected results and ask a colleague to predict them. Use the disagreements to decide which rule needs explaining. These are fictional test cases; use your own approved references for the real procedure.
| Test condition | Expected evidence |
|---|---|
| KSh 8,000 goods plus KSh 500 fee | The sample agreed total is KSh 8,500 before other approved adjustments. |
| Order split into two loads | The order-level fee is not charged twice merely because two dispatch references exist. |
| Full payment received before dispatch | Payment is confirmed separately from either delivery outcome. |
| Second load cancelled | The fee treatment follows the approved terms and any amendment is traceable. |
| Transport provider charges the shop | The business cost is not automatically treated as a new customer charge. |
Delivery charge allocation: questions from the counter
Should the customer’s fee equal the transport invoice?
Only if that is the actual agreed pricing basis. The business’s cost and the customer’s charge are different records. Staff should not pass on a new amount without the appropriate agreement and approval. Use the documented terms to explain the customer’s balance.
What if the delivery is split for the shop’s convenience?
Check the original agreement before adding any charge. A second dispatch reference does not by itself create authority to bill again. Show the agreed fee once at the appropriate level, and preserve any separately approved change so the combined statement remains understandable.
How can duplicate collection be spotted?
Compare the original fee, payment references and final customer statement across all dispatches. Do not check each receipt in isolation. Two individually plausible entries can collect the same order-level fee twice. Give the reviewer one reference that links the deliveries and the customer’s agreed charge.
Use delivery charge allocation in your next demonstration
For a discussion about delivery charge allocation, contact Vega POS on 0725345345. Bring one anonymised example, its starting position and the result your colleague expects. Ask for a demonstration using those details before assuming a particular feature or integration is available.
Other Kenyan business workflows
For a custom business portal, explore Zama Web Experts. If your team is working in another sector, these services provide different examples: Prim for salon bookings, sales and stock; TAS for chama records and contributions; Saseni for writing orders and delivery; JAAT for shop and product listings; Dereva for driver discovery. Use the service that fits your task; a link does not establish that the systems exchange data.