Test your SOLIDWORKS-to-ERP connection before using it on workshop jobs

One successful request does not prove that a connection fits your workshop. Use a dedicated test product and involve both the designer and the person reviewing data in Eggle ERP.

Six practical scenarios

1. A familiar product: compare expected rows and quantities against the received list.
2. A missing product code: verify a clear error and check that no real product changed unexpectedly.
3. A revised part: change one dimension or quantity, understand the replacement scope and compare both changed and unchanged items.
4. Different categories: check wood, purchased fittings and packaging where your business uses them.
5. An interrupted request: inspect ERP before retrying. A missing response does not by itself prove that nothing was saved.
6. A revoked key: use a dedicated test key, verify it can no longer send, then configure and test its replacement.

Record evidence, not impressions

For each scenario, record the tester, expected outcome, actual ERP result and unresolved issues. Begin production use only when senders and reviewers understand the handover and error process. Do not experiment on an active cutting list or revoke a live machine's key for a demonstration.

See the Eggle connection guide or discuss a workshop-specific trial.