Services first
The commerce engine is reached through a services layer, so the storefront technology is a choice rather than a constraint.
Call WebStore from .NET, PHP, Java or a mobile client, and connect content systems through standards based services.
The commerce engine is reached through a services layer, so the storefront technology is a choice rather than a constraint.
WCF and OData expose catalog, basket, order and inventory operations to any HTTP capable client.
A membership provider and an Orchard module connect the commerce engine to established .NET content platforms.
Keep the integration contract small and explicit. A storefront that calls a few well understood services is easier to evolve than one that reaches into every corner of the database.
For back office systems, prefer scheduled imports and exports with validation over direct writes. The scheduler can move data on a predictable cadence and leave a record.
Authenticate service calls, restrict network access and avoid placing secrets in client side code. Review the data each integration actually needs and remove permissions that are no longer used.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
The useful test is a real assortment, a real market and a real order. Bring those to a conversation rather than a generic feature list.