A consignment is discharged at Mombasa and only part of it will ever be sold in Kenya. Some moves inland on the A104, some by rail on the SGR, and it is broken down in a Nairobi warehouse before going out on routes through Nakuru and Eldoret. The remainder is already spoken for by a buyer whose warehouse sits beyond Malaba.
Up to the frontier, the brand can say where that stock is and what it sold for. Past it, the record thins to an invoice, a delivery note and a phone number. The goods keep moving, shelves keep turning, and head office stops seeing any of it.
This is the ordinary shape of Kenyan distribution rather than an edge case. Along the Northern Corridor, Kenyan distributors routinely serve Uganda, Tanzania, Rwanda, Burundi, South Sudan and eastern DRC out of the same depots and the same catalogue. The difficulty is that most sales systems were designed to stop where the country stops.
One Corridor, Several Markets
The Northern Corridor is the defining freight artery of the region, and it does not belong to one market. Stock lands at Mombasa, moves inland through Nairobi, Nakuru and Eldoret, and a meaningful share carries on towards Malaba. The same road and rail line serve a Kenyan duka and a buyer several markets away.
That is a commercial advantage before it is a logistics fact. A distributor near the corridor can reach demand a purely domestic competitor cannot, and a brand that appoints one can cover several markets without a separate operation in each.
The cost is rarely priced in. Every market the corridor touches has its own currency, retail structure, trade terms and regulatory regime. A model built for Kenya alone fits exactly one of them, and quietly misdescribes the rest.
A Morning at Malaba
Consider a load that left a Nairobi warehouse for a buyer on the far side of Malaba. It is real stock against a real order, picked, invoiced and dispatched, and the sales manager who agreed the deal has already counted it in the month.
At the frontier the lorry joins a queue. A clearing agent works through the formalities. The driver waits. None of that is unusual or anyone's failure. What matters commercially is what the brand's own system believes during that interval.
In most set-ups the system believes the stock is gone. It left the depot, so it is no longer depot stock. It has not been received anywhere, so it is not anybody's stock either. A planner running a position that morning will not see those units, and if the buyer rings, the honest answer is a phone call to the transporter.
Meanwhile a rep working a beat through Eldoret is selling against a national availability figure already reduced by a consignment nobody can see. The frontier did not create the problem. It only held the stock still long enough for an existing gap to become visible.
The Stock That Crosses and Disappears
Once a consignment is across, most brands lose the thread. The export sale is recorded as one transaction to one account. Which outlets took it, at what price, how quickly it moved and what is still sitting in a back room is not captured anywhere the brand can read.
So a large slice of turnover ends up managed on primary dispatch alone. Dispatch tells you what you sent, not what was consumed, and those two numbers can drift apart for a long time before anything forces a reconciliation. The consequences are familiar to anyone who has run an export desk as a relationship business:
- A buyer who is over-stocked keeps ordering, because ordering protects their allocation, and the correction arrives as a sudden stop.
- A buyer who is short stays invisible until they complain, by which point a competitor has had the shelf for a full cycle.
- Near-expiry stock in a market you cannot see is discovered rather than managed, and a variant that has missed its season is hard to pull back once it has crossed.
- Trade spend against a volume commitment is settled on the buyer's own claim, because there is nothing independent to check it against.
Pricing in More Than One Currency
The Kenyan price list is held in KSh. Every other market the corridor serves prices in its own currency, and the brand has to decide deliberately which currency each relationship is transacted in and who carries the movement between them.
That decision is usually made once, informally, then never revisited. A price is agreed, someone converts it in a spreadsheet, and that figure becomes the reference for months. When the underlying rate moves, margin moves with it, and nobody notices until a quarterly review shows a market less profitable than its volume suggests.
A workable design treats currency as a property of the price list rather than an afterthought in a workbook. Each market gets its own list, in its own currency, with an owner, a date and a change history. Discounts and schemes are expressed in the same currency as the list they apply to, so a field concession cannot mean two different things in two markets, and nobody converts anything in their head at a counter. For the group view, hold both: the transaction currency the market acts on, and a clearly labelled restatement with its basis stated.
Territory Design That Stops at a Frontier
Most territory structures are drawn as a hierarchy of Kenyan geography: region, area, town, route, outlet. Cross-border volume fits nowhere in that tree, so it is bolted on as an extra account under whichever region owns the relationship, often the one nearest the corridor.
That single decision distorts a lot. The region carrying the export account looks like the strongest performer in the country, because a warehouse-to-warehouse shipment sits in the same total as counter-level sales from dukas, kiosks and agrovets. Incentives follow the number and attention follows the incentives, so patient work on domestic routes comes second to one colleague managing one relationship.
The fix is structural rather than motivational.
- Separate the motions. Domestic route sales and cross-border supply are different jobs with different rhythms, and one shared target rewards the wrong behaviour.
- Give the frontier a territory, not a footnote. Buyers beyond Malaba need coverage plans, call frequency and service standards as a Kenyan route does.
- Do not let one account define a region. If a single customer can swing a region's number, the region has stopped being a useful unit of management.
- State who owns the price. Where a domestic territory and a cross-border account can both quote the same trade, the difference must be a decision rather than an accident of who answered the phone.
Parallel Trade and the Leak Back Across the Border
Where prices, pack sizes or promotional terms differ between neighbouring markets, stock will find the gap. Goods sold cheaply into one market reappear in another, frequently in the direction of the larger, denser trade. Nobody sets out to run a parallel channel; it emerges because arbitrage is rational for the person doing it.
The symptoms are recognisable long before the cause is. Kenyan wholesalers offer a line below the price the appointed distributor pays for it. Packs turn up in a labelling variant meant for elsewhere. A market's offtake looks stronger than its retail base plausibly supports, while another market's dukas are unexpectedly well supplied by nobody in particular.
You cannot police this by instruction, and heavy-handed enforcement pushes it further from view. What works is making the flow visible enough to argue about with facts. Batch identification captured at dispatch and read again in the trade turns a suspicion into a traceable route, and consistent pack coding makes an out-of-market variant obvious to a rep at a counter rather than an analyst months later. Once you can see where the leakage runs, you can close the terms gap, adjust pack strategy, or price for the flow. Not knowing which of those you are doing is the only wrong answer.
One Product Master, Several Markets
Cross-border work strains the product master. The same brand may ship one pack to Kenya and a different variant beyond the frontier, with different labelling, different language on the artwork and sometimes a different case configuration. Carried as a single code, every downstream number becomes an average of things that are not the same.
In Kenya, standards and product marking fall under KEBS, and Kenyan packs are built accordingly. Requirements in the neighbouring markets are set by their own authorities and should be confirmed there rather than inferred. The safe assumption is that a pack approved for one market is not automatically right for the next.
Batch and expiry discipline matters more here than in a domestic network, because a recall or a quality query has to cross the same frontier the goods did. If the batch was not captured at dispatch, tracing it depends on the buyer's records, and those are not yours to rely on.
Invoicing and Collections Across the Frontier
The Kenyan leg of a cross-border sale is still a Kenyan transaction, and Kenyan invoicing obligations apply. KRA has required electronic tax invoices through eTIMS since January 2024, covering businesses of all sizes including those not registered for VAT, and from 1 January 2026 KRA validates income and expenses declared in income-tax returns against eTIMS data. An expense without a valid eTIMS invoice behind it is not deductible, and the penalties for getting this wrong are material.
How a specific export or cross-border sale should be treated for tax is a question for a tax adviser or KRA directly, not something to settle from a distribution playbook. The same applies to customs and the other formalities at the frontier: they are real, they take time, and the detail belongs with a licensed customs agent. What a sales system owes the business is narrower and within its control — a correct, complete, on-time invoice on the Kenyan side, tied to the order and dispatch it belongs to.
Collections split along the same line. On the Kenyan side, M-Pesa is how money normally moves, and reconciling till and paybill receipts against invoices is ordinary daily work. Cross-border settlement runs on longer credit and larger balances across fewer transactions, so exposure is concentrated rather than spread. A single account can carry more open value than a whole route of dukas, which makes the usual controls — a credit limit checked at order entry, visible ageing, a block that actually blocks — matter more, not less, when the customer is harder to visit.
Designing for Thin Signal and Interrupted Power
Any capture design for corridor work has to assume the connection will not always be there. Coverage thins on rural stretches and at frontier points where many people compete for the same network. Power supply is not uniformly reliable either: Kenya experienced a nationwide blackout in 2026 and electricity costs remain high. The grid is not permanently down, but that is reason enough to design for interruption rather than be surprised by it.
The workable pattern is offline-first. The handset holds the outlet list, the catalogue, the correct price list and the last known stock position. The order, the delivery confirmation, the stock count and the collection are captured with no connection, and the device syncs when the network returns. Nothing is retyped from a notebook, and no record waits on coverage.
Where Cross-Border Programmes Go Wrong
These programmes rarely fail on the technology. They fail on a handful of design decisions taken early, usually for understandable reasons, and then never revisited.
The same mistakes recur, and each one is cheaper to avoid than to unwind.
- Treating the export desk as a relationship rather than a channel. One person holding the buyer relationships in their head works until that person is unavailable, and then the market goes dark.
- Reporting cross-border volume inside a Kenyan region. It flatters the region, distorts incentives and hides two different businesses behind one number.
- Having no state for goods at the frontier. If a position knows only dispatched and received, every consignment in the queue is invisible to whoever places the next order.
- Running one price list for several currencies. A converted figure in a spreadsheet stops being right the moment the rate moves, and nobody is accountable for noticing.
- Assuming a Kenyan pack or process travels. Labelling, standards and formalities are set market by market and have to be confirmed, not inferred.
- Launching across every market at once. Prove the flow on one corridor lane, fix what breaks at the frontier and at the counter, then extend.
How 1Channel Supports Cross-Border Distribution
Corridor work only holds together when the order, the dispatch, the invoice, the stock count and the collection sit in one system, because they belong to one journey. 1Channel brings distributor management and field sales onto a single offline-first platform, so the depot record and the counter record are the same record.
The platform is built for multi-currency, multi-language and multi-timezone operation, with KES handled natively and Kiswahili among the supported languages — what a Kenya-based team needs when one catalogue serves more than one market. Reps work on entry-level Android handsets and sync when coverage returns. For distributors running corridor volume alongside domestic routes, the platform lets a team:
- Hold a separate price list per market and per currency, with its own owner, effective dates and change history, so no one converts a price by hand.
- Model cross-border demand as its own territory in the hierarchy, with its own targets and reporting, instead of folding it into a Kenyan region.
- Track stock between plant, depot, distributor and van with an explicit in-transit status, so goods held at a frontier stay visible in the position.
- Capture batch and expiry at goods receipt and dispatch, so a pack found in the wrong market or a quality query can be traced to a specific movement.
- Enforce credit limits, ageing and order blocks per account, which matters most on concentrated cross-border balances.
- Support eTIMS-aligned invoicing on the Kenyan side and record M-Pesa till and paybill collections against the same order, so stock, invoice and payment reconcile.
- Work fully offline on the handset and sync later, with role-based access and audit trails aligned to Data Protection Act, 2019 obligations.
Key Takeaways
Serving the region from Kenya is a genuine advantage, and only an advantage if the visibility travels with the goods. A few principles carry most of the value:
- Give the frontier a status. Stock waiting at Malaba is neither depot stock nor sold stock, and a position with no state for it will mislead whoever places the next order.
- Make currency a property of the price list. One list per market, in its own currency, with an owner and a date, keeps margin from moving quietly while nobody is watching.
- Give cross-border trade its own territory. Folded into a Kenyan region, it flatters that region and hides two businesses inside one number.
- Trace packs, do not police them. Batch identification and consistent pack coding turn parallel trade from a suspicion into a route you can price for or close.
- Confirm the formalities, do not assume them. Customs, labelling and tax treatment are set market by market — take them to a customs agent and a tax adviser, and keep the sales system to what it can control.
Get those right and the border stops being the point where the data ends. The corridor carries the goods either way; the question is whether it carries the record with them.
