CaseShop CRM

Retail orders, customer history and stock in one CRM.

CaseShop needed sales, stock and customer information to work together. We built an operator workspace that connects retail orders with customer history, telephony, payment and delivery details.

The operator’s desk

Customer enquiries connect to sales and stock records.

Customer history and telephony

Customer records bring together previous orders and interactions. IP telephony connects calls with the information staff need to investigate a purchase enquiry.

Product variants and availability

Filters by brand, phone model and product type narrow the selection. Operators compare available variants, colours and prices before adding items to the active order.

Order processing

Print instructions, ordered items, payment and delivery details belong to the same order. Stage-specific comments preserve the information needed as the team prepares and fulfils it.

Returns and defects

Return tracking and defect management extend the workspace beyond the sale. Staff handle these cases in the same platform used for customer, order and inventory records.

01 / Order workspace

Print instructions, payment and delivery within the order.

CaseShop CRM: Order details — Order details
The order workspace separates print instructions, customer details, payment and delivery into readable sections. Status and ordered items stay in the side summary, while comments remain with the stage they explain.

02 / Catalogue and variants

Product selection within the active order.

CaseShop CRM: Product selection — Product selection
Model and product filters narrow the available cases. Colour options and prices sit beside each variant, with the selected items, quantities and total shown on the right. Selection happens inside the active order.

Web interface

React provides the interface for working with customers, sales and inventory. TypeScript defines the interface code.

React
TypeScript

Application API

ASP.NET Core Web API connects the web interface with the application’s business logic and data.

ASP.NET Core Web API

Business data

Microsoft SQL Server provides the relational database for the CRM’s operational records.

Microsoft SQL Server

Application cache

Redis provides an in-memory cache for application data, reducing repeated database reads.

Redis

Your sales workflow

A CRM should understand what your team sells.

Variants, customisation, stock, returns and calls shape the operator’s job. We design around those details, starting with the task that currently requires the most switching between tools.

Discuss your CRM