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 adding a warehouse, supplier or sales channel is configuration, not a new spreadsheet. Most growing organisations need better data and process discipline before more software.

The short answer

Growth strains items, suppliers, locations, channels and delivery promises. A system that scales has:

  1. One version of item and stock data across purchasing, sales, warehouse and finance.
  2. Stock movements as transactions, not hand adjustments.
  3. Purchasing by rules (reorder levels, lead times, demand), not memory.
  4. Traceability by batch or serial where required.
  5. Integration with online stores, marketplaces, logistics providers, carriers and suppliers.

ERP, warehouse system or both: the foundations matter more.

Warning signs your current setup will not scale

  • Stock counts disagree with the system, and the fix is a manual adjustment
  • Salespeople check with the warehouse before promising a delivery date
  • Reordering depends on one or two people who "just know"
  • 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, not applied to stock
  • A new location means copying a spreadsheet
  • Tracing a supplier quality problem or recall to customers would take days

If several apply, more volume will amplify the problems.

The foundations

Item master data

Codes, units, suppliers, lead times, reorder levels, tax classes, tracking; one owner, approval for new items.

Inventory control

Every receipt, transfer, pick, shipment, return and write-off as a transaction; regular cycle counts.

Replenishment

Reorder levels per item and location, reviewed on schedule; the system drafts requests or orders.

Traceability

Batch tracking set up before go-live for batch or expiry products: food, pharmaceuticals, chemicals, consumables.

Landed cost

Freight, duties, levies, clearing and port charges applied to the cost of stock received.

Integration

Decide which system owns stock availability and orders; connect the others to it.

Duplicate and inconsistent items are the most common reason supply chain systems disappoint; manual re-keying between channels is where overselling and missed shipments start. Stock in a Lagos or Port Harcourt depot, or on a truck between them, is still stock the system should know about.

Nigerian imports and regulated products. Many importers buy in US dollars, so the exchange rate on the payment date moves 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 match easily. Import lead times include port clearance: measure from order to goods received. Regulated food, drug and cosmetic products fall under NAFDAC; you need to show where a batch came from and went if a product is recalled. Check current NAFDAC requirements for your product category.
More on each foundation
  • Item data also covers units of measure and conversions, supplier part numbers, weights and dimensions, and whether an item is tracked by batch or serial.
  • Inventory: cycle counts mean counting a portion of stock regularly instead of one annual count; investigate differences rather than simply correcting them. Set up multiple warehouses or bins as locations, with transfers recorded when stock moves.
  • Purchasing: track supplier lead times and on-time delivery so planning numbers reflect reality.
  • Traceability: in ERPNext, for example, a batch can carry an expiry date and shows as expired once that date passes (ERPNext documentation).
  • Channels typically added with growth: an online store, a marketplace, a third-party warehouse, electronic data interchange (EDI) with large customers.

Measures worth tracking

A few measures, defined consistently, show 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 definitions before building reports, and track the trend rather than a single month.

A worked example
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 anyone can create items, a new system produces 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