Transaction snapshots
Prices and costs are stored on offer and order items so future pricing changes do not rewrite history.
Architecture
See how the platform supports reliable operations without unnecessary complexity
The platform brings together architecture trust, role control, configurable features, multilingual support, async behavior, and operational data integrity across both sell-side and buy-side operations.
- Product architecture summary
- Core domains
- Data integrity rules
- Role model
- Vendor and procurement domain boundaries
- Order-driven requirement generation
- Feature flags
- Async and notification model
- Shipment operational tables and partitioning direction
- Shared warehouse layer
- Multilingual and theme support
- Five supported portal languages: EN, TR, AZ, RU, AR
Portal language coverage
The product portal supports five languages
- EN English
- TR Turkish
- AZ Azerbaijani
- RU Russian
- AR Arabic
Platform proof
Architecture trust
Rely on pricing snapshots, role-based access, and optional fulfillment modules that support controlled growth
The platform combines transaction integrity, single-company ownership, soft-delete protection, configurable features, async processing, and multilingual support in one operational model.
Single-tenant model
The platform is designed for one owner company operating its own B2B portal.
Soft deletion
Core entities use soft-delete patterns to preserve operational history.
Role boundaries
Admin, CR, Shipping Clerk, and Customer users have intentionally different workspaces and permissions.
Feature flags
Owner-company settings control shipment planning, terminal, printing, proof media, multilingual content, and CR capabilities.
Operational partitioning direction
High-growth shipment tables are designed with partitioning and health checks in mind.
Async-ready
Celery is used for email, notifications, report generation, and media derivative workflows.
Theme and language controls
Portal support includes light and dark mode plus English, Turkish, Azerbaijani, Russian, and Arabic.
Buy-side trust
Keep vendors, procurement items, contracts, and warehouse truth explicit
These buy-side architecture points give technical and operational buyers confidence that procurement work is modeled deliberately inside the same platform.
Separate vendor truth
Vendors remain their own domain instead of being merged into customer records.
Separate procurement item truth
Procurement items remain distinct from sell-side products and variants.
Order-driven requirements
Procurement demand starts from approved order truth and procurement-aware structure.
Snapshot and transaction history
Purchase-order snapshots and append-only balance transactions preserve operational history.
Shared warehouse layer
Warehouse visibility covers both procurement items and sell-side variants.
Constrained external access
Vendor users are limited to the contracts and purchase orders linked to their memberships.
Platform controls
Use permissions, feature settings, search, and multilingual support to keep operations controlled
These platform controls help teams govern access, enable the right workflows, and support multilingual operations without adding unnecessary complexity.
Permission and feature flag model
Admin user management and owner-company settings control what CR, fulfillment, printing, proof, and multilingual capabilities are available.
Portal language support
The product portal supports English, Turkish, Azerbaijani, Russian, and Arabic, which is a key advantage for multilingual operations.
Platform controls
Global search, notifications, dark mode, and controlled access surfaces support the operational workflows around the core commercial and fulfillment modules.
Roadmap
Desktop and mobile apps are coming soon
Dedicated Windows, Linux, macOS, iOS, and Android apps are planned. The web portal remains the primary product surface today.