Summary
Pedi-Sense combines a Shopify storefront with custom services developed within Hermes: customer support, email workflows and ecommerce event analysis. The work covers both the customer-facing store and the integrations 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 the Pedi-Sense integrations within Hermes, including customer-support workflows, branded emails and storefront event collection.
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. Separate Hermes services provide a multi-store support agent, connections to order and product information, email delivery through Listmonk, and event collection and attribution. Python services, Shopify APIs and MQTT connect these components.
Decisions and trade-offs
I kept checkout within Shopify while developing business workflows separately. The support implementation includes draft responses for review and escalation to an operator. The email implementation includes templates for order confirmations, abandoned carts and shipping notifications; implementation and activation are tracked separately.
Security context
Payments and checkout remain Shopify-managed. This development case study does not claim a custom payment service, an external security audit, or independent validation of product and health statements.
Testing and verification
Public verification covered the home, product, brand, FAQ, contact, policy, blog, language, region, product-option, cart, and metadata surfaces. No test purchase was made.
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
The public storefront and the dated bilingual GitHub case study document the storefront. The Hermes implementation was reviewed separately in the private source repository; its code and customer data are not published here.
Scope and current status
The storefront is publicly accessible. The backend implementation is private; its current production activation has not been verified for this case study. Sales, conversion, traffic and revenue are not claimed, and product effects and customer statements are not treated as verified evidence.