Print shop CRM — from order to signed act
Challenge
A print shop of 7–10 people ran orders through chats and spreadsheets: line items, design revisions, payments and debts were scattered across messengers. They needed a single system: orders with multiple line items and margin, a design cycle with a revision counter, finances across several legal entities, documents generated from their own templates — and a hard rule that designers and production never see the money.
What was built
In three weeks from first requirements to production, a CRM was built on Laravel + Inertia + React in the print shop's brand style. The entire system is in Ukrainian — UI, statuses, documents and server-side validation.
Orders with line items
each item has its own executor (in-house or contractor), price, cost and margin; orders can be duplicated together with items and checklists.
A 9-stage drag-and-drop kanban plus design sub-stages: brief → mockup → approval → revisions with a cycle counter → approved.
PDF documents from the client's real templates
invoice, delivery note, act, sales receipt; separate numbering per legal-entity×type pair, amount in words, tax status in the header.
Finances across several legal entities (sole proprietors, LLC, cash)
incoming and outgoing payments, client debts and contractor payables with clickable dashboard tiles.
Role model
finances are fully hidden from designers and production, both in the UI and at the data level, proven by feature tests.
Calendar and logistics
order deadlines, deliveries/pickups with addresses and assignees, personal tasks; Overdue / Today / Tomorrow groups.
Checklists with templates (per order and per line item), comments, photo reports with a lightbox, links to design files instead of storing terabytes.
Live sidebar badges
active orders, overdue items and pending logistics counted with a single aggregate query.
Client-branded UI
the print shop website's font and colors, dark sidebar, mobile drawer, fully responsive layout.
Production on the client's shared hosting: PHP 8.3, a safe deployment scheme, 11 role-access feature tests.
Result
The system runs on the client's subdomain. The team manages orders, design revisions, documents and finances in one place; an invoice or act is generated in two clicks instead of manually filling Word templates. The first real order was processed in the system on launch day.
Tech stack
Have a similar challenge?
Discuss a projectNext case
SaaS platform
Alemi Fleet — fleet management SaaS →