Assess B2B ordering separately before replacing the ERP

I would first assess a difficult ordering journey for business customers (B2B) separately from replacing the business management software (ERP). Better search, a reusable item list or a clearer status display can be built in a customer application. Whether that approach works depends on the existing integration and required business rules.

Draw the boundary for each function

A fictional wholesaler of technical supplies wants to make reordering easier for customers. The existing ERP remains responsible for customer prices and order creation. The following allocation is a proposed design.

This makes the work that actually concerns the interface visible. Better item search does not automatically require a new order management system. It offers little help, however, if the selected items are then transferred incorrectly to the existing system.

Translation cannot supply a missing capability

Microsoft describes a translation layer between differently modelled systems. Such a boundary can help when the customer application and ERP use different data forms. In this example it should carry the agreed mapping rather than create two independently maintained sets of pricing rules.

If the ERP does not answer an order creation request in time, the application needs to handle the uncertain outcome. Retrying must not create an additional order without checking. Planning therefore needs a recognisable transaction and a reliable way to establish the result. A visual success message does not provide that evidence.

Where separate renewal reaches its limit

If the existing system cannot supply required customer prices, create orders in a controlled way or support permissions appropriately, a new interface alone is insufficient. Adaptations, another integration route or replacing the ERP then need consideration. The smaller initial measure is not an end in itself.

Conversely, not every project needs an additional mediation service of its own. If an existing, maintained interface meets the required mapping, extra infrastructure should justify its workload.

A limited trial would be meaningful for the wholesaler: find an item in the correct customer context, show the confirmed price, transfer a test order and associate its result again. If the interface fails, that is where work is needed. If the core system lacks a required capability, the decision must account for that limit. The scope of ERP replacement then follows from a demonstrated problem.

Sources

• Microsoft Azure Architecture Center: Anti-Corruption Layer pattern