Working with the Coca-Cola Distribution Management System in Nigeria
I have been running route sheets and warehouse allocations through what is commonly called the Oscposko Casesc Cola Nigeria platform for roughly four years now. The interface has shifted around a few times since I started using it, which means some of the shortcuts I learned early on no longer apply. Here is how things actually work as of the latest round of updates. The most recent update changed how inventory reconciliation triggers during your daily close-out cycle. Previously you could run a stock audit and file it at any point before end of business. Now the system locks the reconciliation window at 5:30 PM local time. If you miss that cutoff, your figures roll into the next working day's opening balance. That caused problems for me last month when a route delivery in Lagos got delayed past the window. My stock report showed a phantom deficit because the system had already locked my previous entries. I found that going into Menu > Adjustments > Emergency Rollback and flagging the day with a code-level override is the only way to fix it without involving regional IT support. It takes about ten minutes and generates a ticket automatically. Regional review usually happens within two business days. If you do not have a rollback code handy, you can get one from your area supervisor, but they sometimes take a day to respond. The workaround is to request those codes at the start of every quarter and keep them printed on your desk.
The dashboard itself is cleaner in this update. They removed the cluttered sidebar navigation that used to span three levels deep. Now everything sits under four main tabs: Orders, Inventory, Route Management, and Reports. Navigation takes less time, though some people who liked the old layout say they had to relearn muscle memory for everything. Order submission follows the same general flow but the validation rules got stricter. The system now cross-checks SKU quantities against historical consumption rates per route before allowing you to submit. If your order deviates more than 15 percent from the rolling average, it flags a review requirement. This catches ordering mistakes early but it also means you cannot quickly override a legitimate large order without attaching a reason code. There are about twenty reason codes available. The most commonly used ones are seasonal spike, promotional event, and new outlet onboarding. Warehouse-to-route transfers have a new confirmation step. You can no longer push stock from a central warehouse to a route vehicle without scanning the driver's RFID badge. This was added after a handful of internal theft cases came to light last year. The downside is that routes with missing drivers at handoff points get stuck. The fix is to designate a backup scorer per route so the transfer process keeps moving even if the primary driver is delayed.
The mobile app version of Casesc received an update around the same time. It now supports offline mode for up to eight hours. When connectivity comes back, it syncs in batches. This is useful for routes that pass through areas with poor signal in parts of Northern Nigeria. The batch sync has a known bug where duplicate entries sometimes appear if the connection drops mid-sync. I have found that manually checking the transaction log for flagged duplicates before approving a sync resolves the issue. The flag shows up as a yellow triangle next to the entry. Pricing tables are managed centrally through the admin portal and push to all field devices automatically. However, there is a lag of roughly forty-five minutes between an admin pushing a price change and the field reps seeing it on their devices. If you run a same-day promotion, this lag can cause pricing disputes at point of sale. The practical solution is to prepare the price update at least two hours before the promotion starts and verify the rollout by spot-checking a few devices across different regions. Reporting has improved significantly. The custom report builder now allows you to save templates and schedule automatic delivery via email. I use this daily for my branch summary reports. Before this feature existed, I spent about an hour every evening manually compiling data from three different screens. Now it generates and sends in roughly twelve minutes. The downside is that the scheduling engine occasionally skips a run if the server is under heavy load during end-of-month closing periods. You can manually trigger a report if you notice it was missed, and the system will generate it within about five minutes.
Get the Full Details
Data export functions support CSV and Excel formats. The CSV export includes a timestamp column that the older Excel template did not, which is helpful for auditing. I recommend always using the CSV export for compliance purposes since the column structure is more transparent and harder to accidentally alter without leaving a trace. The system does not handle multi-currency transactions well. If your operations involve cross-border routes near the Benin or Niger borders, you will need to maintain a separate ledger outside the platform for those entries. The update notes mention this is on their roadmap but there is no confirmed release date yet. Until then, keep an Excel tracker alongside the platform for those edge cases. If you are managing a team that uses this platform, I would suggest running a short training session whenever a major update drops. The changes are not dramatic but the small workflow shifts add up. A fifteen-minute walkthrough covering the new validation rules and the rollback procedure saves a lot of headaches down the line.
