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

Bulk changes without bulk risk

Update prices, tiers and stock in volume with validation, scheduling and a clear record of what changed.

01

Dedicated edit screens

Work with purpose built screens for tier pricing, prices and inventory instead of editing products one by one.

02

Import and export

Exchange data with spreadsheets or other systems, then validate before applying changes to the live catalog.

03

Scheduled work

Use scheduled tasks to apply routine updates and reduce the number of manual repeated actions.

Validate before publish

A bulk import can change thousands of prices in a second. Stage the file, check the count and spot check the extremes. A small validation step is cheaper than a rollback.

Keep a copy of every import file with the date and the person responsible. If a number looks wrong, the first question is always which file produced it.

Edition differences

Bulk edit screens, the import and export module and the scheduler are positioned with the Professional and Enterprise Editions. The Community Edition still provides the core catalog and product management tools.

In practice
  • Import into a test catalog before the live catalog.
  • Check the highest and lowest prices in every file.
  • Keep the source file beside the change record.
  • Schedule routine updates outside peak trading hours.

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.
  • Semantic Versioning Version numbering conventions used in release notes.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
  • Open Source Initiative License review and the open source definition.
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.