Skip to main content
Back to work

Fleur Studios Automation

A retail automation system that connects inventory changes, purchase orders, preorder messaging, alerts, and dashboard review into one safer workflow.

Retail Operations AutomationAutomation buildProtected operations work

Services

Workflow automation, Dashboard design, Webhook safety, Operational alerts

Stack

Next.js, Supabase, Shopify-style webhooks, SKU/PO integrations

Fleur Studios public product page showing preorder messaging for a retail item
?

The problem

Retail stock and preorder decisions were too manual: teams had to compare store inventory, purchase orders, ETA rules, preorder messaging, and exception alerts by hand.

What changed

We turned that decision-making into a traceable automation system with dry-run review, activity history, alerts, product-level checks, and health monitoring.

What shipped

A protected dashboard with product review, activity, alerts, purchase-order visibility, reconciliation jobs, webhook processing, and integration health checks.

Private details protected

Only a public product-page screenshot is shown. No customer records, product-level private data, order details, staff emails, provider payloads, SKU decisions, or live-write evidence are shown publicly.

Solution timeline

  1. 1

    Map the decision tree

    Translated stock, purchase-order, ETA, preorder, discontinued, and alert rules into a system the team could review.

  2. 2

    Build a safe preview mode

    Kept the workflow observable before live writes so decisions could be checked without touching the store too early.

  3. 3

    Create the dashboard

    Built views for products, activity, alerts, purchase orders, and health so the team could see what the automation was doing.

  4. 4

    Harden the background work

    Added webhook queues, reconciliation jobs, health checks, and tests around the risky operational paths.

Safe public proof

This page talks about the build in plain English. It avoids sensitive data and uses anonymised framing whenever the real client system is private.

Ready to build something useful?

We can turn the messy version of the problem into a practical first build, then keep the private parts private.