A central production and sales management system for a premium brand

We treated the Dynamic Pricing Module as a critical element, under the highest quality regime. Every price is computed server-side along a strictly defined sequence of components (raw material, components, labor, framing, finishes, channel margins) and stored together with a full breakdown, the calculation date and the version of parameters used.

As a result, calculations are fully repeatable and auditable — an administrator can see at any moment what a given price is made of and compare it with a previous calculation. Changing any parameter (e.g. a commodity rate pulled automatically from NBP) automatically flags all dependent prices for recalculation, and the mass recalculation runs in the background without blocking the team’s work.

The B2B Partner Portal is the system’s second most important tool — all B2B sales flow through it. Each partner has its own company structure with a role hierarchy (owner, manager, employee), support for multiple delivery branches and a configurable order-approval process.

The key was data isolation enforced at the backend level, not in the interface. When handling a wholesale partner’s request, the system simply does not send cost fields, margins or other partners’ data — so there is no way to inspect them, even in the browser developer tools. An additional layer of protection is filtering at the database level itself.

A partner sees only its own catalog, its own net prices, its own orders and its own company data. Orders flow through a transparent process: placement, approval on the company side, automatic handover to the sales channel and live production statuses visible to the buyer.

The retail store, running for years, had an established position in search engines and a stable URL structure. The assumption was simple: don’t touch it. The system acts as the source of truth about the product and exchanges data with the e-commerce platform both ways — it exports the catalog with the right markup per store and receives orders for production, preserving the consistency of identifiers and URLs so as not to harm rankings or existing links.

From day one the architecture is prepared for gradually plugging in the client’s further applications: a shared authentication layer, shared master data exposed via API, a documented contract for every module and a shared interface-component library. Every change of parameters, price lists and permissions goes into an immutable event log. Web-application security standards (including protection against injection, secure password storage, rate limiting on critical endpoints, rotatable session tokens) are built in, and integration keys never reach the client layer.