Eshop integration with SoftOne / Soft1 ERP: workflows, prerequisites and testing

Integrate the store with SoftOne / Soft1 ERP around a defined workflow and the installation's available interface. A Soft1 integration starts with the company and branch where each online order will be recorded. Map the item identifier, variant, customer, fulfilment warehouse, payment method and commercial document series.

A Soft1 integration starts with the company and branch where each online order will be recorded. Map the item identifier, variant, customer, fulfilment warehouse, payment method and commercial document series. We recommend keeping commercial policies in ERP and returning the store order reference to the connected workflow. Availability is not simply the sum of every warehouse: the business must decide which inventory can actually fulfil the online channel.

The login and authenticate calls precede access to business objects. The reference describes getData and setData, together with lookup and calculation services. Soft1 is distinct from Entersoft and Atlantis. The installed version, enabled modules, and local configuration determine the final integration.

A tools retailer stocks the same drill in Athens and Thessaloniki, but online orders are fulfilled only from Athens. The connector publishes the agreed balance for that warehouse, maps the variant identifier, and submits the order to the correct branch. If the customer requests business invoicing, the company account and sales type are checked before recording the transaction. The local reference retains both the store order ID and the confirmed ERP ID.

An important failure scenario occurs when the order has been recorded in Soft1 but its response is lost before reaching the store. 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 branch change, resending the same order, and a mismatched variant code. 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: Least-privilege Web Account/AppID; Enabled Web Services endpoint and a test company; Agreed warehouse, price-list, and document-series policies. Before launch, document the mapping for Soft1 products → store catalogue → Store order → customer/branch mapping → Record creation → confirmation → reconciliation. 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.