Overview
Giota's Boutique is a boutique retailer in North Aurora, Illinois, selling both in store and online. Nexren designed and built the boutique's online store and the administrative system behind it.
The business need
The boutique needed to sell online alongside its physical store: take payments, keep inventory accurate, and manage products and orders day to day without technical staff.
That made the work as much about operations as about the storefront. Every order sets off a sequence of tasks, and the system needed to carry that sequence reliably.
What Nexren built
- Storefront and catalog
- Product browsing with variants, a cart, and a checkout that works on phones as well as desktops.
- Payments
- Card payments through Stripe Checkout, so card details never touch the boutique's own servers.
- Order management
- An admin view of every order, searchable by order number, customer name, or email, and filterable by payment and fulfillment status.
- Product and category management
- Staff create and edit products, variants, images, and categories without developer involvement.
- Fulfillment
- Orders are marked shipped with carrier, tracking number, and tracking link, which triggers the customer's shipping email.
- Refunds
- Refunds are issued from the order screen rather than in a separate payments dashboard, and the customer is notified.
- Customer communication
- Order confirmation, shipping, and refund emails are sent automatically, with the boutique copied.
The order workflow
What happens after a customer clicks pay.
The repetitive parts run on their own. Staff step in only for the physical work of shipping and for decisions like refunds.
Step 1
Customer checks out
Payment is taken through Stripe's hosted checkout.
Step 2
Payment confirmed
The server records the order only when Stripe confirms payment.
Step 3
Stock updated
Inventory for each purchased variant is reduced in the database.
Step 4
Customer notified
An order confirmation email is sent automatically.
Step 5
Order fulfilled
Staff mark the order shipped with carrier and tracking details.
Step 6
Shipping notice sent
The customer receives tracking information by email, once.
Step 7
Refund, if needed
Issued from the admin dashboard, with a refund email to the customer.
Engineering approach
Built for the cases that go wrong.
Commerce systems rarely fail on the happy path. These decisions target the situations that cause lost orders, double charges, and inventory errors.
Payment is confirmed by the server, not the browser
An order is created from Stripe's signed webhook, not from the customer landing on a thank-you page. A closed tab or dropped connection can't produce a paid order the boutique doesn't know about, or a recorded order that was never paid.
Retries can't create duplicate orders
Payment providers resend notifications when they don't get a timely response. Each checkout session can only ever produce one order, enforced by the database itself.
Inventory updates in a single step
Stock is reduced by a database function rather than read-modify-write code, so two customers buying the last item at the same moment can't both be counted against the same unit.
A failed email never loses an order
If an email provider is briefly unavailable, the order is still recorded and fulfilled. Notification problems are logged rather than allowed to undo the sale.
Admin access checked on every request
The dashboard requires a signed-in account that is listed as an active administrator, and the server re-checks that on each action. Payment and database secrets stay on the server only.
The result
The store is live at giotasboutique.com and takes orders online. The boutique runs products, orders, fulfillment, and refunds from its own admin dashboard, and customers receive confirmation, shipping, and refund emails without anyone sending them by hand.
This engagement reflects our approach: understand the operational need, make deliberate technical choices, and deliver a system that supports how the business actually works.

