← back to portfolio

Interactive Prototype · Content Commerce API Platform

Pier · seller-onboarding simulator.

Walk the seller-onboarding flow end-to-end: pick a seller archetype (Shopify Plus beauty, Amazon mid-market electronics, WooCommerce DIY apparel), configure the API tier and the 3P apps to install (Yotpo, Rithum, Zendesk, Klaviyo, ShipStation), watch the catalogue sync with field-level conflict resolution and TikTok-specific moderation flags, and export the onboarding manifest, catalogue diff, audit ledger, and partner-app install record. Sellers and 3P apps are mocked; the export schemas are real.

  1. 01Profile
  2. 02Configure
  3. 03Sync
  4. 04Export
01 · Seller profile

Pick a seller archetype.

Sample sellers · commerce-stack preview
Pick a sample above to populate the seller profile.

Proven on the prototype

  • Tiered Open API surface (Lite / Standard / Premium) over a single REST + webhook contract; tier picker is a one-tap decision with rate-budget reservation.
  • Bidirectional catalogue sync runs in under 30 seconds for the 1,200-SKU sample; field-level conflict resolution (price, inventory, moderation tags, listing status) renders deterministically.
  • TikTok-specific moderation flags are surfaced at sync-time, not after, with seller-facing rejection messages and an appeal path keyed to the audit ledger.
  • Onboarding artifacts (manifest, catalogue diff, audit ledger, partner-app install record) export as PM-ready JSON / CSV / JSONL the seller-tools team can archive against the activation cohort.

Out of scope, by design

  • Real OAuth handshakes to Shopify / Amazon / WooCommerce are mocked; live OAuth integration is M0–3 work on real seller credentials.
  • Partner-app permission scopes render as declared metadata; production scope-review (security audit, data-residency check) sits behind real partner certification.
  • Content-moderation ML model is heuristic; production deployment uses TikTok's content-classifier on listing text + image embeddings.
  • Real cryptographic key custody (HSM · rotation · revocation) and rate-limit enforcement at the edge are post-engagement infra, not a static-page concern.