All work/Anubis
Anubis logoCase study · Fashion brand · Italy

Anubis — the shop and the back-office as one system

A shop customers browse like a clothes rail, and a back-office where every order becomes an invoice, a parcel and a stock movement — with each team member signed in under their own name.

ClientAnubis
IndustryFashion & apparel
LocationItaly
DeliveredOnline shop · Back-office · Invoices · Shipping tracking · Reports
01

See it working

Anubis

An order from the website to the invoice, shipping and delivery — and stock that updates itself

Screens recorded with sample data — no real client information.

02

What the brand needed

A small team launching its first collection needed to sell online without stitching together tools: a storefront that feels like the brand, payment that customers trust, and one place to see every order, size and parcel.

  • A storefront with the collection hanging on a rail — front, back and close-up for every piece
  • Payment on a secure page, with the price and stock checked on the server
  • Stock that goes down by itself when a piece sells, and a size that sells out crossed out on the site
  • An invoice for every order with the VAT shown separately
  • A personal login for each of the four team members, and a record of who did what
Where it stands: built and tested end to end. Payment is simulated until the brand connects its Stripe account; prices and stock are added from the back-office.
03

What we built

Storefront

Six pieces in three colours, shown on a rail you drag, each with front, back and detail views.

Secure checkout

The customer pays on Stripe's page. The server re-checks price and stock — nothing is trusted from the browser.

Orders, step by step

Paid, packed, handed to the courier, delivered — a timeline that shows who did each step and when.

Invoice per order

A numbered invoice with the VAT breakdown, shipping and payment status, ready to print or save as PDF.

Stock that moves itself

A sale takes one piece off the right size. Change a price or a quantity and the website follows.

Reports

Revenue by month, best sellers, sizes sold and customers with what they spent.

04

Careful by design

Prices checked on the server

The browser never decides what a piece costs. The price and the stock are read from the database at payment time.

Every action has a name

Each team member signs in personally, and an activity log records who changed what, and when.

The last piece is handled

If two customers buy the last piece at once, the order is flagged and the team is warned — nothing is lost silently.

05

At a glance

6pieces: three colours, hoodie and sweatpants
4team logins, each with its own record
3languages in the back-office
2storefront designs built

Counts describe the system as built.

More case studies

Your brand could sell like this

Tell us how you work today. We'll show you where a system saves time and money, and send a written plan — no phone calls needed.

Talk to us on WhatsApp