# A B2B portal for a store network's uniforms, built for a tender.

> A tender asked for a portal where a network's stores order staff uniforms, with free kits, paid reorders and two separate brands. We built it with an AI coding agent and human review, and put it online as a demo with made-up data.

- Sector: E-commerce
- Practice: Software engineering
- Status: Ongoing
- URL: https://cloudfactory.it/en/projects/b2b-uniform-ordering-portal/

## In brief

For a tender we developed a B2B portal where a network's stores order uniforms and accessories: franchise stores with their store code, agencies running corners inside large retailers, head office administrators with separate scopes. The portal handles free kits per employee or per store, paid reorders at each channel's price list, stock, tracking and reports. It is a Laravel 13 and Filament 5 application for AWS in the Milan region, built with Claude Code from a written brief, with no real data, and reviewed by people.

- **2** brands served by the same application, with separate catalogues, price lists, carts and colours
- **3** channels with different rules: company-owned stores, franchises and large retailers
- **13** functional requirements of the tender covered by the demo
- **0** real data given to the AI during development

## Context

The client has a national network of stores with uniformed staff: company-owned stores, franchise stores and corners inside large retailers run by agencies, across two brands. The tender asked for a cloud portal developed by the supplier, usable from a browser and a smartphone, with different rules for each channel and the security conditions of a large group.

## The problem

The rules were not those of an online shop. The first kit is free and calculated on the number of employees, corners have an allowance per agency, and company-owned stores' orders are placed in head office's purchasing system and only need tracking in the portal. Each administrator must see only their own scope and the two brands must stay separate, colours included. The client's security conditions forbid unsupported software and require a penetration test before going live.

## What we did

1. **Rules in the code, not in plugins.** Per-employee and per-store kits, allowances approved by head office orders, administrator scopes: they are written into the application and covered by automated tests, including two simultaneous orders on the same allowance.
2. **Two brands, one application.** Each brand has its own catalogue, price lists, cart and colours; agencies choose the brand when they sign in. Name, colours and logo are changed from the admin panel, so a rebrand is a configuration.
3. **Head office orders without fragile integrations.** Orders and approvals decided in head office's purchasing system enter the portal from CSV files, with a summary of rejected rows and the reason. The portal tracks shipping and stock deductions even for stores that have no account.
4. **Security designed for a large group.** A dedicated AWS account in Milan, web application firewall, server and database on a private network, no open SSH ports, two-factor authentication, an operations log, components with long support. We answered the client's security conditions point by point.
5. **Built with AI, reviewed by people.** Claude Code wrote the code from a technical brief, with only made-up data and no AI features in the product, as the client's AI code of conduct requires. The critical parts, namely permissions, kit calculations and payments, we reviewed ourselves.

## How it went

The demo is online with made-up data and covers the tender's 13 functional requirements. The offer has been submitted and the outcome is not yet known, which is why the case is ongoing. For other store networks we are preparing a separate version of the platform, configurable in a few weeks.

## Tools

Laravel 13, Filament 5, Livewire 4, PHP 8.5, MySQL 8.4, Ubuntu 26.04, AWS, Amazon SES, Stripe Checkout, Claude Code

## FAQ

### Can a standard online shop handle uniforms for a store network?

For selling, yes; for running a network, less so: per-employee free kits, agency allowances, head office orders and administrator scopes need rules that a standard online shop only covers with many extensions to maintain.

### How does it connect to head office's purchasing system?

Through CSV and Excel imports and exports: orders, kit approvals, store records, tracking and stock levels. Direct API integrations are developed on request.

### Does the code stay with the client?

Yes. The client receives the source code and a perpetual right of use; the application code uses only open source libraries with permissive licences.

---

Cloudfactory S.r.l., Rome. Contact: hello@cloudfactory.it
