Eshop integration with Entersoft ERP: workflows, prerequisites and testing

Integrate the store with Entersoft ERP around a defined workflow and the installation's available interface. Entersoft integration is particularly useful when a store must apply different prices for corporate customers. Mapping covers item identifier, sales unit, customer, price list, promotion, discount and order.

Entersoft integration is particularly useful when a store must apply different prices for corporate customers. Mapping covers item identifier, sales unit, customer, price list, promotion, discount and order. Publishing one generic product price is insufficient. Define when a trade customer is identified, which commercial policy is displayed, and when that policy is checked again before purchase confirmation. B2B and B2C can share a catalogue while still requiring distinct pricing rules.

The official e-Com Connector presentation describes exchanging items, prices, offers, and orders with external applications. This concerns business data integration rather than only importing a catalogue file. Entersoft ERP and Entersoft WMS serve different purposes. The connector must be checked against the actual customer version and enabled modules.

An electrical wholesaler sells the same switch to consumers and installers. A guest sees retail pricing, while an identified installer sees agreed trade pricing. The store retains the customer code and sales unit so that one carton is not transmitted as one individual item. If a promotion expires during checkout, the order follows the agreed revalidation and customer-notification procedure. Discounts are not applied a second time when ERP receives the transaction.

An important failure scenario occurs when an offer expires while the customer still has an open shopping cart. Keep the external reference and confirmed destination ID before retrying. Separate access failure, business rejection and an unknown outcome. An operator must be able to inspect the relevant record and resolve its status without replaying completed steps. Agree which fields may appear in logs and who handles unresolved cases.

Test a trade customer and a guest buying the same item, an expired offer, and a quantity change. For each case record the expected source data, destination record and customer-visible state. Include one denied-permission case and one interrupted response. Re-run a previously confirmed event and check that its business effect is unchanged. The acceptance record should identify the responsible team and the evidence required to close any discrepancy.

The initial discovery should confirm: Web API/e-Com Connector access in the installation; Agreed B2B and B2C pricing rules; Test customer and promotional data. Before launch, document the mapping for Items and prices → online catalogue → Customer identification → commercial policy → Order → ERP → status feedback. Assign responsibility for access renewal, monitoring and correction. A change to product configuration or the agreed business rule should trigger targeted regression checks. Begin with this defined workflow; add another channel only after its ownership and acceptance cases are clear.