Product-data and order-quality process
Professional trust is strengthened by accurate catalogue data, visible revision dates and a server-validated invoice workflow.
Structured product records
Each product record contains a canonical name, SKU, category, brand, manufacturer, origin, exact pack description, current displayed price, stock state and related product links. Product pages are generated from these records rather than copied by hand.
Pricing review states
The catalogue distinguishes verified public prices from values still awaiting internal review. Release checks can block publication when a price source is not approved, while preview builds remain available for design and content QA.
Server-side basket validation
Prices submitted by the browser are never treated as authoritative. The invoice endpoint matches every SKU with the server catalogue, recalculates line totals and rejects unknown or malformed lines.
Transparent requested-product handling
Items not displayed in the catalogue are stored as separate requested-product lines. They never inherit a guessed price. The basket and invoice message label them as pending so the buyer can distinguish known totals from requested additions.