Eshop integration with WMS / Entersoft WMS: workflows, prerequisites and testing

Integrate the store with WMS / Entersoft WMS around a defined workflow and the installation's available interface. WMS integration gives the store actual execution state: reservation, picking, packing, loading and returns. Core data includes order reference, item, quantity, location or warehouse where needed, executed quantity and shipment reference.

WMS integration gives the store actual execution state: reservation, picking, packing, loading and returns. Core data includes order reference, item, quantity, location or warehouse where needed, executed quantity and shipment reference. One dispatched status is insufficient for partial fulfilment. Define a state vocabulary with the warehouse owner so that customer communication follows confirmed stages rather than merely the creation of a picking request.

Entersoft WMS documentation describes picking, packing, loading, returns, and shipment-order stages. SCM360 presents additional warehouse automation. Actual capabilities depend on the installation and enabled modules. WMS manages physical warehouse execution and is not equivalent to a single stock figure in the online store. We verify the available interface and do not assume every automation feature or hardware component is included.

A sporting-goods store receives an order for two pairs of shoes and a shirt. The warehouse picks the shoes but discovers a problem with the shirt. WMS returns executed quantities and the store displays the agreed partial state. Packing does not automatically mean loading onto the carrier. If a pair is returned, availability follows the warehouse suitability check rather than merely receipt of a parcel. Order and shipment references keep individual movements connected.

An important failure scenario occurs when a quantity is picked only partially and the store risks marking the entire order dispatched. 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 partial picking, cancellation before loading, and a return not yet inspected. 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: Warehouse owner and available WMS interface; Defined status vocabulary and available-stock rule; Realistic picking/packing/returns test scenarios. Before launch, document the mapping for Store order → WMS execution request → Reservation → picking/packing → actual loading → Partial/full execution → store status. 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.