Back to all work

Software engineering

Pedi-Sense

Shopify storefront, customer-support agent, ecommerce agents, branded email workflows and event analytics.

From storefront to ecommerce services

Behind the storefront, I developed ecommerce and support agents, email workflows, catalogue retrieval and the tracking pipeline into Analytics Hub.

View the desktop screenshot too

French storefront on desktop and mobile. Screenshots taken on 12 September 2026.

Pedi-Sense agents and business workflows

The components developed for this project and their respective responsibilities.

  • Storefront and ecommerce agent

    Product presentation, variants, languages and access to catalogue, stock and order information.

    Shopify APIs connect product and order information to the business services.

  • Customer-support agent

    Support-request handling with catalogue retrieval, store policies and FAQs.

    The workflow includes draft responses for review and escalation to an operator.

  • Emails and customer relationships

    Branded templates for order confirmations, abandoned carts and shipping notifications.

    The email workflows developed use Listmonk and business events.

  • Tracking pixel and Analytics Hub

    Custom pixel integration for purchase-path events and their transformation into KPIs.

    Storefront and agent events → aggregation → Analytics Hub.

Summary

Pedi-Sense combines a Shopify storefront with ecommerce and support agents, branded email workflows, catalogue retrieval and event analytics. The work covers the customer-facing store and the business workflows behind it.

Role and scope

I designed and implemented the storefront, from theme composition and product options to localization, content and launch. I also developed Pedi-Sense’s business integrations, including customer-support workflows, branded emails and storefront event collection.

I built the store’s tracking-pixel integration and the event-to-KPI path into Analytics Hub. The agent workflows also connect to semantic catalogue retrieval and ecommerce knowledge, with content and SEO workflows developed for the store.

Problem and constraints

A focused catalogue needs enough structure for product variants, bundle options, practical information, customer support, localization, and editorial content without obscuring the purchase path.

Architecture

Shopify handles the catalogue, accounts, cart and checkout. Python services connect ecommerce and support agents to product, stock and order information. The support workflow prepares responses for review and escalation; branded email workflows cover order confirmations, abandoned carts and shipping through Listmonk.

Catalogue retrieval uses FAISS, while Qdrant provides ecommerce knowledge and store-specific policies and FAQs. The content and SEO workflow includes task instructions documented as skills. This separates catalogue facts, support documents and editorial methods.

The store’s custom pixel integration collects navigation and purchase-path events. Analytics services store, aggregate and attribute them, then publish KPI snapshots to Analytics Hub over MQTT. Events emitted by the business agents feed the analysis pipeline too.

Decisions and trade-offs

I kept checkout within Shopify while developing business workflows separately. Support includes draft responses for review and escalation to an operator. Email templates cover order confirmations, abandoned carts and shipping notifications.

Public results

The live store presents a complete purchase journey in French, English, German, Italian, and Spanish, with localized regions, currencies, product choices, customer information, and editorial content.

Resources and links

Explore the storefront and its case study. The business integrations use private source code.

Scope and current status

The store is online. The agent services and backend integrations are developed.

Next case study

Persistent Memory

View case study