Birted

Architecture

Commerce operations reside in Medusa workflows and modules. The storefront provides browsing and purchasing interfaces, while import runs and product drafts remain separate from published catalog records. This separation supports review before a supplier item becomes a sellable product.

Supplier ingestion pipeline

1. 01

   Acquisition

   Authenticated supplier sessions, category discovery, list and detail HTML parsers, bounded page and item counts.

2. 02

   Normalization

   ISBN normalization, supplier identity resolution, product validation, and deduplication of pending review drafts.

3. 03

   Review

   Persistent per-item outcomes, editorial approval and rejection, and Medusa product creation following approval.

4. 04

   Media

   Supplier cover and gallery image resolution with Cloudflare R2 storage and a dry-run-first backfill tool.

Operational controls

Each catalog run persists fetched items and draft states individually. Network requests have explicit timeouts. Work is limited by item and page ceilings, with cancellation between pages and detection of stalled runs. A database uniqueness constraint prevents overlapping runs for the same supplier scope. Errors are sanitized to avoid exposing supplier credentials.

The Medusa import path is subject to separate staging acceptance and release gates. The live storefront link is not evidence that every import workflow is already enabled in production.