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

Stock that follows the physical world

Track stock per warehouse and location, then decide how each storefront should present availability.

01

Multiple locations

Create warehouses that match physical locations and keep stock positions separate without separating the catalog.

02

Availability with context

Decide which warehouse serves which storefront and how much stock a shopper should see.

03

Web to store

Use location level stock to send online visitors to a physical point of sale when that is the better answer.

Inventory is a promise

Displayed stock is not only a number. It is a promise about what will happen after checkout. Keep a buffer for damaged goods, pending orders and returns, and make that buffer explicit rather than hiding it in optimistic availability.

Warehouses also interact with tax and shipping rules. Review those relationships when a new location is added.

Choose the right capacity

Community supports one warehouse, Professional supports five and Enterprise removes the limit. Match the edition to the operating model, not to the current month.

In practice
  • Name warehouses after physical locations, not internal teams.
  • Agree a stock buffer per product group.
  • Review the warehouse and shipping zone relationship after every move.
  • Decide whether storefronts show exact stock or a simple availability state.

Related capabilities

Primary sources

Reference shelf

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

  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • SQL Server Database engine documentation and editions.
  • OData The open data protocol used by the WebStore services layer.
  • NuGet Package distribution used by the .NET client and samples.
  • OWASP Application security guidance and cheat sheets.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • Semantic Versioning Version numbering conventions used in release notes.
  • Schema.org Structured data vocabulary for product and organization markup.
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.