Article

Supply chain management systems that support growth

A supply chain system supports growth when everyone works from the same item, stock and order data, and when adding a warehouse, supplier or sales channel is a configuration task rather than a new spreadsheet. Most growing organisations need better data and process discipline before they need more software.

The short answer

Growth strains a supply chain in predictable places: more items, more suppliers, more locations, more sales channels and more customers expecting accurate delivery dates. A system that supports growth has five qualities:

  1. One version of item and stock data, shared by purchasing, sales, warehouse and finance.
  2. Stock movements recorded as transactions, not adjusted by hand afterwards.
  3. Purchasing driven by rules (reorder levels, lead times, demand), not by memory.
  4. Traceability by batch or serial number where products require it.
  5. Integration with the channels and partners you rely on: e-commerce, marketplaces, third-party logistics providers, carriers and suppliers.

Whether that system is an ERP, a warehouse management system, or both, matters less than whether these foundations are in place.

Warning signs your current setup will not scale

  • Stock counts regularly disagree with the system, and the fix is a manual adjustment.
  • Salespeople check with the warehouse before promising a delivery date.
  • Purchasing depends on one or two people who "just know" when to reorder.
  • The same item has different codes or descriptions in different systems.
  • Landed costs (freight, duties, clearing agent charges, exchange-rate differences) are estimated at year-end rather than applied to stock.
  • Opening a new location means copying a spreadsheet.
  • A supplier quality problem or recall would take days to trace to customers.

If several of these apply, adding volume will amplify the problems.

The foundations

Item master data

Every other process depends on item data: codes, descriptions, units of measure and conversions, suppliers and supplier part numbers, lead times, reorder levels, weights and dimensions, tax classes, and whether the item is tracked by batch or serial. Assign an owner for item data and a simple approval step for new items. Duplicate and inconsistent items are the most common reason supply chain systems disappoint.

Inventory control

Record every receipt, transfer, pick, shipment, return and write-off as a transaction. Use cycle counts (counting a portion of stock regularly) rather than relying on one annual count, and investigate differences instead of simply correcting them. Multiple warehouses or bins should be set up as locations in the system, with transfers recorded when stock moves. Stock held in a depot in Lagos or Port Harcourt, or on a truck between them, is still stock the system should know about.

Purchasing and replenishment

Set reorder levels and quantities per item and location, review them on a schedule, and let the system raise material requests or draft purchase orders. Track supplier lead times and on-time delivery so that the numbers used in planning reflect reality. For imported items, lead times include port clearance, so measure them from order to goods received rather than from order to shipment.

Traceability

For products with batches or expiry dates (food, pharmaceuticals, chemicals, many consumables), batch tracking needs to be configured before go-live. In ERPNext, for example, a batch can carry an expiry date and show its status as expired once that date passes (ERPNext documentation). Some sectors have explicit rules: regulated food, drug and cosmetic products fall under NAFDAC, and a business handling them needs to be able to show where a batch came from and where it went if a product has to be recalled. Check the current NAFDAC requirements for your product category.

Landed cost and imports

For imported goods, apply freight, duties, levies, clearing and port charges to the cost of the stock received. Many Nigerian importers also buy in US dollars, so the exchange rate on the day of payment can move the real cost of stock; record the difference rather than burying it in the margin. The Nigeria Customs Service assesses and collects import duties on commercial goods, so it helps if customs entries and ERP receipts can be matched easily.

Integration

Growth usually means more channels: an online store, a marketplace, a third-party warehouse, electronic data interchange (EDI) with large customers. Decide which system owns stock availability and orders, and connect the others to it. Manual re-keying between channels is where overselling and missed shipments start.

Measures worth tracking

You do not need a large dashboard. A few measures, defined consistently, tell you whether the supply chain is keeping up:

MeasureWhat it tells you
Stock accuracy (count vs system)Whether transactions are being recorded properly
Fill rateHow often you ship what the customer ordered, when promised
Supplier on-time deliveryWhether planning lead times are realistic
Inventory turns or days on handWhether stock levels match demand
Short-dated or obsolete stock valueHow much is at risk of write-off

Agree the definitions before building reports, and track the trend rather than a single month.

Demonstration, not a client project

Hypothetical example. A regional distributor of cleaning and hygiene supplies has grown from one warehouse to three and has added an online store. Stock is held in accounting software with a separate spreadsheet per warehouse, and the online store's stock levels are updated by hand each morning.

A practical plan: clean and de-duplicate the item list; set up the three warehouses as locations in one ERP; record transfers between them; add reorder levels for the fastest-moving items first; turn on batch tracking for products with expiry dates; and connect the online store so that orders flow in and stock levels flow out automatically. Each step can go live separately.

Readiness checklist

Data

  • Is there one item list, with an owner and an approval step for new items?
  • Are units of measure and conversions consistent across purchasing and sales?
  • Which items need batch, expiry or serial tracking?

Process

  • Is every stock movement recorded as a transaction?
  • Do we cycle count, and do we investigate differences?
  • Are reorder levels and lead times set, and reviewed on a schedule?

Cost

  • Are freight, duties and clearing charges applied to stock when it is received?

Channels and partners

  • Which system owns stock availability?
  • Which channels, warehouses or partners need automatic integration?

Growth

  • What happens in the system when we add a warehouse, supplier or channel?

Limitations

Software cannot fix a process nobody follows. If receipts are not recorded when goods arrive, or items are created freely by anyone, a new system will produce the same inaccurate results faster. Very high-volume or highly automated warehouses may also need a dedicated warehouse management system alongside the ERP.

Next step

Prometheus ERP, our ERP built on ERPNext, includes inventory control across multiple warehouses, batch management, landed cost vouchers, multi-currency accounting and automated replenishment. See also our work with distribution and retail and transportation and logistics organisations, and our guide to preparing data for an ERP migration.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Batch, ERPNext documentation (Frappe)
  2. Nigeria Customs Service, Nigeria Customs Service
  3. NAFDAC, National Agency for Food and Drug Administration and Control

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in NGN before any work starts