The real work starts after the order
RetroTablo produces retro-style printed wall art and sells it wholesale. The system processes thousands of orders a day.
In most e-commerce projects the focus is everything up to the order: catalogue, cart, payment. Here it is different. Once an order is placed, every item still has to be physically produced — the artwork is prepared to the print size, printed, packed and handed to the carrier.
At this scale what you are dealing with is not shop software but the digital counterpart of a production line. Thousands of orders a day, each with its own print preparation and packing step, cannot be tracked on hand-kept lists. Which stage an order is at has to be visible at any moment; otherwise a bottleneck only becomes apparent when the customer asks.
Why an off-the-shelf solution was not used
The e-commerce and order management products on the market cover only the front of this flow. Print preparation, scaling and production tracking are not part of the standard packages — and where something similar exists, it does not match the way this business actually produces.
So the system was custom built. React on the interface side, .NET on the application side. We built the larger part of the system and continue to develop it.
The whole order flow in one system
Orders and the dealer side. In a wholesale model the buyer is not an end consumer; dealer login, dealer-specific pricing and order history all need their own structure. That is a different shape from the storefront work we do under e-commerce solutions.
Print preparation and scaling. The ordered artwork is made print-ready for the size of the product. Run manually this step is both slow and error-prone; in the system it is automated.
Packing and dispatch. Packing and dispatch for finished orders are part of the same flow. Every order carries its current stage inside the system.
Shipping. The dispatch process is connected as the final step of the flow.
The question of scale
In a system processing thousands of orders a day, performance is not something to improve later — it is the result of architectural decisions made at the start. The system was designed to absorb growing volume and scales as load increases.
This project sits apart from our integration work: here the job was not connecting existing systems to one another but building an application that carries the company’s own operation end to end. We handle needs like this under custom software development. For a contrast, the Açık Medikal project shows the integration-led side of the same domain.
Server and maintenance
Server management and regular maintenance are on our side: updates, backups and performance monitoring run continuously.
Ongoing work
The work started in 2026 and continues. Development on the system is still under way.
