01Goal Definition

Stokkup came to Codal with plans to build an incredibly complex and expansive piece of software that would take print shops into the space age. The capabilities of the proposed system were vast, the user types were numerous, and the number of 3rd party integrations that would be required meant that some careful design (and code) maneuvering had to be conducted.

Additionally, the following requirements were given to Codal’s User Experience team:
  • Super admin functionality for shop management and onboarding
  • Extensive shop settings that tie in directly with every other module
  • A distinct module for each of the many steps in the screen printing process
  • Ability to manage the entire production phase from an intuitive workflow module
  • Interpret complex algorithms for both production estimates and automatic box packing
  • Integrate with multiple shipping services, payment authentication gateways, and accounting softwares
  • Centralize the user’s relevant data in a dashboard

02Ideation & Brainstorming Sessions

The first step in attempting the enormous task of designing such a full circle system is to understand the printing business, process, and problems.

This began with contextual inquiries across multple large print shops in the Chicago area, where Codal’s UX researchers spent several weeks understanding, documenting, and improving on the process.

Once the team understood the print, embroidery, and finishing processes as well as any print shop employee, they were able to sit down with the visionaries at Stokkup and orchestrate a complete overhaul of the process before arriving at an improved flow.

Next, the research met one-on-one with shop employees across the entire production spectrum in order to gather their frustrations, wishes, and requirements.


03User Experience Design

Upon completion of the research phase, the process of architecting Stokkup’s incredibly robust dashboard finally began.

Among the greatest challenges that came up early on in the process was simply a question of how to organize this mass of information in a visually appealing manner. The team decided to layout the information in a dashboard reminiscent of other complex platforms.

This proved advantageous due to the fact that users of the platform had to be restricted to their own modules, and as such, the layout of the dashboard itself was not as much of a concern. Instead the designers were able to focus on the usability of each module.

The system’s twelve independent modules were designed in an intuitive manner which addressed the specific concerns and criticisms voiced during the research phase.

For example, one major print shop expressed concern about the ease with which boxing and shipping would be handled by the new system. As a result, the shipping module was designed to automatically generate suggested box sizes and pack rates based on the size and garment variety of a particular order.


04Web Development

Stokkup’s massive, enterprise level architecture had to be built on the most scalable and stable back end available. That’s why Codal’s engineering team built this web app on the time-tested LAMP stack architecture.

Advanced features include cross-device responsiveness, blazing fast server load times, bar code scan recognition, advanced multi-tenant architecture, client portal, and a full-scale production scheduling system.

Ready to start your journey with Codal?

Schedule a time to chat with us to learn about how Codal can help you grow, or launch your business.

Next Case Study

IndiCard is an app that offers deals to over 20,000 service workers across four major U.S. cities. Users of the app gain access to hundreds of “hook ups”, employee benefits, and even admittance to unique events hosted by Indicard sponsors.