# A B2B portal for a store network's uniforms: how we built it for a tender

> A tender asked for a portal where a store network orders staff uniforms: free kits, paid reorders, multiple brands and the security of a large group. Here is what it does, how we built it with AI and what people checked.

- Published: 2026-11-17
- Who it is for: Companies with store networks and uniformed staff, and workwear suppliers
- URL: https://cloudfactory.it/en/ideas/b2b-uniform-ordering-portal-store-network/

## The problem: uniforms for a store network

![Catalogue of the B2B uniform ordering portal on a computer and order tracking on a smartphone](https://cloudfactory.it/assets/img/articoli/portale-b2b-ordini-divise/copertina.webp)

*Mockup with fictional brands and garments.*

For a network with hundreds of stores, uniforms look like a detail, but they are a process full of exceptions. Every new employee is entitled to a kit, franchise stores pay for reorders and corners inside large retailers are run by agencies that manage several locations. Meanwhile head office wants to know what was shipped, to whom and what is left in stock.

When everything goes through email and spreadsheets the problems are always the same: duplicate or missing kits, untraceable orders, stock that does not add up, no reliable reports. The tender's requirements are common to many networks:

- simple access for every store, from any device, with nothing to install;
- free starter kits with controlled quantities;
- paid reorders at each channel's price list;
- orders decided by head office tracked like all the others;
- multiple brands, each with its own look;
- reports and exports for head office;
- security suited to a large group.

## How it works for each type of store

Each type of store has different rules, and the portal handles them without manual exceptions. Everyone sees only what concerns them.

| User | How they sign in | What they do |
| --- | --- | --- |
| Franchise store | Store code and personal password | Uses the free starter kit, calculated on the number of employees; then reorders at the reserved price list, by card or bank transfer |
| Agency running corners inside large retailers | One account per agency | Chooses which brand to order for and uses an allowance equal to the sum of its corners' kits, with a breakdown per corner |
| Company-owned store | No account: head office orders | Orders decided by head office in the corporate purchasing system enter the portal from a file, so shipping and stock stay tracked |
| Head office administrator | Email and two-factor authentication | Sees only their own channel or brand, orders on behalf of a store, pulls reports |
| Supplier operator | Email and two-factor authentication | Manages catalogue, prices, stock, accounts, shipping and file imports |

Agencies working for more than one brand choose the brand when they sign in. Each brand has its own cart, colours and catalogue, so nobody ends up in the wrong section.

![Brand selection page for an agency working for two brands, with each brand's allowance](https://cloudfactory.it/assets/img/articoli/portale-b2b-ordini-divise/scelta-marchio.webp)

*Brand selection for an agency. Mockup with fictional brands.*

![Head office dashboard with orders to prepare, kits delivered, items per product and Excel and CSV export](https://cloudfactory.it/assets/img/articoli/portale-b2b-ordini-divise/report-sede.webp)

*The head office dashboard. Mockup with fictional data.*

## Main features

- **Sign-in.** A password created for the portal, to be changed at first sign-in; access temporarily suspended after too many failed attempts.
- **Catalogue.** Product pages with photos, fabric, care instructions and a size guide; men's and women's models; lines reserved for specific profiles and invisible to everyone else.
- **Free kits and allowances.** Quantities per employee or per store, with the remaining balance always visible. The check prevents going over the limit even with two orders at the same moment; if an order is cancelled, quantities and stock come back.
- **Paid orders.** One cart per brand, editable shipping address, pre-filled billing details, standard or express shipping. Payment by card through a gateway or by bank transfer.
- **Stock.** Goods are reserved when the order is created and deducted on payment; low-stock alerts below a minimum threshold; every movement is logged.
- **Shipping.** Carrier and tracking code visible to the store in the order details, and updatable in bulk from a file.
- **Reports and exports.** Sales and movements by date, store, product, brand and channel, exportable to Excel and CSV.
- **Support.** Issues, returns and size exchanges linked to the order; a log of every operation.
- **Multiple brands.** Name, colours, logo and fonts are changed from the admin panel: a rebrand is a configuration, not a development project.

![Product page with colours, sizes and size guide](https://cloudfactory.it/assets/img/articoli/portale-b2b-ordini-divise/scheda-prodotto.webp)

*Product page with size guide. Mockup with fictional garments and prices.*

![Composing the free kit by choosing gender and size, with the remaining allowance](https://cloudfactory.it/assets/img/articoli/portale-b2b-ordini-divise/kit-gratuito.webp)

*Composing the free kit. Mockup with fictional data.*

## Technology and infrastructure

We chose mature, open source components with long security support, so the portal stays up to date for years without rewrites.

| Component | Choice | Why |
| --- | --- | --- |
| Application | Laravel 13 on PHP 8.5 | Security fixes until 17 March 2028 for Laravel 13 ([Laravel](https://laravel.com/docs/13.x/releases)) and until 31 December 2029 for PHP 8.5 ([PHP](https://www.php.net/supported-versions.php)) |
| Admin panel | Filament 5 and Livewire 4 | Panels, imports and exports out of the box: less code to maintain |
| Database | MySQL 8.4 LTS | Extended support until 30 April 2032 ([endoflife.date](https://endoflife.date/mysql)) |
| Operating system | Ubuntu 26.04 LTS | Security updates until May 2031, until May 2036 with Ubuntu Pro ([Canonical](https://ubuntu.com/about/release-cycle)) |
| Hosting | Amazon Web Services, Europe (Milan) region | Data in Italy, a dedicated account for each client |
| Email | Amazon SES | Service emails only: credentials, confirmations, shipments |
| Payments | Stripe Checkout | Card data never passes through the portal |

When a version approaches the end of its support, moving to the next one is included in maintenance. The interface is responsive: it works on smartphones, tablets and handheld devices, with no app to install. Colour contrast meets [WCAG 2.1](https://www.w3.org/TR/WCAG21/) level AA, and every feature is covered by automated tests.

## Security: a baseline for everyone, enterprise level for those who need it

A tender from a large group brings security requirements that many e-commerce sites do not meet. We used them as the foundation of the product, not as an add-on.

**For every client:**

- a dedicated server in the European Union, HTTPS, data encryption and daily backups;
- two-factor authentication for administrators and operators, which stores can also turn on;
- passwords stored only as hashes and repeated attempts blocked;
- an operations log kept for at least 12 months;
- security and version updates: never unsupported software.

**For those with stricter requirements, such as the [NIS2 Directive](https://eur-lex.europa.eu/eli/dir/2022/2555/oj):**

- a web application firewall in front of everything, with server and database on a private network;
- administrative access with no open SSH ports, through named and logged accounts;
- a penetration test by an external company before going live;
- a staging environment separate from production;
- development following OWASP guidelines and a software bill of materials (SBOM);
- hybrid post-quantum key exchange (ML-KEM) on the AWS load balancer ([AWS](https://aws.amazon.com/about-aws/whats-new/2025/11/network-load-balancers-post-quantum-key-exchange-tls));
- documented procedures for incidents, continuity and system administrators.

## Built with AI, reviewed by people

We developed the portal with an AI coding agent, Claude Code, driven by a detailed technical brief. It took a few days to go from brief to online demo. This is how we build custom software today: AI shortens the timeline, people decide and check.

- **No real data during development.** The AI received only functional requirements and made-up data.
- **No AI features in the product.** The portal is deterministic: no chatbots, no automatic suggestions, no third-party services with built-in AI.
- **Human review.** The code is reviewed by people, starting with security, permissions, kit calculations and payments.
- **Measurable quality.** Automated tests on every feature and documented design decisions.

## Code ownership and no lock-in

The client is not tied to us. They receive the source code and a perpetual, irrevocable right of use that stays valid even if they stop the service.

- **Data and content** belong to the client, with a full export at any time.
- **Licences:** the application code uses only open source libraries with permissive licences (MIT, BSD, Apache 2.0), with no third-party licences to pay.
- **Hosting of your choice:** a service managed by us, or installation on the client's own server with on-call support.

## Who it is for and how to try it

The platform is designed for:

- chains and franchise networks with uniformed staff: retail, food service, pharmacies, services;
- companies with corners or promoters inside large retailers, run through agencies;
- workwear suppliers who want to offer their clients an ordering portal under their own brand.

A new client is up and running in 2-3 weeks: we configure brands, catalogue, price lists, stores, accounts and kit rules, without developing from scratch. The full story of the project is in our [work](https://cloudfactory.it/en/projects/b2b-uniform-ordering-portal/).

The demo uses made-up data and shows the whole journey in 5 minutes: free kit, paid reorder and tracking for a store; brand selection for an agency; reports and orders on behalf of stores for head office; file imports and shipping for the operator. [Write to us](https://cloudfactory.it/en/#contact) for access: we will send the credentials and walk you through it.

## How we wrote this article

At Cloudfactory we also use artificial intelligence in our editorial work: it helps us find and cross-check sources, compare data, set up the structure and polish the language. The system we use is configured by us, with instructions, examples and procedures built around the way we write. Our team checked every source, corrected the text and approved the published version. The assessments and choices are Cloudfactory's, and we answer for them.

## Frequently asked questions

### What is a B2B uniform ordering portal?

It is a private website where the stores of a network order uniforms and accessories for their staff. It handles free kits, allowances, paid reorders, stock and shipping, and gives head office reports and control over everything.

### Which store networks is it suited to?

Networks with company-owned stores, franchise stores and corners inside large retailers run by agencies, including multi-brand ones. It works from a few dozen to several hundred stores.

### How do free kits and allowances work?

Each store or agency has an allowance of free items, calculated per employee or per store. The portal shows the remaining balance, prevents going over it and updates it with every order or cancellation. Once the allowance is used up, orders are paid.

### Can it be used with more than one brand?

Yes. Each brand has its own colours, logo, catalogue, price lists and cart. Users working for several brands choose the section when they sign in. A rebrand is done from the admin panel, with no development.

### Does it connect to the corporate purchasing system or ERP?

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

### Which payment methods does it support?

Credit or debit card through Stripe Checkout, or bank transfer, which stays pending until the operator records the payment. Free kits require no payment.

### Where is the data hosted?

On Amazon Web Services, in the Europe (Milan) region, with a dedicated account for each client. Database, disks and backups are encrypted.

### Is it secure enough for a large group?

Yes. It was built for a large group's security requirements: web application firewall, two-factor authentication, a penetration test before going live, an operations log, continuous updates. The level is chosen to match the client's requirements.

### Who owns the code?

The client, who receives the source code and a perpetual, irrevocable right of use. The application code uses only open source libraries with permissive licences, so there are no third-party licences to pay.

### How long does it take to get started?

2-3 weeks for a new client, configuring brands, catalogue, price lists, accounts and kit rules. Customisations are planned separately.

### Can it be installed on our own server?

Yes. In that case the server is the client's responsibility and we step in on call for updates and maintenance.

### Does it use artificial intelligence?

We built it with AI, but the product has no AI features: it is deterministic and sends no data to artificial intelligence services.

### How much does it cost?

It depends on the number of stores, the products and the customisations. There is a one-off set-up fee and a monthly fee covering hosting, security, updates and support. We prepare a quote after the demo.

## Sources

- [Laravel, Release Notes: Support Policy](https://laravel.com/docs/13.x/releases)
- [PHP, Supported Versions](https://www.php.net/supported-versions.php)
- [endoflife.date, MySQL](https://endoflife.date/mysql)
- [Canonical, Ubuntu release cycle](https://ubuntu.com/about/release-cycle)
- [AWS, Application and Network Load Balancers now support post-quantum key exchange for TLS](https://aws.amazon.com/about-aws/whats-new/2025/11/network-load-balancers-post-quantum-key-exchange-tls)
- [W3C, Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/)
- [EUR-Lex, Directive (EU) 2022/2555 (NIS2)](https://eur-lex.europa.eu/eli/dir/2022/2555/oj)

---

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