Eshop integration with Galaxy ERP: workflows, prerequisites and testing

Integrate the store with Galaxy ERP around a defined workflow and the installation's available interface. Correct Galaxy synchronisation depends on the Web Scenario and continuity of revision numbers. The store needs an initial snapshot of items, attributes and inventory, followed by the agreed changes.

Correct Galaxy synchronisation depends on the Web Scenario and continuity of revision numbers. The store needs an initial snapshot of items, attributes and inventory, followed by the agreed changes. Save the update checkpoint only after data has been applied completely. Online customer and purchase operations are organised separately from bulk catalogue updates. With multiple companies or scenarios, destination selection is an essential mapping decision rather than merely a technical detail.

Sync Service provides synchronised entity lists and online write operations. It uses revision numbers for changes to items, attributes, customers, and inventory. A working Web Scenario is a prerequisite. The design primarily anticipates scheduled bulk catalogue updates. A non-default scenario requires the correct WebScenID. We do not promise universal real-time synchronisation.

A professional equipment supplier operates B2B and B2C scenarios. The connector retains the checkpoint for the intended workflow and sends the correct WebScenID where required. If an update stops halfway through, it resumes from the last completed checkpoint rather than advancing merely because a response was received. A purchase creates the corresponding commercial entry in the appropriate scenario, linked to its customer and external order. Catalogue continuity and sale recording can then be checked independently.

An important failure scenario occurs when a bulk update is interrupted and the connector stores the new revision too early. 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 resuming after interruption, a non-default Web Scenario, and creating a new customer. 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: Working Web Scenario and correct WebScenID; API access with company permissions; Revision checkpoints and an initial full synchronisation. Before launch, document the mapping for Initial snapshot → store catalogue → Revision changes → confirmed checkpoint → Online purchase → Galaxy commercial entry. 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.