e-commerce-architect

Architect scalable e-commerce systems for catalogs, checkout, and fulfillment.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill e-commerce-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e-commerce-architect
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/e-commerce-architect
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill e-commerce-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects scalable e-commerce architectures for catalogs, checkout, and fulfillment across multi-vendor marketplaces.

Core Features & Use Cases

  • End-to-end catalog modeling, multi-location inventory, and marketplace-level fulfillment.
  • Payments orchestration across PSPs and marketplaces with auditability and security.
  • Governance, PCI DSS compliance, and observability patterns for reliable operations.

Quick Start

Outline an end-to-end architecture for a mid-sized marketplace.

Frequently Asked Questions about e-commerce-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I architect a scalable e-commerce backend for a multi-vendor marketplace?

To architect a scalable e-commerce backend, you outline data models for catalogs, multi-location inventory, and marketplace-level fulfillment, applying integration patterns and governance across the entire architecture.

What is the best way to handle payments orchestration while ensuring PCI compliance?

Payments orchestration across PSPs and marketplaces requires strict guardrails for PCI DSS compliance, auditability, and security, ensuring reliable operations and secure transaction processing across the platform.

How do I model catalog and inventory data for a headless e-commerce setup?

Modeling catalog and inventory data for headless e-commerce involves defining end-to-end data structures for multi-location inventory, marketplace-level fulfillment, and detailed catalog references that support scalable integration.

Does this e-commerce architecture approach support SaaS platforms and multi-vendor marketplaces?

Yes, this e-commerce architecture approach explicitly supports SaaS platforms and multi-vendor marketplaces by outlining scalable data models, integration patterns, and governance rules tailored for these environments.

What governance and observability patterns are needed for reliable e-commerce fulfillment?

Reliable e-commerce fulfillment requires governance patterns that enforce error handling, performance, and security guardrails, alongside observability patterns to monitor operations and maintain auditability across the system.