Family-business case study · 19 October 2026

WOOL O WOOL: connecting uniform ordering and everyday operations

What we are building for our family business, why the workflows matter, and how we will judge the results.

Our relationship to this project

WOOL O WOOL is our family uniform business. This is an account of iFactory-led work for that business, rather than an independent client testimonial. We do not yet publish measured time savings, revenue uplift or audited performance results.

The business workflow

WOOL O WOOL manufactures and sells school and institutional uniforms. A uniform order involves more than selecting a product: the school, class, item, size and season affect the choices. The operating team must then handle the order, payment, stock and fulfilment.

Institutional customers add further requirements such as fabric, colours, logo treatment, quantities and commercial approval. Outlet operations introduce billing, returns, stock movements and daily closing.

The problem we set out to address

When product choices and order details pass through separate conversations and records, the team may need to ask the same questions again. We wanted clearer customer choices and a more structured record for the staff responsible for the next step.

Rather than assume one large system should do everything immediately, we worked on three related workflows.

1. School-specific online ordering

The ordering experience is organised around a school’s requirements. The build includes guided item and size selection, product and price information, an order summary, payment-related steps and delivery details.

The design question is practical: can a parent understand what to order, and can the team receive the information it needs to handle that order?

Explore the WOOL O WOOL website ↗

2. Billing and outlet operations

The POS work covers article and size selection, billing, returns and exchanges, inward and outward stock, staff roles, daily closing and reports.

For a product business, the exceptions matter: a return, a transfer between outlets, a correction or a price change. These need understandable controls and a history that supports reconciliation.

3. Institutional catalogue and requirements

The institutional workflow structures product options, sizes, colours, fabric choices, logo requirements, minimum quantities and commercial terms. The aim is to capture a complete requirement before the team moves towards quotation and production.

What this demonstrates—and what still needs checking

AreaBuild focusValidation focus
Customer orderingSchool-specific choices and structured order detailsCheck selection accuracy and repeated customer questions.
Outlet operationsBilling, returns, stock movements and closingReconcile transactions and stock; test staff use during busy periods.
Institutional ordersProduct options and requirement captureCheck completeness and how revisions reach the operating team.
Connections between systemsDefine the shared order and stock informationValidate each handoff before describing it as a single integrated system.

How we intend to measure results

We will publish results only when a defined baseline and comparable operating period support them. Screens and feature lists alone do not establish an improvement.

What another business can take from this

Begin with the information people repeatedly ask for. Define where it should be recorded, who can change it and how the next person knows the work is ready. Then choose a focused first project and test its exceptions with the people who will use it.

The same approach can guide a distributor’s quotation tracker, a manufacturer’s approval workflow or a retailer’s stock and billing system. Each needs its own requirements.

E-commerce development · Billing and inventory software · Custom business software

Discuss one workflow with iFactory India

Based in Chandigarh, we build custom business software, e-commerce websites and billing and inventory systems for businesses in India and abroad.

Bring your workflow to a project discussion ↗

Back to insights · Explore our work