How a Trading Company Digitalised in 12 Weeks

A Singapore-based trading company with 15 employees replaced their spreadsheet-driven operations with a custom ERP system in 12 weeks, reducing order processing time by 65% and eliminating SGD 4,000 per month in operational inefficiencies. This is how they did it and what other trading SMEs can learn from their experience.

What Problems Were They Facing Before Digitalisation?

The company traded industrial components across Southeast Asia, managing roughly 200 purchase orders and 300 sales orders per month. Their operations ran on a combination of Excel spreadsheets, email, and WhatsApp — a setup that had worked well enough when they were smaller but was now causing serious problems.

Their inventory tracking was particularly painful. Stock levels were updated manually in a shared spreadsheet, but by the time the warehouse updated the file, the sales team had already promised stock that was not actually available. This led to an average of 8-10 backorder situations per month, each requiring scrambled communications with suppliers and apologetic calls to customers.

Invoicing was another bottleneck. The accounts team manually created each invoice in Excel, cross-referencing delivery orders and purchase orders from different files. Errors crept in regularly — wrong quantities, outdated pricing, mismatched reference numbers. Each error required a credit note, a revised invoice, and wasted time for both the company and their customer.

The breaking point came when they lost a SGD 50,000 order because they could not confirm stock availability quickly enough. The customer went to a competitor who could give an immediate answer. That single lost deal justified the entire digitalisation investment.

How Did They Approach the ERP Implementation?

Rather than buying an off-the-shelf ERP and spending months customising it, the company chose a custom-built solution designed specifically around their trading workflows. The rationale was pragmatic: generic ERP systems built for manufacturing or retail would require extensive modification to handle their specific needs around multi-currency pricing, supplier commission structures, and regional logistics coordination.

The implementation followed a compressed 12-week timeline. Weeks one and two focused on process mapping — documenting every workflow, every spreadsheet, every manual handoff. This was the most valuable phase, as it revealed redundancies and bottlenecks that had become invisible through familiarity.

Weeks three through eight covered system development. The core modules were built iteratively: inventory management first, then sales order processing, then procurement, then invoicing and accounts receivable. Each module was demonstrated to the team as it was completed, and feedback was incorporated immediately.

Weeks nine and ten were dedicated to data migration and testing. Historical customer data, product catalogues, and pricing sheets were imported from their spreadsheets. The team ran real orders through both the old spreadsheet process and the new system in parallel, verifying accuracy.

Weeks eleven and twelve were the go-live period. The old spreadsheets were retired, and the team worked exclusively in the new system with on-call support available for any issues.

What Results Did They See After Going Live?

The quantifiable results appeared quickly. Order processing time dropped from an average of 45 minutes to 15 minutes per order. The sales team could check real-time stock levels and confirm availability to customers immediately, eliminating the backorder problem entirely within the first month.

Invoice accuracy improved from approximately 94% to 99.5%. The system auto-populated invoice details from confirmed sales orders and delivery records, removing the manual transcription that caused most errors. The accounts team went from spending three days per week on invoicing to half a day.

Cash flow improved because invoices went out faster and payment tracking was automated. The average days sales outstanding (DSO) dropped from 52 days to 38 days — a 27% improvement that freed up significant working capital.

The less quantifiable but equally important result was visibility. Management could see real-time dashboards showing sales pipeline, inventory levels, outstanding payments, and profit margins by product line. Decisions that previously required days of data compilation could now be made in minutes.

What Lessons Apply to Other Trading SMEs?

Several lessons from this implementation are broadly applicable. First, custom does not mean expensive or slow. A focused custom solution that addresses your specific workflows can be implemented faster and more effectively than a bloated generic system.

Second, involve your frontline staff from day one. The warehouse team, the sales coordinators, the accounts clerks — they know where the real problems are, and their buy-in determines whether the system succeeds or becomes expensive shelf-ware.

Third, do not try to digitise every process simultaneously. Prioritise the workflows with the highest pain and the clearest ROI. For trading companies, that is almost always inventory visibility and order-to-invoice processing.

Frequently Asked Questions

Is a custom ERP realistic for a 15-person company?

Absolutely. Custom ERP does not mean a multi-million dollar SAP implementation. For a focused trading operation, a custom system covering inventory, sales, procurement, and invoicing can be built and deployed for a fraction of what you would spend on a large enterprise system. The key is scoping the system to your actual needs rather than building for hypothetical future requirements.

How did they handle staff resistance to the new system?

Resistance was minimal because staff were involved in the design process and could see their specific frustrations being addressed. The parallel running period — two weeks of using both old and new systems — was critical. By the time the old spreadsheets were retired, every team member had experienced the new system working correctly and was ready to commit to it.

What ongoing maintenance does a custom ERP require?

Plan for ongoing support covering system updates, minor feature additions, and occasional troubleshooting. The company budgets approximately SGD 500-1,000 per month for maintenance and periodic enhancements. New requirements emerge as the business evolves — adding a new report, adjusting a workflow, integrating with a supplier's system — and having a responsive development partner makes these changes straightforward.