Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
Platform · 14 of 18

Commerce as a service inside your stack

Call WebStore from .NET, PHP, Java or a mobile client, and connect content systems through standards based services.

01

Services first

The commerce engine is reached through a services layer, so the storefront technology is a choice rather than a constraint.

02

Standards based access

WCF and OData expose catalog, basket, order and inventory operations to any HTTP capable client.

03

Content systems included

A membership provider and an Orchard module connect the commerce engine to established .NET content platforms.

Integration patterns that age well

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.

Security is a shared responsibility

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.

In practice
  • Define the integration contract before choosing a client technology.
  • Use scheduled files for bulk back office exchange.
  • Keep credentials out of storefront source code.
  • Review integration permissions every quarter.

Related capabilities

Primary sources

Reference shelf

Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.

  • OData The open data protocol used by the WebStore services layer.
  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • NuGet Package distribution used by the .NET client and samples.
  • Orchard The content management system supported by the integration module.
  • SQL Server Database engine documentation and editions.
  • OWASP Application security guidance and cheat sheets.
  • W3C Web standards for markup, accessibility and internationalization.
  • GitHub Source hosting and issue tracking for .NET projects.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
Next step

Put this capability against your own catalog

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.