Custom ERP vs Off-the-Shelf: What Fits Indonesian Distributors?

In the distribution software projects we handle at Sahabat Teknologi, the need for custom ERP rarely starts with a request for a different interface. It usually starts with operational rules that have become too specific to manage efficiently in a standard workflow: multiple warehouses, different prices for wholesalers and project customers, approval limits based on transaction value, overseas purchasing with containers and ETAs, and orders arriving from marketplaces or WhatsApp. The more useful question is therefore not “Which ERP has more features?” but “How much of our business process would have to change to fit the software?” Established ERP platforms already cover many core distribution requirements. Odoo, for example, supports multiple warehouses and stock movements between locations. That means multi-warehouse support alone is not a strong reason to build an ERP from scratch. The stronger case for custom ERP appears when business rules directly affect how the distributor makes money. Consider a building-material distributor with different prices based on customer type, purchase volume, brand, payment terms, branch, and project. If sales staff must open several spreadsheets before confirming the correct selling price, the problem is not simply user convenience. A small pricing error repeated across hundreds of orders can directly reduce gross margin. A custom distribution system can make pricing rules, minimum margins, discount approvals, and price history part of the transaction itself.

ERP cost comparisons often fail because companies focus only on the license or initial development quote. For a distributor, the real cost is closer to Total Cost of Ownership: implementation, data migration, training, integrations, customization, maintenance, and the cost of operational work that remains manual. Off-the-shelf ERP normally has an advantage at the beginning because many modules are already built and tested across recurring use cases. Odoo, for example, provides vendor pricelists that can automatically populate supplier prices into RFQs or purchase orders, including bulk import through XLSX or CSV. Rebuilding such a standard capability usually makes little economic sense. Custom ERP requires a larger initial investment because the company-specific rules, workflows, APIs, database structures, reports, and integrations must be designed and implemented. The trade-off is that the business does not have to keep paying for workarounds just because the software’s workflow is different from its own. Imagine a distributor with three warehouses where every sales representative has a different discount authority. A standard ERP may support the rule through configuration or additional modules. If that configuration becomes difficult to maintain, every future change can become more expensive. A custom ERP can encode a rule such as “discounts above 7% require supervisor approval” or “this customer price is valid only for this branch.” However, custom does not mean rebuilding everything. Our usual recommendation is to customize only the areas that genuinely differentiate the business. Mature capabilities such as authentication, basic user management, standard purchasing, or basic inventory do not automatically need to be reinvented.

Multi-level pricing is one of the areas that looks simple at first and becomes complicated quickly in distribution. One product may have retail, wholesale, reseller, project, and customer-specific prices. Prices may also change according to quantity, promotional periods, branch, or payment terms. Mature ERP platforms already provide pricing engines. Microsoft Dynamics 365 Supply Chain Management, for example, supports pricing attributes covering product categories, product variants, customer areas, payment methods, payment terms, ordering channels, and delivery methods. Therefore, a distributor should never assume that an off-the-shelf ERP cannot handle complex pricing. The real test is whether the company’s rules can be configured cleanly without creating an operational mess. In a distributor ERP assessment, we typically recommend testing 20–50 real pricing scenarios before deciding whether custom development is necessary. For example: customer A receives price X at 100 cartons; customer B receives reseller pricing; a project order receives a special discount but cannot fall below the minimum margin; certain salespeople can discount only within their authority; and imported products need exchange-rate and additional-cost considerations. If most scenarios can be configured cleanly, an off-the-shelf ERP remains a strong option. If critical rules require spreadsheets, frequent manual overrides, or multiple layers of customization, custom ERP has a stronger ROI case.

Distribution operations in Indonesia often continue far beyond a purchase order. Goods may be purchased from an overseas supplier, assigned to a container, tracked against an ETA, processed through documentation, and only then received into the warehouse. On the sales side, orders may arrive from internal sales teams, a website, marketplaces, or other channels. An off-the-shelf ERP can cover many of these processes, but the integration points need to be examined in detail. Odoo, for example, provides purchase orders, vendor pricelists, receipts, and inventory workflows as standard capabilities. For a distributor with complex import operations, custom ERP can connect supplier invoices, container planning, document tracking, ETAs, additional costs, actual receipts, and accounting into a single operational lifecycle. For example, if one supplier invoice is allocated across two containers, the system can maintain the one-to-many relationship and track partial arrivals without treating the entire invoice as received. The same principle applies to marketplace integrations. Do not stop at asking whether an ERP “integrates with marketplaces.” Check whether the API can retrieve orders, map SKUs, update inventory, handle cancellations and returns, process settlement data, and synchronize order status without duplicates. If marketplace orders still need to be exported to Excel and manually imported into the ERP every day, the integration has not actually removed the operational bottleneck.

The answer is not determined by company size alone. A large distributor may be perfectly suited to an off-the-shelf ERP if its processes are relatively standard. A smaller distributor may need custom ERP if its operating model is highly specialized and transaction volume makes small errors expensive. A practical approach is to calculate the value of three things: workaround cost, error cost, and time saved. For example, if an administrative team spends two hours every working day reconciling stock across different sources, checking prices, and correcting marketplace orders, that workload can be quantified before comparing software investments. Add the risk of inaccurate stock, incorrect pricing, wrong shipments, delayed approvals, and uncontrolled margins. This makes the ROI of custom ERP much easier to evaluate. Do not build a custom ERP because users dislike the interface of an off-the-shelf product. That is a weak business case. Build custom when the company’s business rules, integrations, data, and workflows create greater economic value when the system follows the actual operating model. Conversely, if the requirements are mainly sales, purchasing, inventory, accounting, multi-warehouse management, and basic pricing, a mature off-the-shelf ERP is often the more rational choice. Modern standard platforms already cover capabilities that once required significant development, including warehouse management and advanced pricing. One of the most common mistakes we see is selecting technology before mapping the real process. The safer sequence is to map actual transactions, quantify the problems, test an off-the-shelf ERP using real scenarios, and then identify the gaps. If the gaps are cosmetic, do not customize. If they affect margins, inventory control, approvals, integrations, or operational speed, build the business case for custom ERP.